RAID 0 Failure

I'm on my Sony Vaio VGC-RC210G and whenever I restart, a message pops up saying "A drive in a RAID 0 volume is failing. Try to back up data immediately."
I believe I'm using 2 160GB Maxtor drives, 1 on RAID 1 and the other on RAID 0.


I haven't noticed any problems, but maybe that's just because I've had the problem for so long. Any suggestions?
27 answers Last reply
More about raid failure
  1. One reason you may not have more responses to your post is that unless you really went through the trouble to set up both RAID1 and RAID0 arrarys on the same 2 disks it may appear that you're confused. If you had such a setup you'd likely know it.

    ...that said do you have a RAID0 or RAID1...or do you really have both type of arrays on the same 2 disks? Its kind of important that you know this...and I do hope you have good, tested, backups.
  2. I didn't set it up, this is how it came, but now that I look at it closer, I think I only have RAID 0.
  3. Okay, well, onboard RAID controllers do get squirly. Back up your data, ASAP, because if the array goes its gonna take some effort, prayers, or an act of God to get your data off the array. Best to kill and rebuild, studying what may have caused the failure (bad disk).

    RAID0 is not generally forgiving. One disk goes...the array goes...your data on the array is G O N E...unless you have a good back up.

    I know I repeated myself, trying to stress my point.
  4. Should I get new HDDs?
  5. Well, that might be premature, but you could do that. Do you have any other signs that the drive(s) are bad? ...any other errors, any audible clicking?
  6. As far as I know, this is the only problem, and it has persisted for a couple months with nothing else happening.
  7. You could try a chkdsk c: /f in cmd prompt and tell it to run the next time windows starts. This will check your disks' filesystem for bad sectors or other errors and fix them. If it finds bad sectors you may want to look at buying two new drives or just one if you don't wanna do raid 0 again.

    And, as was already mentioned, back up any important data you have just in case!
  8. Well, you could just back up your data and keep your fingers crossed. ...but were it me I'd probably at least rebuild the array and re-install Windows. If the error persisted I'd replace the drives.
  9. You cannot get data off raid 0 once you break the raid. I don't care what you think you know but you cannot get data off a raid 0 once you break the raid 0.

    This is why raid 0 is bad and you should never ever ever use raid 0 ever.

    Raid 1 or Raid 5 should be your options. Raid 0 should be banned and removed from every chipset in existence.

    halcyon said:
    Okay, well, onboard RAID controllers do get squirly. Back up your data, ASAP, because if the array goes its gonna take some effort, prayers, or an act of God to get your data off the array. Best to kill and rebuild, studying what may have caused the failure (bad disk).

    RAID0 is not generally forgiving. One disk goes...the array goes...your data on the array is G O N E...unless you have a good back up.

    I know I repeated myself, trying to stress my point.
  10. halcyon said:
    Well, you could just back up your data and keep your fingers crossed. ...but were it me I'd probably at least rebuild the array and re-install Windows. If the error persisted I'd replace the drives.


    Don't forget to remove the raid entirely or use raid 1.
  11. Under my computer how many drives does it show you have? How large are they? If you have more then 1 try saving data to both of them. honestly it doesn't even sound like your system was ever raided.
  12. Port 0 is not raid 0. sata ports on mobos are labled starting from 0 not 1. If your system was in raid 0 and it failed it wouldn't start.
  13. PsyKhiqZero said:
    Under my computer how many drives does it show you have? How large are they? If you have more then 1 try saving data to both of them. honestly it doesn't even sound like your system was ever raided.


    It shows in his first picture that he's using Raid 0, in the second picture you can see the array. In the first picture you can see he is using Basic Mode for the IMSM program, for the second picture he switched to advanced mode which shows the array.

    Like i said before, try chkdsk c: /f in cmd prompt to see if that drive has bad sectors or anything. If not then you may want to try right clicking on the Raid 0 array called Volume 0 and Verify Volume Data. Also if you right click the drive with the error there might be some options, but i'm not sure doing either will fix anything since there is no redundancy on raid 0.

    Most likely you'll have to back up all your data and delete the raid array (from the RAID Bios, should see it each time you start the computer) and recreate it or not recreate it all. Then install windows again. Or... you could live on the edge and see how much longer you can go before it totally dies.
  14. My question is still relevent. he says he hasn't noticed problems. if indeed his raid 0 failed he would have lost some data and that would be a very noticable problem.

    Also if this is an actual matrix setup and there are multiple raid volumes on partitions they would have showed up.

    If windows reports 2 drives at 160GB a piece then his setup is in JBOD mode.

    If it reports a total less then 320 for all drives then he does indeed have a raid 0 and a raid 1 setup.

    IF it reports multiple drives varying in size with a total of 320 then he has 2 raid 0 arrays.

    Of course my method will not work if he has 2 raid 0 arrays at 160GB a piece. but then again that would mean he doesn't have a raid 1 setup either.
  15. xxsk8er101xx said:
    You cannot get data off raid 0 once you break the raid. I don't care what you think you know but you cannot get data off a raid 0 once you break the raid 0.

    This is why raid 0 is bad and you should never ever ever use raid 0 ever.

    Raid 1 or Raid 5 should be your options. Raid 0 should be banned and removed from every chipset in existence.


    I've had RAID 0 arrays fail on this rig, that I've put back together and continued happily. Perhaps they didn't fail hard enough. Didn't take much effort to put them back together and it was not calculus. That's not what I think I know, that's what I indeed do know.

    This is on an Asus Rampage Formula with X48 chipset and ICH9R sb.
  16. PsyKhiqZero said:
    My question is still relevent. he says he hasn't noticed problems. if indeed his raid 0 failed he would have lost some data and that would be a very noticable problem.

    Also if this is an actual matrix setup and there are multiple raid volumes on partitions they would have showed up.

    If windows reports 2 drives at 160GB a piece then his setup is in JBOD mode.

    If it reports a total less then 320 for all drives then he does indeed have a raid 0 and a raid 1 setup.

    IF it reports multiple drives varying in size with a total of 320 then he has 2 raid 0 arrays.

    Of course my method will not work if he has 2 raid 0 arrays at 160GB a piece. but then again that would mean he doesn't have a raid 1 setup either.


    Did you even read or look at anything he posted in his first post? The pictures SHOW that it IS a raid 0 array, not jbod, not raid 1. His raid array has NOT failed, he is getting a message that one of the drives is failing or may soon fail which at that point would cause his raid 0 array to fail and no longer boot windows.
  17. The OP wrote
    I believe I'm using 2 160GB Maxtor drives, 1 on RAID 1 and the other on RAID 0.

    I'm only trying to confirm his actual setup cuz it only shows 1 volume. He says he has both a raid 0 and a raid 1 yet only 1 volume is listed. There is a possibility he is mistaken and in order to help him we should at least confirm his raid configuration.
  18. PsyKhiqZero said:
    The OP wrote
    I believe I'm using 2 160GB Maxtor drives, 1 on RAID 1 and the other on RAID 0.

    I'm only trying to confirm his actual setup cuz it only shows 1 volume. He says he has both a raid 0 and a raid 1 yet only 1 volume is listed. There is a possibility he is mistaken and in order to help him we should at least confirm his raid configuration.


    There's nothing to confirm, look at the first picture in his first post. It says, "Raid 0 stripes user files across multiple hard drives, increasing hard drive performance." He's in basic mode in that picture so there's nothing he can click on for that message to appear, it's just there. He must be using an older version of the software though because I am running a raid 0 and it does not show that message.
  19. When I look at My Computer, it displays one disk, C, that has a total size of 291. I'm currently using version 6.1.0.1002 for the Intel Matrix Storage Console.

    Also, I just found out that the drives are Seagate Barracudas (ST3160023AS) and I only have 4 GB left, if that helps at all. I'm in the process of verifying the data right now.

    Edit: Verification is done. It said that 5 blocks were reassigned and there were no verification errors.
  20. omyjosh said:
    When I look at My Computer, it displays one disk, C, that has a total size of 291. I'm currently using version 6.1.0.1002 for the Intel Matrix Storage Console.

    Also, I just found out that the drives are Seagate Barracudas (ST3160023AS) and I only have 4 GB left, if that helps at all. I'm in the process of verifying the data right now.

    Edit: Verification is done. It said that 5 blocks were reassigned and there were no verification errors.


    Did it clear the error message atleast?
  21. nope :\
  22. Have you run "chkdsk c: /f" in command prompt? (without quotes) It'll check your hard drives for errors and fix them. When you run it it'll tell you it can't dismount and scan now since it's in use, it'll let you run it at the next boot up, just type in y and hit enter to let it do that. Then, just restart your computer and let it do it.

    Or you could just do "chkdsk c:" which will check and idnetify errors without having to reboot. It won't fix any errors if it finds them though, if it finds errors run the first command and then restart, it'll fix them then.

    If it finds bad sectors I would look into buying a new hard drive or two new hard drives if you want to run raid again. You could probably pick up one of those 640GB Western digital drives and it'd probably be a little faster than both of those drives you currently have in RAID 0.
  23. you may want to just buy a 3rd hard disk for storing all your important files. such as pictures, videos and documents and just ignore the error message. If the array actually fails then go ahead and replace the drives if you wanna continue to use raid.

    During boot you can press ctrl-I to setup partions and raids. some times you have to disable quick boot in the bios to do it. You may want to consider doing a raid 1 for your OS and raid 0 for your apps. Setup 2 drives, a 40 gig raid 1 with your OS and any crucial apps. and a 180GB raid 0 for all your games and apps you could live without. Still you would want to keeping your files on a 3rd drive.
  24. PsyKhiqZero said:
    you may want to just buy a 3rd hard disk for storing all your important files. such as pictures, videos and documents and just ignore the error message. If the array actually fails then go ahead and replace the drives if you wanna continue to use raid.

    During boot you can press ctrl-I to setup partions and raids. some times you have to disable quick boot in the bios to do it. You may want to consider doing a raid 1 for your OS and raid 0 for your apps. Setup 2 drives, a 40 gig raid 1 with your OS and any crucial apps. and a 180GB raid 0 for all your games and apps you could live without. Still you would want to keeping your files on a 3rd drive.


    Yep, it's always a good idea to keep stuff you don't want to lose on a seperate drive/partition from your OS. I've been doing this for years and the only thing i've ever lost from a failed OS is maybe a saved game or two. All my music, installers, pictures, etc. are all on a 3rd drive while I install all my games/windows/windows apps on my Raid 0 array.
  25. PsyKhiqZero said:
    you may want to just buy a 3rd hard disk for storing all your important files. such as pictures, videos and documents and just ignore the error message. If the array actually fails then go ahead and replace the drives if you wanna continue to use raid.

    During boot you can press ctrl-I to setup partions and raids. some times you have to disable quick boot in the bios to do it. You may want to consider doing a raid 1 for your OS and raid 0 for your apps. Setup 2 drives, a 40 gig raid 1 with your OS and any crucial apps. and a 180GB raid 0 for all your games and apps you could live without. Still you would want to keeping your files on a 3rd drive.


    I like this idea a lot. I can just buy the third drive and put my files and installers on now, then reformat the other two after, right?

    Also, any more recommendations for new drives? What brands are the best?
    I was look at this Samsung HDD as a possibility: http://www.newegg.com/Product/Product.aspx?Item=N82E16822152100
  26. yeah just pop a third drive in there and copy all the the stuff over. personally i've always used seagate drives there reliable and have a nice 5 year warranty. From what i hear the samsungs are only recommended as performance drives...that is not to say they are not reliable.
  27. I have the same box, with the same problem. except in my case, my first drive failed. I tried rebuilding from the recovery discs, and it fails. I contacted Sony, and they tell me that the recovery discs are no longer available for purchase, and that I can send the box to them for $100 and they will rebuild.

    This box was originally a Media Center box, I don't want to pay them $100 to rebuild it as that. I would much prefer to reload it as an xp machine, but I cannot find a way to reconfig the raid, and when I try to load the os, it fails because it can't read the drives. I can press F6 to load custom raid drivers, except this box has no floppy and that appears to be a stopping point because the windows config will only look at a floppy.

    Finally my question.

    I tried pressing ctrl-I during boot to reconf the raid, all it does is stop the boot process in its tracks.

    Anybody have thoughts on how to proceed? MH
Ask a new question

Read More

NAS / RAID Sony Vaio Storage