[TriLUG] Maxtor on HPT-366 giving DMA errors
Michael Hrivnak
mhrivnak at triad.rr.com
Mon Dec 1 23:37:44 EST 2003
I was getting similar read/write related kernel errors on my hard drive
not too long ago. Despite passing all of WD's utilities, I replaced it
and the cable. The problem persisted, and got worse, to the point of
crashing my system at least daily. I replaced the motherboard and CPU,
problem solved! My suspicion is that the IDE controller or some related
process on the motherboard went bad. For what it's worth, I noticed the
problem was significantly diminished if I stopped using DMA.
Anyone have a suggestion for testing the MB and CPU to verify which was
responsible? It'd be nice to be able to blame one and put the other
back to work.
Thanks,
Michael
-----Original Message-----
From: trilug-bounces at trilug.org [mailto:trilug-bounces at trilug.org] On
Behalf Of James Manning
Sent: Monday, December 01, 2003 9:44 PM
To: trilug at trilug.org
Subject: [TriLUG] Maxtor on HPT-366 giving DMA errors
Ran Maxtor's Powermax util to diag this drive, and both the basic and
full-scan tests (SMART tests included) passed. However, I'm still
getting dma errors for the drive in my kernel log, although maybe
they're innocuous (since things seem to still succeed).
Debian woody box, Abit BP6 (that had no problems with the adaptec scsi
controller and drive that this used to boot to), QQ bios, dual 366
celeron's (UP kernel does the same).
Anyone seen similar issues or heard of a possible solution? I could
drop it down to PIO to test if need be, just more curious if this is
already in someone's mental cache :)
hdparm info:
/dev/hde:
multcount = 0 (off)
I/O support = 0 (default 16-bit)
unmaskirq = 0 (off)
using_dma = 1 (on)
keepsettings = 0 (off)
nowerr = 0 (off)
readonly = 0 (off)
readahead = 8 (on)
geometry = 158816/16/63, sectors = 160086528, start = 0
busstate = 1 (on)
IDE info:
Dec 1 21:23:07 sublogic kernel: Uniform Multi-Platform E-IDE driver
Revision: 6.31
Dec 1 21:23:07 sublogic kernel: ide: Assuming 33MHz system bus speed
for PIO modes; override with idebus=xx
Dec 1 21:23:07 sublogic kernel: PIIX4: IDE controller on PCI bus 00 dev
39
Dec 1 21:23:07 sublogic kernel: ide0: BM-DMA at 0xf000-0xf007, BIOS
settings: hda:pio, hdb:pio
Dec 1 21:23:07 sublogic kernel: ide1: BM-DMA at 0xf008-0xf00f, BIOS
settings: hdc:pio, hdd:pio
Dec 1 21:23:07 sublogic kernel: HPT366: IDE controller on PCI bus 00
dev 98
Dec 1 21:23:07 sublogic kernel: ide2: BM-DMA at 0xd400-0xd407, BIOS
settings: hde:DMA, hdf:pio
Dec 1 21:23:07 sublogic kernel: HPT366: IDE controller on PCI bus 00
dev 99
Dec 1 21:23:07 sublogic kernel: ide3: BM-DMA at 0xe000-0xe007, BIOS
settings: hdg:pio, hdh:pio
Dec 1 21:23:07 sublogic kernel: ide2 at 0xcc00-0xcc07,0xd002 on irq 18
Dec 1 21:23:07 sublogic kernel: ide3 at 0xd800-0xd807,0xdc02 on irq 18
Dec 1 21:23:07 sublogic kernel: /dev/ide/host2/bus0/target0/lun0: p1
Dec 1 21:23:07 sublogic kernel: EXT3 FS 2.4-0.9.17, 10 Jan 2002 on
ide2(33,1), internal journal
drive and errors:
Dec 1 21:23:07 sublogic kernel: ide2: BM-DMA at 0xd400-0xd407, BIOS
settings: hde:DMA, hdf:pio
Dec 1 21:23:07 sublogic kernel: hde: Maxtor 98196H8, ATA DISK drive
Dec 1 21:23:07 sublogic kernel: hde: 160086528 sectors (81964 MB)
w/2048KiB Cache, CHS=158816/16/63, UDMA(66)
Dec 1 21:23:07 sublogic kernel: hde: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Dec 1 21:23:07 sublogic kernel: hde: dma_intr: error=0x84 {
DriveStatusError BadCRC }
Dec 1 21:23:07 sublogic kernel: hde: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Dec 1 21:23:07 sublogic kernel: hde: dma_intr: error=0x84 {
DriveStatusError BadCRC }
Dec 1 21:23:07 sublogic kernel: hde: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Dec 1 21:23:07 sublogic kernel: hde: dma_intr: error=0x84 {
DriveStatusError BadCRC }
Dec 1 21:23:07 sublogic kernel: hde: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Dec 1 21:23:07 sublogic kernel: hde: dma_intr: error=0x84 {
DriveStatusError BadCRC }
Dec 1 21:23:07 sublogic kernel: hde: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Dec 1 21:23:07 sublogic kernel: hde: dma_intr: error=0x84 {
DriveStatusError BadCRC }
Dec 1 21:23:07 sublogic kernel: hde: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Dec 1 21:23:07 sublogic kernel: hde: dma_intr: error=0x84 {
DriveStatusError BadCRC }
Dec 1 21:23:07 sublogic kernel: hde: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Dec 1 21:23:07 sublogic kernel: hde: dma_intr: error=0x84 {
DriveStatusError BadCRC }
Dec 1 21:23:07 sublogic kernel: hde: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Dec 1 21:23:07 sublogic kernel: hde: dma_intr: error=0x84 {
DriveStatusError BadCRC }
Dec 1 21:23:07 sublogic kernel: hde: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Dec 1 21:23:07 sublogic kernel: hde: dma_intr: error=0x84 {
DriveStatusError BadCRC }
Dec 1 21:23:07 sublogic kernel: hde: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Dec 1 21:23:07 sublogic kernel: hde: dma_intr: error=0x84 {
DriveStatusError BadCRC }
Dec 1 21:23:07 sublogic kernel: hde: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Dec 1 21:23:07 sublogic kernel: hde: dma_intr: error=0x84 {
DriveStatusError BadCRC }
Dec 1 21:23:07 sublogic kernel: hde: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Dec 1 21:23:07 sublogic kernel: hde: dma_intr: error=0x84 {
DriveStatusError BadCRC }
Dec 1 21:23:07 sublogic kernel: ide2: reset: success
Dec 1 21:23:24 sublogic kernel: hde: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Dec 1 21:23:24 sublogic kernel: hde: dma_intr: error=0x84 {
DriveStatusError BadCRC }
Dec 1 21:27:34 sublogic kernel: hde: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Dec 1 21:27:34 sublogic kernel: hde: dma_intr: error=0x84 {
DriveStatusError BadCRC }
Dec 1 21:34:08 sublogic kernel: hde: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Dec 1 21:34:08 sublogic kernel: hde: dma_intr: error=0x84 {
DriveStatusError BadCRC }
Dec 1 21:34:08 sublogic kernel: hde: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Dec 1 21:34:08 sublogic kernel: hde: dma_intr: error=0x84 {
DriveStatusError BadCRC }
Dec 1 21:34:08 sublogic kernel: hde: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Dec 1 21:34:08 sublogic kernel: hde: dma_intr: error=0x84 {
DriveStatusError BadCRC }
Dec 1 21:34:09 sublogic kernel: hde: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Dec 1 21:34:09 sublogic kernel: hde: dma_intr: error=0x84 {
DriveStatusError BadCRC }
Dec 1 21:34:09 sublogic kernel: hde: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Dec 1 21:34:09 sublogic kernel: hde: dma_intr: error=0x84 {
DriveStatusError BadCRC }
Dec 1 21:34:10 sublogic kernel: hde: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Dec 1 21:34:10 sublogic kernel: hde: dma_intr: error=0x84 {
DriveStatusError BadCRC }
--
James Manning <http://www.sublogic.com/james/>
GPG Key fingerprint = B913 2FBD 14A9 CE18 B2B7 9C8E A0BF B026 EEBB F6E4
--
TriLUG mailing list :
http://www.trilug.org/mailman/listinfo/trilug
TriLUG Organizational FAQ : http://trilug.org/faq/
TriLUG Member Services FAQ : http://members.trilug.org/services_faq/
TriLUG PGP Keyring : http://trilug.org/~chrish/trilug.asc
More information about the TriLUG
mailing list