Mark Knecht writes:
> On Fri, Feb 26, 2010 at 8:01 AM, Alex Schuster <[email protected]>
> wrote:
> > Okay, but it still states:
> >> * SMART error logging
> >> * SMART self-test
> >
> > So maybe smartctl -t long /dev/hda still works? Just give it a try.
>
> No, -t long fails the same way. Basically every time I try to use
> smartctl on the drive it seems to issue one of these 3-line reports
> about SectorIDNotFound in dmesg. My other machines don't do this. Not
> a good sign I think...
>
> hda: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
> hda: task_no_data_intr: error=0x10 { SectorIdNotFound },
> LBAsect=16777008, sector=18446744073709551615
> hda: possibly failed opcode: 0xb0
Uh-oh. Okay, I guess it just won't work then.
> Could this have ANYTHING to do with kernel configuation? Is there
> anything required at the kernel level that I might not have turned on?
I'm pretty sure it has nothing to do with the kernel, but with your drive
being incapable of the SMART commands.
But I guess using badblocks is not that different in the end. The SMART
selftest runs in the background and does not create disk I/O, but I think
it does nothing so much different from badblocks.
Wonko
