Took less then 24 hours this time. However I did manage to capture dmesg output this time. See the attachment for the full log, here's the snippet how it goes wrong:
mdadm detects a drive timeout (these soft hangs of the hard drives have been present ever since day one and never caused any issues). mdadm fails the drive and tries to keep the raid drive running on 3 disks. But this reset/hang of the disks seems to happen controller wide, thus it fails the next drive until it has no drives left and fails the array with an uncorrectable error message. Then the I/O write errors occur and the system fails. Is mdadm to strict in drive timing? Is the sata controller driver to strict? Where does this go wrong? Any idea's? ** Attachment added: "dmesg output" http://launchpadlibrarian.net/53435676/dmesg.txt -- md raid5 set inaccessible after some time. https://bugs.launchpad.net/bugs/613872 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs