On Wed, Jul 12, 2006 at 11:10:59PM +0100, David Greaves wrote: > Alan Cox wrote: > > Ar Maw, 2006-07-11 am 09:28 -0400, ysgrifennodd Justin Piszcz: > >> Alan/Jeff/Mark, > >> > >> Is there anything else I can do to further troubleshoot this problem now > >> that we have the failed opcode(s)? Again, there is never any corruption > >> on these drives, so it is more of an annoyance than anything else. > > > > Nothing strikes me so far other than the data not making sense. Possibly > > it will become clearer later if/when we see other examples. > > For me it's SMART related. > > smartctl -data -o on /dev/sda reliably gets a similar message. > Justin - does this smartctl command trigger a message for you? In that case SMART just isn't enabled. smartctl -d ata --smart=on /dev/sda should make those messages go away. Some BIOSes have a setting to enable/disable SMART, though the option is usually badly documented (hey, what do you expect from BIOS writers). Erik -- +-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 -- | Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands - : 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
