https://bugzilla.kernel.org/show_bug.cgi?id=34302 --- Comment #3 from Andreas Dilger <adilger@xxxxxxxxx> 2011-05-03 17:54:17 --- On 2011-05-03, at 10:27 AM, bugzilla-daemon@xxxxxxxxxxxxxxxxxxx wrote: > The final message of concern was > > May 3 01:40:09 fawkes kernel: [309464.781078] ata8.00: exception Emask 0x0 > SAct 0x2 SErr 0x0 action 0x6 frozen > May 3 01:40:09 fawkes kernel: [309464.781091] ata8.00: failed command: READ > FPDMA QUEUED > May 3 01:40:09 fawkes kernel: [309464.781107] ata8.00: cmd > 60/08:08:47:0a:ab/00:00:45:00:00/40 tag 1 ncq 4096 in > May 3 01:40:09 fawkes kernel: [309464.781111] res > 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) > May 3 01:40:09 fawkes kernel: [309464.781118] ata8.00: status: { DRDY } > May 3 01:40:09 fawkes kernel: [309464.781131] ata8: hard resetting link > May 3 01:40:10 fawkes kernel: [309465.112103] ata8: SATA link up 6.0 Gbps > (SStatus 133 SControl 300) > May 3 01:40:10 fawkes kernel: [309465.119531] ata8.00: configured for UDMA/133 > May 3 01:40:10 fawkes kernel: [309465.119543] ata8.00: device reported invalid > CHS sector 0 > May 3 01:40:10 fawkes kernel: [309465.119559] ata8: EH complete This looks like a problem with your disk. > I am not 100% sure which disk ata8 corresponds to. I tried looking through the > boot log to figure out the device assignments, but it was a bit confusing, It > appears that ata8.00 is one of the source raid disks. If so, I wonder why it > got reset? One possibility is if the source disks share the SATA controller with the target they may both be blocked at the same time. Cheers, Andreas -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
