I just installed CentOS 5 on a computer. On boot, I get the a error message, related to 2 SATA disks. These errors did NOT appear on version 4.4 with the EXACT same hardware.
Despite the error messages, the disks seem to be working with no problems.
Could someone please tell me what these error are and if there is some known way to prevent them?
I searched the Net for these errors and they seem to appear with a wide range of disks, controlers and chips set brands, even with different Linux distributions. The issue seems to be related to the last few kernel versions and is perhaps a bug or ill implemented "feature" of libata.
My configuration:
- 2 Hitachi SATA 120 GB Harddisks (first generation, no NCQ) - Intel P4 3GHz - Tyan Tomcat i875p motherboard, Intel ICH5 disk controler - 1 GB ECC RAM - 2 Intel Gb NICs - 1 Intel 10/100 NIC
Error message follows:
--------------------------------------------------------------------- ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 ata1.00: tag 0 cmd 0xb0 Emask 0x1 stat 0x51 err 0x4 (device error) ata1: EH complete ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 ata1.00: tag 0 cmd 0xb0 Emask 0x1 stat 0x51 err 0x4 (device error) ata1: EH complete ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 ata1.00: tag 0 cmd 0xb0 Emask 0x1 stat 0x51 err 0x4 (device error) ata1: EH complete ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 ata1.00: tag 0 cmd 0xb0 Emask 0x1 stat 0x51 err 0x4 (device error) ata1: EH complete ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 ata1.00: tag 0 cmd 0xb0 Emask 0x1 stat 0x51 err 0x4 (device error) ata1: EH complete ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 ata1.00: tag 0 cmd 0xb0 Emask 0x1 stat 0x51 err 0x4 (device error) ata1: EH complete SCSI device sda: 241254720 512-byte hdwr sectors (123522 MB) sda: Write Protect is off sda: Mode Sense: 00 3a 00 00 SCSI device sda: drive cache: write back SCSI device sda: 241254720 512-byte hdwr sectors (123522 MB) sda: Write Protect is off sda: Mode Sense: 00 3a 00 00 SCSI device sda: drive cache: write back ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 ata2.00: tag 0 cmd 0xb0 Emask 0x1 stat 0x51 err 0x4 (device error) ata2: EH complete ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 ata2.00: tag 0 cmd 0xb0 Emask 0x1 stat 0x51 err 0x4 (device error) ata2: EH complete ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 ata2.00: tag 0 cmd 0xb0 Emask 0x1 stat 0x51 err 0x4 (device error) ata2: EH complete ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 ata2.00: tag 0 cmd 0xb0 Emask 0x1 stat 0x51 err 0x4 (device error) ata2: EH complete ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 ata2.00: tag 0 cmd 0xb0 Emask 0x1 stat 0x51 err 0x4 (device error) ata2: EH complete ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 ata2.00: tag 0 cmd 0xb0 Emask 0x1 stat 0x51 err 0x4 (device error) ata2: EH complete SCSI device sdb: 241254720 512-byte hdwr sectors (123522 MB) sdb: Write Protect is off sdb: Mode Sense: 00 3a 00 00 SCSI device sdb: drive cache: write back SCSI device sdb: 241254720 512-byte hdwr sectors (123522 MB) sdb: Write Protect is off sdb: Mode Sense: 00 3a 00 00 SCSI device sdb: drive cache: write back ---------------------------------------------------------------------
Thank you Miguel
I just installed CentOS 5 on a computer. On boot, I get the a error message, related to 2 SATA disks. These errors did NOT appear on version 4.4 with the EXACT same hardware.
Error message follows: (etc)
I connected both disks to a Promise PDC20378 Sata Controler available on the same board and the error disappears. The configuration stays EXACTLY the same, I only switch both disks' SATA cables to the other 2 connectors.
The error was basically this one, repeated several times:
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 ata1.00: tag 0 cmd 0xb0 Emask 0x1 stat 0x51 err 0x4 (device error) ata1: EH complete
I have this 5 times, after which come the statements:
SCSI device sda: 241254720 512-byte hdwr sectors (123522 MB) sda: Write Protect is off sda: Mode Sense: 00 3a 00 00 SCSI device sda: drive cache: write back SCSI device sda: 241254720 512-byte hdwr sectors (123522 MB) sda: Write Protect is off sda: Mode Sense: 00 3a 00 00 SCSI device sda: drive cache: write back
(Is this duplication normal?)
The whole thing is repeated for "ata2.00" and "SCSI device sdb"
So, it is related to the use of the Intel 82801EB ICH5 controler that makes the Southbridge. I report it here in the hope that someone related to kernel development will address this problem.
As I said before, these errors are being reported all over the Net and they seem to appear with a wide range of disks, controlers and chips set brands, even with different Linux distributions. The issue seems to be related to the last few kernel versions and is perhaps a bug or ill-implemented feature of libata or ata_piix.
I would like to give feedback about some disk errors I reported here some days ago:
The errors were the following with ICH5 controler:
--------------------------------------------------------------------- ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 ata1.00: tag 0 cmd 0xb0 Emask 0x1 stat 0x51 err 0x4 (device error) ata1: EH complete --------------------------------------------------------------------- (They were then repeated for ata2.00).
The same disks connected to a Promise controler gave the following errors:
--------------------------------------------------------------------- hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error } hda: drive_cmd: error=0x04 { DriveStatusError } ide: failed opcode was: 0xb0 --------------------------------------------------------------------- (Repeated for hdb)
I asked the kernel developers about these errors and they told me that they were related to SMART.
SMART was disabled in the BIOS. After enabling the optin, the error messages disappeared.
Maybe this information will be useful to someone.
A big thanks to Andrey Melnikoff and Alan Cox for telling me what the problem was.
-
Miguel Medalha