At 02:16 30.03.00, you wrote:
>Hi... I have a Raid5 Array, using 4 IDE HDs. A few days ago, the system
>hung, no reaction, except ping from the host, nothing to see on the
>monitor. I rebooted the system and it told me, 2 out of 4 disks were out
>of sync. 2 Disks have an event counter of 00000062, the two others
>00000064. I hope, that there is a way to fix this. I searched through the
>mailing-list and found one thread, but it did not help me.
Yes I do. Check Jakobs Raid howto, section "recovering from multiple failures".
You can recreate the superblocks of the raid disks using mkraid; if you
explicitly mark one disk as failed in the raidtab, no automatic resync is
started, so you get to check if all works and perhaps change something and
retry.
* Check your raidtab against the info you get in the logs from the failed
startup (correct sequence of partitions).
* mark one of the disks with the lowest event count as a "failed-disk"
instead of "raid-disk" in the raidtab
* recreate the raid superblocks using mkraid
* try to mount readonly, check if all is OK
* if it doesn't work, recheck raidtab, perhaps mark a different drive as
failed, go back to the mkraid step.
* mount normally, add the last disk using raidhotadd
* remove the failed-disk stuff from your raidtab.
The mkraid command will NOT change any data on your drives except for the
raid superblocks. normally, after mkraid the resynchronisation gets startet
automatically - which you definitely don't want while trying to recover
from a failure - should you have gotten anything wrong, the resync would
definitely kill your data. So, you mark one disk as failed and create the
array in degraded mode.
Bye, Martin
"you have moved your mouse, please reboot to make this change take effect"
--------------------------------------------------
Martin Bene vox: +43-316-813824
simon media fax: +43-316-813824-6
Andreas-Hofer-Platz 9 e-mail: [EMAIL PROTECTED]
8010 Graz, Austria
--------------------------------------------------
finger [EMAIL PROTECTED] for PGP public key
