DriveStatusError BadCRC on hda
Hello
I've seen some messages in the system log and am wondering what to do
with them:
Aug 14 06:25:53 pflanze kernel: hda: timeout waiting for DMA
Aug 14 06:25:53 pflanze kernel: ide_dmaproc: chipset supported
ide_dma_timeout func only: 14
Aug 14 06:25:53 pflanze kernel: hda: irq timeout: status=0x59 {
DriveReady SeekComplete DataRequest Error }
Aug 14 06:25:53 pflanze kernel: hda: irq timeout: error=0x84 {
DriveStatusError BadCRC }
Doing a zgrep hda on the old messages logs I get:
messages.0:Aug 6 06:25:47 pflanze kernel: hda: timeout waiting for DMA
messages.0:Aug 6 06:25:47 pflanze kernel: hda: irq timeout:
status=0x59 { DriveReady SeekComplete DataRequest Error }
messages.0:Aug 6 06:25:47 pflanze kernel: hda: irq timeout:
error=0x84 { DriveStatusError BadCRC }
messages.0:Aug 8 06:26:24 pflanze kernel: hda: timeout waiting for DMA
messages.0:Aug 8 06:26:24 pflanze kernel: hda: irq timeout:
status=0x59 { DriveReady SeekComplete DataRequest Error }
messages.0:Aug 8 06:26:24 pflanze kernel: hda: irq timeout:
error=0x84 { DriveStatusError BadCRC }
messages.0:Aug 12 06:27:50 pflanze kernel: hda: timeout waiting for DMA
messages.0:Aug 12 06:27:50 pflanze kernel: hda: irq timeout:
status=0x59 { DriveReady SeekComplete DataRequest Error }
messages.0:Aug 12 06:27:50 pflanze kernel: hda: irq timeout:
error=0x84 { DriveStatusError BadCRC }
The machine runs since 2nd of august with a new hard disk (Quantum
fireball). What I'm wondering is why there is no sector listed where
the error occurs (I'm used to scsi error messages where erroneous
sectors are listed). The machine is used as small corporate
server/firewall, it is not used at all at this time (except cron
jobs). I'm running noflushd so the disk is spun down most of the time
during the night.
Is it a read error on the disk (if yes, should I worry about my
reiserfs filesystem?, should I run a bad-blocks test?), or is it some
communication error or so?
Some parts from dmesg that might be relevant:
PCI: PCI BIOS revision 2.10 entry at 0xfb250, last bus=1
PCI: Using configuration type 1
PCI: Probing PCI hardware
Unknown bridge resource 0: assuming transparent
Found VT82C686A, not applying VIA latency patch.
...
Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: IDE controller on PCI bus 00 dev 39
VP_IDE: chipset revision 16
VP_IDE: not 100% native mode: will probe irqs later
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: VIA vt82c686a (rev 22) IDE UDMA66 controller on pci00:07.1
ide0: BM-DMA at 0xc000-0xc007, BIOS settings: hda:DMA, hdb:DMA
ide1: BM-DMA at 0xc008-0xc00f, BIOS settings: hdc:DMA, hdd:pio
hd0: C/H/S=28741/16/255 from BIOS ignored
hda: QUANTUM FIREBALLP AS60.0, ATA DISK drive
hdb: ATAPI 52X CDROM, ATAPI CD/DVD-ROM drive
hdc: ST340824A, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: 117266688 sectors (60041 MB) w/1902KiB Cache, CHS=116336/16/63, UDMA(66)
BTW: should/could I switch to UDMA/66Mhz or is this done automatically?
BTW II: I also see in dmesg the following - does this really mean
there is only 256k L2 cache?? Even my G3 macintosh from 2 years ago
has 1 MB !! This is a 800Mhz Athlon.
CPU: Before vendor init, caps: 0183f9ff c1c7f9ff 00000000, vendor = 2
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 256K (64 bytes/line)
CPU: After vendor init, caps: 0183f9ff c1c7f9ff 00000000 00000000
CPU: After generic, caps: 0183f9ff c1c7f9ff 00000000 00000000
CPU: Common caps: 0183f9ff c1c7f9ff 00000000 00000000
CPU: AMD Athlon(tm) Processor stepping 02
Sorry for the lenghty post & Thanks for clarification
Christian.
Reply to: