i recovered my raid by using dd_rescue the last failed disk to a spare
disk (with 4 read errors)
(and doing a mdadm -A -force)
(so I should have a corrupted file somewhere?)
Or a corrupted filesystem, which e2fsck will find & fix.
Did you write down the bad sectors? If so, you can use debugfs to find out
where they are on the filesystem. Computing the filesystem block number from
the device sector number will be an exercise...
On Thu, 22 Dec 2005, Andrew Burgess wrote:
quoted
i recovered my raid by using dd_rescue the last failed disk to a spare
disk (with 4 read errors)
(and doing a mdadm -A -force)
quoted
(so I should have a corrupted file somewhere?)
Or a corrupted filesystem, which e2fsck will find & fix.
filesystem is xfs
and to make sure i runned xfs_check
(which runned for a while with no output)
afther this the dmesg output after mounting :
XFS mounting filesystem md0
Ending clean XFS mount for filesystem: md0
Did you write down the bad sectors? If so, you can use debugfs to find out
where they are on the filesystem. Computing the filesystem block number from
the device sector number will be an exercise...
dd_rescue made a logfile :
dd_rescue: (warning): /dev/sdb1 (39297916.0k): Input/output error!
dd_rescue: (warning): /dev/sdb1 (39297916.5k): Input/output error!
dd_rescue: (warning): /dev/sdb1 (39297917.0k): Input/output error!
dd_rescue: (warning): /dev/sdb1 (39297917.5k): Input/output error!