* Disk errors reported on boot - kernel 2.6.18
@ 2007-06-14 6:44 Miguel Medalha
0 siblings, 0 replies; 4+ messages in thread
From: Miguel Medalha @ 2007-06-14 6:44 UTC (permalink / raw)
To: linux-ide
Gentlemen
I thought you might be interested in the following:
I just installed CentOS 5 on a computer (kernel-2.6.18-8.1.4.el5.i686) . On
boot, I get an error message,
related to 2 SATA disks. These errors did NOT appear on version 4.4
(kernel-smp-2.6.9-42.EL.i586) with the
EXACT same hardware.
Despite the error messages, the disks seem to be working with no problems.
I searched the Net for these errors and they seem to appear with a wide
range of disks, controlers and chip 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.
My configuration:
- 2 Hitachi HDS722512VLSA80 SATA 120 GB Harddisks (first generation, no NCQ)
- Intel P4 3GHz
- Tyan Tomcat i875p (S5102) 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
---------------------------------------------------------------------
This repeats another 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"
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.
So, it is related to the use of the Intel 82801EB ICH5 controler that makes
the Southbridge.
Thank you
Miguel Medalha
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Disk errors reported on boot - kernel 2.6.18
@ 2007-06-16 15:08 Miguel Medalha
2007-06-16 17:30 ` Alan Cox
0 siblings, 1 reply; 4+ messages in thread
From: Miguel Medalha @ 2007-06-16 15:08 UTC (permalink / raw)
To: linux-ide
After my previous message on the same subject, I thought it would be useful
to report the following:
I recently installed a new disk on the same computer. This one is a Hitchi
HDS721616PLAT80.
When this disk is connected to the ICH5 controller, the following error
lines appear on boot:
-------------------------------------------------------------------
hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
hda: drive_cmd: error=0x04 { DriveStatusError }
ide: failed opcode was: 0xb0
-------------------------------------------------------------------
The drive is working perfectly. I even verified it with a tool provided by
the manufacturer. SMART also does not report any error .
The same disk gives no error whatsoever when connected to a ITE8212 IDE
Controler present on the same computer.
The overall configuration of this machine was given on my previous post.
Thank you for your attention.
Best regards
Miguel
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Disk errors reported on boot - kernel 2.6.18
2007-06-16 15:08 Miguel Medalha
@ 2007-06-16 17:30 ` Alan Cox
0 siblings, 0 replies; 4+ messages in thread
From: Alan Cox @ 2007-06-16 17:30 UTC (permalink / raw)
To: Miguel Medalha; +Cc: linux-ide
> I recently installed a new disk on the same computer. This one is a Hitchi
> HDS721616PLAT80.
>
> When this disk is connected to the ICH5 controller, the following error
> lines appear on boot:
>
> -------------------------------------------------------------------
> hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
> hda: drive_cmd: error=0x04 { DriveStatusError }
> ide: failed opcode was: 0xb0
Your new drive rejected a SMART command. It was asked (by user space I
suspect - ie smartd) to do some kind of smart operation and reported
51/04 - which is basically 'I do not know/support the command you have
asked me to perform) - amd opcode 0xB0 is smart.
> The drive is working perfectly. I even verified it with a tool provided by
> the manufacturer. SMART also does not report any error .
> The same disk gives no error whatsoever when connected to a ITE8212 IDE
> Controler present on the same computer.
The IT8212 with raid firmware doesn't support SMART so any smart
configuration funnies would be hidden
Alan
^ permalink raw reply [flat|nested] 4+ messages in thread
* Disk errors reported on boot - kernel 2.6.18
@ 2007-06-17 11:51 Miguel Medalha
0 siblings, 0 replies; 4+ messages in thread
From: Miguel Medalha @ 2007-06-17 11:51 UTC (permalink / raw)
To: linux-ide
Hello
I received a message from Andrey Melnikoff. I tried to answer him but the
remote host keeps rejecting the message because he is "backlisted".
<temnota+news@kmv.ru>:
217.13.212.5 does not like recipient.
Remote host said: 553 5.3.0 <temnota+news@kmv.ru>... Too many spam messages.
Blacklisted. 2004/03/17
Giving up on 217.13.212.5.
I am sending this for his information.
Thank you!
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2007-06-17 11:51 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-06-17 11:51 Disk errors reported on boot - kernel 2.6.18 Miguel Medalha
-- strict thread matches above, loose matches on Subject: below --
2007-06-16 15:08 Miguel Medalha
2007-06-16 17:30 ` Alan Cox
2007-06-14 6:44 Miguel Medalha
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox