I've got some hardware problems w/ SATA drives on my Fedora Core 6 system.

This is what I've got:
ABIT KW-7 motherboard (via sata), ABIT NF7-S motherboard (sil sata)
2x WDC WD4000KD
2x WDC WD3200YS

The WD4000KD's are configured as a software RAID1, the 3200's as a software RAID0

Both motherboards have the sata raid disabled - so the sata controller is just IDE.

Both boxes are FC6 (Linux 2.6.18-1.2849.fc6 #1 SMP Fri Nov 10 12:45:28 EST 2006 i686 athlon i386 GNU/Linux) but have a somewhat different set of packages installed.

The OS for each box is installed on a RAID1 of 2 PATA drives (OS A and B)

Running OS A on the KW-7 w/ the WD4000KD's gives me errors. Running OS A on the NF7-S w/ the WD4000KD's gives me errors.

Running OS A on either motherboard w/ the WD3200YS's gives me no errors. (I did have to force the drives into SATA 150 mode though w/ a jumper)

Running OS B on the NF7-S w/ the WD4000KD's gives me no errors.

I haven't run OS B on the KW-7 w/ the WD4000KD's.


So, I think the problem is possibly a tuning setting on the OS that is affecting the WD4000KD's - but I don't know where to look.

OS B is a 'desktop' install, while OS A is a somewhat trimmed down install. So maybe I'm missing a package somewhere.

Ideally I want the KW-7 to have the WD4000KD's setup and running.

I get the below errors when doing "heavy" read/write to the disks. I've google'd a bit, but most references are to kernel patches - which is not what I think I'm looking for. I also saw the same behaviour w/ FC5.

Any thoughts? Any more information I can provide? (and yes, that's prime like optimus)

Dec 10 15:26:19 prime kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
Dec 10 15:26:19 prime kernel: ata1.00: (BMDMA stat 0x20)
Dec 10 15:26:19 prime kernel: ata1.00: tag 0 cmd 0x25 Emask 0x10 stat 0x51 err 0x84 (ATA bus error)
Dec 10 15:26:20 prime kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Dec 10 15:26:20 prime kernel: ata1: soft resetting port
Dec 10 15:26:20 prime kernel: ata1.00: configured for UDMA/133
Dec 10 15:26:20 prime kernel: ata1: EH complete
Dec 10 15:26:20 prime kernel: SCSI device sda: 781422768 512-byte hdwr sectors (400088 MB)
Dec 10 15:26:20 prime kernel: sda: Write Protect is off
Dec 10 15:26:20 prime kernel: SCSI device sda: drive cache: write back
Dec 10 15:28:31 prime kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
Dec 10 15:28:31 prime kernel: ata1.00: (BMDMA stat 0x20)
Dec 10 15:28:31 prime kernel: ata1.00: tag 0 cmd 0x25 Emask 0x10 stat 0x51 err 0x84 (ATA bus error)
Dec 10 15:28:31 prime kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Dec 10 15:28:31 prime kernel: ata1: soft resetting port
Dec 10 15:28:31 prime kernel: ata1.00: configured for UDMA/133
Dec 10 15:28:31 prime kernel: ata1: EH complete
Dec 10 15:28:31 prime kernel: SCSI device sda: 781422768 512-byte hdwr sectors (400088 MB)
Dec 10 15:28:31 prime kernel: sda: Write Protect is off
Dec 10 15:28:31 prime kernel: SCSI device sda: drive cache: write back
Dec 10 15:29:15 prime kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
Dec 10 15:29:15 prime kernel: ata1.00: (BMDMA stat 0x20)
Dec 10 15:29:15 prime kernel: ata1.00: tag 0 cmd 0x25 Emask 0x10 stat 0x51 err 0x84 (ATA bus error)
Dec 10 15:29:15 prime kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Dec 10 15:29:15 prime kernel: ata1: soft resetting port
Dec 10 15:29:15 prime kernel: ata1.00: configured for UDMA/133
Dec 10 15:29:15 prime kernel: ata1: EH complete