sda fails also: Feb 24 17:57:42 server-gentoo ata1.00: configured for UDMA/133 Feb 24 17:57:42 server-gentoo sd 0:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x08 Feb 24 17:57:42 server-gentoo sd 0:0:0:0: [sda] Sense Key : 0x3 [current] [descriptor] Feb 24 17:57:42 server-gentoo Descriptor sense data with sense descriptors (in hex): Feb 24 17:57:42 server-gentoo 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 Feb 24 17:57:42 server-gentoo 01 3c ba 1a Feb 24 17:57:42 server-gentoo sd 0:0:0:0: [sda] ASC=0x11 ASCQ=0x4 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). (sector 1072 on sda4). So I am down to one drive, from 3 ... :-( 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 ... S -- 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
