> -----Original Message----- > From: linux-raid-owner@xxxxxxxxxxxxxxx > [mailto:linux-raid-owner@xxxxxxxxxxxxxxx]On Behalf Of Guy > Sent: 30 August 2004 21:14 > To: 'Jonathan Baker-Bates'; linux-raid@xxxxxxxxxxxxxxx > Subject: RE: The right way to recover from md partition failure? > > > No need to copy, that's what md does. > > Verify that the disk is not part of the array: > mdadm -D /dev/md1 > > I bet you will find the disk is there, but failed. > So, raidhotremove it, then raidhotadd it. > > mdadm is the preferred tool. The old raidtools are not supported. > For details: > man mdadm > > You may need to install mdadm. > > mdadm manage /dev/md1 -r /dev/hde3 > mdadm manage /dev/md1 -a /dev/hde3 > > or short form: > mdadm /dev/md1 -r /dev/hde3 > mdadm /dev/md1 -a /dev/hde3 > > It should start to re-sync. Monitor the status with: > cat /proc/mdstat > and/or > mdadm -D /dev/md1 > Ah, thanks. I'll need to do a backup just in case before I try that though. One question meanwhile: If there are bad blocks on the drive, and assuming mdadm adds that disk to the array OK, can I fsck /dev/md1 in the normal way and repair or mark them as bad? I'm a bit confused about using fsck and RAID. Jonathan - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
