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

[John Bradford]

> > 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". 
> > 
> > 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.

Quite possible.

> 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).

For some reason, both of my Gigabyte GA-7VA motherboards seem to
disable SMART when I reboot.

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

You may need to use smartctl -e /dev/hdX every time you boot.

John.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/