[mdlug] ext3 - fixing bad block in RAID 1 on root file system.

[Dan Pritts]

worst case, you can use dump & restore (or pick your favorite backup
& restore tools) to copy from the mostly-working drive to a new drive.
Should be able to keep going past errors.

while you are dorking with it, you might want to just build up a
fresh fedora 10 system and copy your user data off the existing
drive.

In the future to hopefully avoid this kind of problem, scrub
your RAIDs regularly:

   http://wiki.xdroop.com/space/Linux/Software+Raid+Scrub

Note that this applies for hardware raid as well as software raid,
although obviously it's a different process to scrub HW raid.

On Sun, Dec 21, 2008 at 09:40:06PM -0500, Stan Green wrote:
> I have a ext3 file system, which is the root FS, on a RAID 1 array where one 
> drive failed.  No problem, I replace it and the array starts to rebuild. It 
> gets to 99% done and finds a bad block on the source drive. So, it starts 
> over going into an endless rebuild loop. 
> 
> I booted to Knoppix and ran e2fsck -cc (Should this have been -c ?) on the 
> partition,  /dev/hda1, (not the RAID array), but that did not work. The 
> rebuild still found the bad block.
> 
> So, I need to some how mark the block bad (I have the number) so that the RAID 
> rebuild will complete.
> 
> The system seems to run fine with the bad block, it just will not rebuild the 
> RAID array. The distro is Fedora 6.
> 
> Any ideas here?
> 
> FYI: Yes I am replacing the source drive as soon as I get the the RAID array 
> working again.
> 
> Thanks,
> Stan
> _______________________________________________
> mdlug mailing list
> mdlug at mdlug.org
> http://mdlug.org/mailman/listinfo/mdlug

danno
--
dan pritts
danno at umich.edu
734-929-9770