[cc'ing Bruce Allen] Andrew Paprocki wrote: > I didn't mention it before, but I'm also getting these errors every > time I boot. I'm thinking they're related to the drive not supporting > cmds that smartd is sending it. If so, is there any way that > libata/smartd can handle this more gracefully? This stuff spews into > dmesg and gives a scare that there is a real hardware problem that may > cause data corruption. I get exactly 6 instances of each of these two > blocks of output prior to reaching the login prompt: > > ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 > ata1.00: cmd b0/db:f8:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 0 > res 51/04:f8:00:4f:c2/00:00:00:00:00/00 Emask 0x1 (device error) > ata1.00: configured for UDMA/100 > ata1: EH complete > > ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 > ata2.00: cmd b0/db:f8:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 0 > res 51/04:f8:00:4f:c2/00:00:00:00:00/00 Emask 0x1 (device error) > ata2.00: configured for UDMA/100 > ata2: EH complete Upgrading smartd should fix it. Which version are you using? -- tejun - To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
