Error Message

[netwalker]

Hey all,

My new build that's not yet a month old and I noticed the following error.

Any ideas would be appreciated as I get very random BSOD playing BF4 (unless that's just my bad o/c ing)

I also notice that the Samsung Magician doe snot recognise Raid...is that correct?


Rig details are as follows:

Corsair Carbide Air 540
AUSU Maximus VI Formula MB
i7 4770K
Corsair Dominator Platinum 32GB 2133 @ 9-11-11-31
EVGA GTX 780 Ti SC 3GB Sli
Corsair H100i CPU Cooler
Samsung 840 EVO 250GB Raid 0
Samsung 840 EVO 750GB
ASUS ROG Xonar Phoebus Sound Card
Corsair AX1200i Power Supply
Win 8.1

Cheers all...

 

[Surfie]

Looks like the drive plugged into your 5th SATA port has had an error of some type.

Quite possibly you will need to replace it and rebuild your RAID array. Depends on the error, which you won't know without going into the configuration utility or looking at the log files.

Edit: It also depends on your RAID type. Looking at your configuration, you are either using RAID 0 or 1.

If 0, and it is a fatal error, you're pretty much screwed, since RAID 0 is not redundant at all.

If you use RAID 1, you should be ok, if you replace the disk and rebuild the array.

 

[netwalker]

Looks like the drive plugged into your 5th SATA port has had an error of some type.

Quite possibly you will need to replace it and rebuild your RAID array. Depends on the error, which you won't know without going into the configuration utility or looking at the log files.

Edit: It also depends on your RAID type. Looking at your configuration, you are either using RAID 0 or 1.

If 0, and it is a fatal error, you're pretty much screwed, since RAID 0 is not redundant at all.

If you use RAID 1, you should be ok, if you replace the disk and rebuild the array.

Its Raid 0, so I was thinking of cloning the boot disk and go from there with a replacement perhaps.
Its not fatal but still concerning tho.

Any idea on a good free cloning software?

Cheers...

ps...how would I check what the error is?

 

[tinytomlogan]

Its Raid 0, so I was thinking of cloning the boot disk and go from there with a replacement perhaps.
Its not fatal but still concerning tho.

Any idea on a good free cloning software?

Cheers...

ps...how would I check what the error is?

If you clone it and it doesnt pass ALL the data over cleanly youll just put corrupted data on the other disc....

 

[netwalker]

If you clone it and it doesnt pass ALL the data over cleanly youll just put corrupted data on the other disc....

True, but worth a try first.

Any decent cloning software out there. I have tried Norton Ghost and Acronis in the past to not much luck.

CHeers...

 

[S_I_N]

cloning from raid to non raid and back is usually a crap shot at best with the results normally being snake eyes.

 

[SuB]

Acronis True Image should be alright, I've used that to great effect, creates a carbon copy of the drive, even with a UEFI partition (which ghost has no clue what it is).

But as people have said, cloning into or out-of a RAID array, aint gonna give you perfect results

 

[netwalker]

Okies, I get that message.

Anyone got any idea about the error message and what it might mean or should I head to the Samsung forums?

Cheers...

 

[Surfie]

Well, I don't think that Samsung will be able to help you much, since the error is generally spat out by the RAID controller.

I think that the error indicates bad sectors on the disk in question, but i'm not 100% sure. Best bet is to check with the manufacturer of your RAID card.

 

[netwalker]

Well, I don't think that Samsung will be able to help you much, since the error is generally spat out by the RAID controller.

I think that the error indicates bad sectors on the disk in question, but i'm not 100% sure. Best bet is to check with the manufacturer of your RAID card.

No Raid Card , just a bios setup one. So guessing intel perhaps as the controller?

 

[S_I_N]

why not give us more details about your rig mostly what we need here is mobo and drives in the raid we can see the drives in raid in your pic. And please dont say rigs in sig cause sigs change the topic of the thread doesnt.

Now i used to get that same error with my C300 raid rma'd the drive only to find out it was the intel chipset going bad. Upon pulling the board I found a bent pin in the socket. dont know why it took so long to show as bad. But heres what the symptoms were.

Started with my raid doing what your is one bootup it'd say error occurred next bootup it would be fine (or several reboots seating and reseating the sata cable or replacing sata cables)
then the USB 2.0 ports (controlled by intel chipset) started getting flakey would work have issues like the raid one bootup fine another non working

Ethernet port would also start doing the same as raid and USB 2.0's final straw was when Ethernet died all together.

contacted Gigabyte got an advance RMA setup (I hate getting the same board back) got new board then pulled old one (this is when I discovered the bent pin) Put in new board had zero issues with it so I sent the old board back. Fully expecting Gigabyte to keep my deposit due to bent pin. But gigabyte informed me the RMA was good and released my deposit back.

So basically saying the raid issue may be the start of it. and it may not it could just be a bad cable or bad drive. I'd start by contacting Samsung they will most likely have you do a series of things to reset the drive to factory specs before offering an RMA.

 

[netwalker]

why not give us more details about your rig mostly what we need here is mobo and drives in the raid we can see the drives in raid in your pic. And please dont say rigs in sig cause sigs change the topic of the thread doesnt.

Now i used to get that same error with my C300 raid rma'd the drive only to find out it was the intel chipset going bad. Upon pulling the board I found a bent pin in the socket. dont know why it took so long to show as bad. But heres what the symptoms were.

Started with my raid doing what your is one bootup it'd say error occurred next bootup it would be fine (or several reboots seating and reseating the sata cable or replacing sata cables)
then the USB 2.0 ports (controlled by intel chipset) started getting flakey would work have issues like the raid one bootup fine another non working

Ethernet port would also start doing the same as raid and USB 2.0's final straw was when Ethernet died all together.

contacted Gigabyte got an advance RMA setup (I hate getting the same board back) got new board then pulled old one (this is when I discovered the bent pin) Put in new board had zero issues with it so I sent the old board back. Fully expecting Gigabyte to keep my deposit due to bent pin. But gigabyte informed me the RMA was good and released my deposit back.

So basically saying the raid issue may be the start of it. and it may not it could just be a bad cable or bad drive. I'd start by contacting Samsung they will most likely have you do a series of things to reset the drive to factory specs before offering an RMA.

Cheers...

Appreciate the response. My sig is my rig as it is less than 1 month old. I will try some cable reseating first.

 

[S_I_N]

Cheers...

Appreciate the response. My sig is my rig as it is less than 1 month old. I will try some cable reseating first.

why not give us more details about your rig mostly what we need here is mobo and drives in the raid we can see the drives in raid in your pic. And please dont say rigs in sig cause sigs change the topic of the thread doesnt.

hope thats clearer now this isnt because we dont want to check ur sig. Its because a month or more or less from now somebody else may have a similar issue and use the forum search before posting and looks at ur thread and see wow look he has same issue I'm having and same mobo and you changed your sig and it no longer applies to your current rig but they didnt know because you couldnt take 2 mins to post your specs in the thread and instead decided to use the rigs in sig line. So always when posting about an issue PLEASE FOR THE LOVE OF SANITY for the rest of us put ur rigs specs in the thread

yeah good place to start is the cables and reseating/replacing them then you might want to break the raid and have whatever utility samsung uses to check them.

 

[netwalker]

Ok, I understand now.

Rig details are as follows:

Corsair Carbide Air 540
AUSU Maximus VI Formula MB
i7 4770K
Corsair Dominator Platinum 32GB 2133 @ 9-11-11-31
EVGA GTX 780 Ti SC 3GB Sli
Corsair H100i CPU Cooler
Samsung 840 EVO 250GB Raid 0
Samsung 840 EVO 750GB
ASUS ROG Xonar Phoebus Sound Card
Corsair AX1200i Power Supply
Win 8.1

Cheers...

 

[Warchild]

Samsung magician for me would not even recognise my raid 0. Instead it showed up as Intel Main therefore not allowing all the goodness from the software.

I bit the bullet and removed the raid 0 config so now I have 2x 840pro. To be honest, the performance is still fantastic and I dont really see the point in going back to Raid 0.

At least Samsung recognises the drives now.

edit*
Out of curiosity, I wasted some time going back to raid 0 to see what it would do and samsung recognised it as Intel main again. Probably something i did wrong with creating the raid volume, but I am loving the speed which windows loads for me.

Latest problem i have is stupid inability to upgrade to 8.1. A device I have is stopping the install but I just dont have patience to find out which.

 

[S_I_N]

Ok, I understand now.

Rig details are as follows:

Corsair Carbide Air 540
AUSU Maximus VI Formula MB
i7 4770K
Corsair Dominator Platinum 32GB 2133 @ 9-11-11-31
EVGA GTX 780 Ti SC 3GB Sli
Corsair H100i CPU Cooler
Samsung 840 EVO 250GB Raid 0
Samsung 840 EVO 750GB
ASUS ROG Xonar Phoebus Sound Card
Corsair AX1200i Power Supply
Win 8.1

Cheers...

OK Great now edit your first post with this info

Have you had any luck with your issue?? what have you tried so far??

Samsung magician for me would not even recognise my raid 0. Instead it showed up as Intel Main therefore not allowing all the goodness from the software.

I bit the bullet and removed the raid 0 config so now I have 2x 840pro. To be honest, the performance is still fantastic and I dont really see the point in going back to Raid 0.

At least Samsung recognises the drives now.

edit*
Out of curiosity, I wasted some time going back to raid 0 to see what it would do and samsung recognised it as Intel main again. Probably something i did wrong with creating the raid volume, but I am loving the speed which windows loads for me.

Latest problem i have is stupid inability to upgrade to 8.1. A device I have is stopping the install but I just dont have patience to find out which.

most manufacturers software for ssd's do not recognize drives in any raid config thats why I mentioned to the op to break the raid and use the software to examine the drives. As far as 8.1 I've found it somewhat lacking to the point I reinstalled back to 8

 

[netwalker]

Ok,

A little fault finding seems to point to it being the SSD. swapping all of my SATA cables around in the back only shows a fault when any of the 4 I used are connected to one particular SSD.

Going to d/l Acronis and make a clone, then break the raid and try a backup. Then use Magician to test the offending SSD.

Yes, I still take the note on not possibly getting an error free clone but I think it is worth the shot.

Cheers...

Edit. As soon as I broke the raid the SSD showed no errors. Made the raid and still showed no errors. Pretty confusing so I am hoping acronis worked. If it errors again I will stay with no raid boot.

Edit 2. Well the Acronis backup failed I am now running no raid. All SSD seem fine through Magician and TBH, my machine boots faster without the raid.

So I can only deduct that some part of the out of o/s raid setup was flaky.