http://www.captain.at/howto-linux-drive ... serror.php
I'm running v2.05 05-2007.
Code:
# Jul 3 01:15:19 user.info kernel: Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4
# Jul 3 01:15:19 user.info kernel: ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
# Jul 3 01:15:19 user.info kernel: VP_IDE: IDE controller at PCI slot 00:0f.0
# Jul 3 01:15:19 user.info kernel: VP_IDE: chipset revision 6
# Jul 3 01:15:19 user.info kernel: VP_IDE: not 100% native mode: will probe irqs later
# Jul 3 01:15:19 user.info kernel: ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
# Jul 3 01:15:19 user.info kernel: VP_IDE: VIA vt8237 (rev 00) IDE UDMA133 controller on pci00:0f.0
# Jul 3 01:15:19 user.info kernel: ide0: BM-DMA at 0xd400-0xd407, BIOS settings: hda:DMA, hdb:DMA
# Jul 3 01:15:19 user.info kernel: ide1: BM-DMA at 0xd408-0xd40f, BIOS settings: hdc:pio, hdd:pio
# Jul 3 01:15:19 user.warn kernel: hda: WDC WD3200JB-00KFA0, ATA DISK drive
# Jul 3 01:15:19 user.warn kernel: hdb: WDC WD3200JB-00KFA0, ATA DISK drive
# Jul 3 01:15:19 user.warn kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
# Jul 3 01:15:19 user.warn kernel: hda: attached ide-disk driver.
# Jul 3 01:15:19 user.warn kernel: hda: host protected area => 1
# Jul 3 01:15:19 user.info kernel: hda: 625142448 sectors (320073 MB) w/8192KiB Cache, CHS=38913/255/63, UDMA(100)
# Jul 3 01:15:19 user.warn kernel: hdb: attached ide-disk driver.
# Jul 3 01:15:19 user.warn kernel: hdb: host protected area => 1
# Jul 3 01:15:19 user.info kernel: hdb: 625142448 sectors (320073 MB) w/8192KiB Cache, CHS=38913/255/63, UDMA(100)
# Jul 3 01:15:19 user.info kernel: Partition check:
# Jul 3 01:15:19 user.info kernel: /dev/ide/host0/bus0/target0/lun0: p1
# Jul 3 01:15:19 user.info kernel: /dev/ide/host0/bus0/target1/lun0: p1
# Jul 3 01:15:19 user.info kernel: SCSI subsystem driver Revision: 1.00
About the only time I see DriveReady SeekComplete Error/DriveStatusError is on reboot -- and perhaps about once a month in the syslog, if that. If the above link is to be believed, it's not much to worry about, but suggests something is up with the driver or HDD firmware.