|
From: Michael M. <mi...@np...> - 2004-12-22 00:32:07
|
Hi Bruno, > > What I've done after our discussions from yesterday was to use your commands > > below as: > > > > # mdadm /dev/md0 -f /dev/hda1 -r /dev/hda1 -a /dev/hda1 > > > > for each md device, which successfully went through and re-synced the mirrors. > > > > I then booted a rescue cd and: > > > > e2fsck -c /dev/hda1 to 8 (except extended and swap) > > > > No errors were found. > > It would be pretty unlikely to hit something there, since that > doesn't check the data in files. > > > I did this last night with "e2fsck -c" as discussed above, but it didn't find > > anything wrong with the drive. Should I be using the "badblocks" tool for > > this? > > That should run badblocks, but you might want to run it yourself > since you have more flexibility in the test. If the disks aren't > that big letting badblocks repeatedly read and write the disk might > be a good idea. With bigger disks this can take a long time. As discussed yesterday, I ran this through multiple passes last night, all night using the non-destructive read/write tests, and waking up this morning to see the results all tests passed successfully. No errors were detected on the drive. Booting the machine this morning, the same SMART errors were reported to me via email. > There might be something odd about that model of drive. Once a successful > read has been made from a blocking that has a pending reallocation, > it should be reallocated. Yeah I'm not sure what the issue is, but appreciate your help and advice so far. I've learnt a bit during this process :) Michael. |