Tomas Lund wrote:
Hello,
I have a SuperMicro X7SBi with ICH9R SATA running 64bit linux 2.6.24.4.
I have 4 1TB disks connected to the motherboard, and one of the disks is
logging an error message. Everything is brand new, and hooked up just a
few weeks ago.
..
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: irq_stat 0x40000001
ata2.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
res 51/04:00:0a:24:f9/00:00:00:00:00/a9 Emask 0x1 (device error)
ata2.00: status: { DRDY ERR }
ata2.00: error: { ABRT }
..
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
ea 00 00 00 00 00 00 08 03:56:15.157 FLUSH CACHE EXIT
61 08 00 3f 59 70 74 08 03:56:15.157 [RESERVED FOR SERIAL ATA]
ea 00 00 00 00 00 00 08 03:56:15.157 FLUSH CACHE EXIT
ea 00 00 00 00 00 00 08 03:56:00.377 FLUSH CACHE EXIT
61 08 00 3f 59 70 74 08 03:56:00.377 [RESERVED FOR SERIAL ATA]
..
The SMART log shows that 0xea was a "FLUSH CACHE EXT" (not "EXIT", duh..)
command, which is what libata issues when it wants to ensure that all
cached data has been written to the drive.
This particular drive is reporting that it doesn't understand the command.
Peculiar that, because all modern large drives implement it.
What does hdparm --Istdout give for that specific drive,
and then again for one of your three "good" drives ?
Cheers
--
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
