On 15/12/2013 10:34 AM, Alex wrote:
Hi,
What I would do is run smartctl -t short /dev/sdc, then smartctl -a /dev/sdc
and make sure the drive was reported as PASSED and not in imminent failure. Then
run fsck on /dev/sdc2 (the partition reporting the I/O error on what was sda2 --
DO NOT fsck /dev/sdc3.
I ran a short (which succeeded) then a long (which also succeeded)
test on /dev/sdc.
I realized that /dev/sdc2 is a non-raid partition mounted as /boot, so
it can't be checked.
This box is in a remote datacenter. Still think it's okay to boot remotely?
Thanks,
Alex
--
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
You could also try running a non destructive badblocks check on the
partition "badblocks -nsv /dev/sdc3" and see if it fails again, it could
be the cable rather than the disk that is at fault. I would expect that
a reboot would set the drive back to sda.
--
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
