Raid 0 which drive failed

Write speed suffers a bit in this set up but you can withstand a single drive failure and be ok. This can be simultaneous failures or during a rebuild another drive can fail and the system will still be operational. It is a very fast setup with redundancy built in and requires a minimum of 4 drives to be operational. Want to learn how to improve your media management practices? External drive with Ghost or Driveimage can backup you system. Hatman Distinguished.

Aug 8, 2, 0 19, 0. Well if you just bought a single drive, doesnt have to be fast, you could simply copy and store files and programs on it without it even being used, so if the raid array fails you can copy it back on there right away.

Wouldnt ever reccomend raid0 for an OS though. Aug 29, 1 0 18, 0. Guest Guest. I know this thread is old but I just had the same problem and would like to answer the last post. I am running win7 click load system repair in win7 and load your raid drivers then run startup repair.

I rebooted and it worked like a charm, no hassle. I don't know why this works as when you delete the array there is a warning saying it will delete all drive data, and the same message appears when you make a new array.

But it does, so I am now making my backup and not complaining. But if someone know why this works I wouldn't mind hearing the details. Jun 24, 5 0 18, 0. Apr 17, 2, 0 21, Have you got your data back by booting Ubuntu livecd? Oh you destroyed the RAID volume; gone is your metadata! You can still recover the data, if you really want to ask me how. G6atToms Distinguished. Aug 14, 1 0 18, 0. Themilkman Honorable.

Sep 1, 1 0 10, 0. I wanted to take the time to respond to this post and bump it. I tried everything and was at the point of giving up with my raid failure. Next step for me was to delete the raid volume and reformat a single drive. But sure enough the procedure listed in this topic worked! I deleted the raid volume, noting the name. Rebooted Created a new raid volume, naming it the same. Rebooted with the OS disc in the tray. Did a system repair, and selected startup repair.

It automatically rebooted and started up normal with all my files intact. I am running a Gateway FX 64bit with Vista. Thanks so much for posting this. I would have hated to lose my data. Best chance is either finding same electronics and hoping that electronics is all that failed or recovering data from backup. This is a common issue and you have uncommonly good potential for recovery. Most modern drives have PCB locked to serial number. Once both images are made you should be able to mount both images and recover data using professional version.

This costs money but is well worth while if needed. It will not try to "fix" your RAID. It will merely create a copy of your RAID at another location. It will collect sector by sector from each single drive involved and write these sectors in the correct order to the designated destination.

This process is also called "de-striping". It will recover from broken Windows Dynamic Disk sets. The part in bold may be a problem for you I don't know if your copied disk will work Old question, but it sounds like you can read both of the disks, just not at the same time. If this is the case, I suspect that mdadm would be happy to run your array if one or both disks were an image file instead of a hardware disk, assuming that mdadm could run the array if both disks were hardware.

You cannot recover a RAID 0 drive that has failed. RAID 0 is striped, meaning the data is split. It's like having only half of a piece of paper that was ripped in two Next time, try RAID 1. You get less space, but the fault tolerance is n-1 drives, so you'll have a much less chance of losing data. Backup should be mandatory for any data that you remotely deem important. Why was a user allowed to create anything, anywhere, at any time????

Bad move, and your data may pay the price. Be sure management knows who did the deed. A drive cannot have failed, there is no limping with RAID 0. Either it failed and all is lost or it has not failed and you need to take a back up, power down, replace the drive, rebuild as RAID 6 or RAID 10 and start over.

Your users have their own platforms? This seems like a bad idea. Brand Representative for Datarecovery. Count you or rather the user fortunate that the limping disk has not completely failed. Hopefully it will survive long enough to back everything up. If not, the data might be lost and you might be contacting a data recovery company to save those VMs. Let's not bee too hard on the OP. We've all been there and discovered a "dafuq?!

You can always pull the failing drive and do a bit for bit drive clone, use the new copy in place to get it running again, and then pull everything off it like removing a bag of oreos from the grasp of a 2year old.

To continue this discussion, please ask a new question.