Re: Resync orphaned drives in RAID 5?
It's been a while since I have done an thing with the 4100. Normally after replacing a HD you must set it has a spare and the unit will pick it up and start the resync. Drive 3 has a different starting point then the other 2 drives. This normally accours if OS updates were done after the RAID5 array was built. OS v2-v3-v4 all calculate the starting point different, this is a time bomb waiting to happen. If this is the case just backup the data while it is in degraded mode (3 of 4 drives).
You need to login as admin and make the new HD a spare. The snap will then init the drive and start the resync. The resync will take a long time so Allow it to run over night, it should be done before morning. If the resync does not happen (be paitent these are not speed demons) use the quick format utility on the new HD to wipe it clean and start over.
Now you say it fails at 5%. This is the point on the HD's where the table is kept. So your orig/bad drive is toast. I use Spinrite to check hd's out.
Read the FAQ's. Also verify the 4100 MB has the MOD done to it. Ref. to Sticky thread "Attention 4100 users" at the top of the theads.
Once you break a Raid5 4 disk array below 3 HD all data is lost. Your only option is a recovery service.
|