> > [ 225.378426] sd 2:0:1:0: [sdb] Result: hostbyte=0x01 driverbyte=0x00 > > [ 225.378659] end_request: I/O error, dev sdb, sector 141295703 > > [ 225.390133] sd 2:0:1:0: [sdb] Result: hostbyte=0x01 driverbyte=0x00 > > [ 225.391988] end_request: I/O error, dev sdb, sector 141295703 > > [ 225.392463] sd 2:0:1:0: [sdb] Result: hostbyte=0x01 driverbyte=0x00 > > [ 225.392625] end_request: I/O error, dev sdb, sector 141295703 > > [ 225.392999] sd 2:0:1:0: [sdb] Result: hostbyte=0x01 driverbyte=0x00 > > [ 225.393161] end_request: I/O error, dev sdb, sector 141295703 > > [ 225.393571] sd 2:0:1:0: [sdb] Result: hostbyte=0x01 driverbyte=0x00 > > [ 225.393731] end_request: I/O error, dev sdb, sector 141295703 > > [ 225.394382] sd 2:0:1:0: [sdb] Result: hostbyte=0x01 driverbyte=0x00 > > [ 225.394544] end_request: I/O error, dev sdb, sector 141295703 > > [ 225.395247] sd 2:0:1:0: [sdb] Result: hostbyte=0x01 driverbyte=0x00 > > [ 225.395412] end_request: I/O error, dev sdb, sector 141295703 > > I don't know whether this failure was a scsi thing or an ata thing? The ATA layer would print diagnostics if it failed the command so I'm a bit baffled by the report. It looks like the SCSI mid layer rejected it before we even got it ? - To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
