often ide errors on amd64 / A8N-SLI
from dmesg:
Linux version 2.6.13-rc3-mm1 (jurriaan@middle) (gcc version 4.0.1 (Debian 4.0.1-2)) #4 Thu Jul 21 19:09:25 CEST 2005 Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
NFORCE-CK804: IDE controller at PCI slot 0000:00:06.0
NFORCE-CK804: chipset revision 162
NFORCE-CK804: not 100% native mode: will probe irqs later
NFORCE-CK804: BIOS didn't set cable bits correctly. Enabling workaround.
NFORCE-CK804: 0000:00:06.0 (rev a2) UDMA133 controller
ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:DMA
ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:DMAProbing IDE interface ide0...
hda: WDC WD2000JB-32EVA0, ATA DISK drive
hdb: _NEC DVD_RW ND-3500AG, ATAPI CD/DVD-ROM drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
I see a lot of these errors:
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
CPU0
0: 204642 IO-APIC-edge timer 1: 3710 IO-APIC-edge i8042 8: 0 IO-APIC-edge rtc 9: 0 IO-APIC-level acpi 12: 106 IO-APIC-edge i8042 14: 30571 IO-APIC-edge ide0 15: 30529 IO-APIC-edge ide1 50: 0 IO-APIC-level ohci_hcd:usb2 58: 9407 IO-APIC-level libata 66: 54 IO-APIC-level libata, NVidia CK804 74: 61503 IO-APIC-level libata 82: 0 IO-APIC-level ehci_hcd:usb1 225: 56249 IO-APIC-level ohci1394, fast 233: 0 IO-APIC-level SysKonnect SK-98xx NMI: 483 LOC: 204607 ERR: 0 MIS: 0
Is there any way to detect what exactly is causing this? To the best of my knowledge, the disk works fine - even my raid1 set on this disk isn't impacted, the speed stays ok, I'm wondering if there's a command being sent the disk (or the controller) doesn't know how to handle.
smartctl isn't active, BTW.
Thanks,
Jurriaan
Signature · 6 lines
And the gosts of hope walk silent halls At the death of the promised land All is gone, all is gone But these changing winds can turn cold and hostile New Model Army Debian (Unstable) GNU/Linux 2.6.13-rc3-mm1 5149 bogomips load 0.97
Quoted 2 lines · jurriaan
hda:
dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda:dma_intr: error=0x84 { DriveStatusError BadCRC }
There was corruption on the cable between the controller and drive. That usually indicates a cable or noise problem in the PC but could indicate mistuning of the interface. Make sure the IDE cable is
[controller]<---- long section ----->[slave]--short section-->[master]
as one common cause is having the cable the other way around.
From: Alan Cox <[email protected]>
Date: Thu, Jul 21, 2005 at 08:30:13PM +0100
Quoted 11 lines · jurriaan
Quoted 2 lines
hda:
dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda:dma_intr: error=0x84 { DriveStatusError BadCRC }There was corruption on the cable between the controller and drive. That usually indicates a cable or noise problem in the PC but could indicate mistuning of the interface. Make sure the IDE cable is
[controller]<---- long section ----->[slave]--short section-->[master]
as one common cause is having the cable the other way around.
The cable happens to run the correct way, but you've given me a valuable hint. I was wondering why hda had errors and hdc (which is the same drive on the second port of the controller) didn't. Perhaps I'll try another cable.
Thanks,
Jurriaan
Signature · 5 lines
IF MICROSOFT BUILT CARS...... You could only have one person in the car at a time, unless you bought "Car95" or "CarNT". But, then you would have to buy more seats. Debian (Unstable) GNU/Linux 2.6.13-rc3-mm1 5149 bogomips load 1.94
Quoted 9 lines · Alan Cox
There was corruption on the cable between the controller and drive. That usually indicates a cable or noise problem in the PC but could indicate mistuning of the interface. Make sure the IDE cable is
[controller]<---- long section ----->[slave]--short section-->[master]
as one common cause is having the cable the other way around.
Another common cause is to have the master and slave swapped. The master should be at the end of the cable.
Erik
Signature · 2 lines
+-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 -- | Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands