Stefan G. Weichinger wrote:
Feb 24 17:57:42 server-gentoo end_request: I/O error, dev sda, sector
20757018
Feb 24 17:57:42 server-gentoo raid5:md4: read error not correctable
(sector 1032 on sda4).
Feb 24 17:57:42 server-gentoo raid5: Disk failure on sda4, disabling
device. Operation continuing on 1 devices
Feb 24 17:57:42 server-gentoo raid5:md4: read error not correctable
(sector 1040 on sda4).
Feb 24 17:57:42 server-gentoo raid5:md4: read error not correctable
(sector 1048 on sda4).
Does it make sense to repeat:
mdadm --assemble
xfs_repair
mount
and rsync stuff aside until it fails again?
I once was lucky with such a strategy ...
I recently had similar problem with a 6 disk array, when one died and
another gave read errors during reconstruction (see older posts about
end of january).
I was able to recover most data reassembling the array and copying data
from it to another storage, repeating the assembly each time the read
errors was encountered; so the 'strategy' mostly worked for me
(recovered almost everything); it may help setting the md device in
readonly mode, and mounign the partition as readonly.
I hope you can recover your data.
Regards
PS.
I see this is the 4th time in a month that poeple reports problem on
raid5 due to the read errors during reconstruction; it looks like the
'corrected read errors' policy is quite a real concern.
--
Cordiali saluti.
Yours faithfully.
Giovanni Tessore
--
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
