[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

System locking up with hard disk activity


I have a gigabyte motherboard with an nforce chipset, and my hard disk configuration is as follows (with three identical maxtor 160GB sata drives):

server:~# dmesg | grep ata
Bootdata ok (command line is noapic noacpi noapm)
BIOS-e820: 000000003fff3000 - 0000000040000000 (ACPI data)
Memory: 1022912k/1048512k available (1745k kernel code, 24996k reserved, 949k data, 140k init)
libata version 1.10 loaded.
sata_nv version 0.6
ata1: SATA max UDMA/133 cmd 0x9F0 ctl 0xBF2 bmdma 0xD800 irq 11
ata2: SATA max UDMA/133 cmd 0x970 ctl 0xB72 bmdma 0xD808 irq 11
ata1: dev 0 cfg 49:2f00 82:7c6b 83:7f09 84:4003 85:7c68 86:3e01 87:4003 88:407f
ata1: dev 0 ATA, max UDMA/133, 320170943 sectors: lba48
nv_sata: Primary device added
nv_sata: Primary device removed
nv_sata: Secondary device added
nv_sata: Secondary device removed
ata1: dev 0 configured for UDMA/133
scsi0 : sata_nv
ata2: dev 0 cfg 49:2f00 82:7c6b 83:7f09 84:4003 85:7c68 86:3e01 87:4003 88:407f
ata2: dev 0 ATA, max UDMA/133, 320173056 sectors: lba48
ata2: dev 0 configured for UDMA/133
scsi1 : sata_nv
sata_sil version 0.8
ata3: SATA max UDMA/100 cmd 0xFFFFC2000001C080 ctl 0xFFFFC2000001C08A bmdma 0xFFFFC2000001C000 irq 12 ata4: SATA max UDMA/100 cmd 0xFFFFC2000001C0C0 ctl 0xFFFFC2000001C0CA bmdma 0xFFFFC2000001C008 irq 12 ata3: dev 0 cfg 49:2f00 82:7c6b 83:7f09 84:4003 85:7c69 86:3e01 87:4003 88:207f
ata3: dev 0 ATA, max UDMA/133, 320173056 sectors: lba48
ata3: dev 0 configured for UDMA/100
scsi2 : sata_sil
ata4: no device found (phy stat 00000000)
scsi3 : sata_sil
EXT3-fs: mounted filesystem with ordered data mode.
ata1: status=0x51 { DriveReady SeekComplete Error }
ata1: error=0x84 { DriveStatusError BadCRC }

These last errors happen occasionally with normal use. However with intensive hard disk activity (software raid as I tried at first, but abandoned quickly because of the crashes, or more recently with the mythtv backend, watching live tv on another machine) these errors will happen more far more frequently until the machine locks up.

I've run the maxtor diagnostics utility on all three disks and they are all fine. Until I started using mythtv I wasn't too worried about this, just had to reset the machines twice a month or so, with no bad side effects.

This might seem a bit off topic, but I'm running the amd64 kernel on it (Linux server 2.6.11-9-amd64-k8 #1 Sun Apr 3 18:09:29 CEST 2005 x86_64 GNU/Linux).

One thing that struck me when I pasted the dmesg extract that ata1 reports more sectors than ata2 and ata3 even though they are identical disks. Could this be an indication of the problem?

Thanks in advance,


Reply to: