Skip to contentSkip to conversation

mkraid-problems

DISCUSSION Ekkehard Lissner 2 participants 2 messages Aug 15, 2003 MD RAID

lore
Share & tools
lore
#0 lore raw

Hello,

I have a problem with a raid-5-array. The array consits of 3 disks, sdb1, sdc1 and sdd1.

First I found disk sdb1 out of synch - the timestamp caused it to be kicked out of the array. Second I added the device again with raidhotadd to the array.
Third I rebooted the machine after I had seen a "synched"-message in syslog.

When the machine boots up, it stopped because the raid could not start up again.

When starting the raid manually with raidstart, it shows up that sdb1 and sdc1 have the same timestamp, sdd1 is a lower timestamp. But for some strange reason, sdb1 is also not in the array. This results in the array not comming up, because it can not run with only one disk left.

My question here:
How can I reconstruct the array without losing my data?
The device was formated with a ext2-fs, and since the first failure im very confident that no write-access has been done to the array (it was mounted read-only).
What is the effect of mkraid -f? Does it force a re-construct and does this destroy the filesystem on the md-device?

If there is no normal way to reconstruct the array without losing my data, how about patching the timestamps with a disk-editor? Which bytes must be read from sdc1 and be written to sdd1 and sdb1?

Regards
Ekkehard Lissner

#1 lore raw
Quoted 6 lines · On Friday August 15, [email protected] wrote:

If there is no normal way to reconstruct the array without losing my data, how about patching the timestamps with
a disk-editor? Which bytes must be read from sdc1 and be written to sdd1 and sdb1?

Your array sounds very sick, though it is not at all clear what the problem really is.

I suggest you get mdadm, and use
mdadm --assemble --force /dev/md0 /dev/sd[bcd]1

It will try to assemble the array for force-update event counts as necessary.

What kernel version are you running?

NeilBrown