Skip to contentSkip to conversation

Problem: IDE data corruption with VIA chipsets on2.4.20-19.8+others

DISCUSSION Roman Kagan 1 participant 1 message Sep 12, 2003

lore
Share & tools
lore
#0 lore raw
Quoted 4 lines · Rogier Wolff

Anyway, speaking about SMART, some "smartd" was interfering with normal operation on one of our systems and we saw similar "nasty" stuff on that system until I removed "smartd".

Quoted 12 lines
Aug 10 06:54:25 falbala kernel: hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
Aug 10 06:54:25 falbala kernel: hda: drive_cmd: error=0x04 { DriveStatusError }
Aug 10 06:54:25 falbala kernel: hdb: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
Aug 10 06:54:25 falbala kernel: hdb: drive_cmd: error=0x04 { DriveStatusError }
Aug 10 07:24:25 falbala kernel: hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
Aug 10 07:24:25 falbala kernel: hda: drive_cmd: error=0x04 { DriveStatusError }
Aug 10 07:24:25 falbala kernel: hdb: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
Aug 10 07:24:25 falbala kernel: hdb: drive_cmd: error=0x04 { DriveStatusError }
Aug 10 08:24:25 falbala kernel: hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
Aug 10 08:24:25 falbala kernel: hda: drive_cmd: error=0x04 { DriveStatusError }
Aug 10 08:24:25 falbala kernel: hdb: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
Aug 10 08:24:25 falbala kernel: hdb: drive_cmd: error=0x04 { DriveStatusError }

You probably have SMART disabled on those drives by BIOS, and smartd is not smart enough to enable it before trying to use it so the drives complain. I had the same problem on my GigaByte mobo where the BIOS setup didn't even provide an option to turn SMART on (like earlier Award BIOSes did).

Check with smartctl -i /dev/hdX. Enable with smartctl -e /dev/hdX _before_ starting smartd.

Sorry for OT.

Roman.