Re: Updated on UDMA BadCRC errors + subsequent problems (was: Is it safe to ignore UDMA BadCRC errors?)

[John Bradford]

Quote from Jonathan Kamens <jik@xxxxxxxxxxxxxxxxxxxxxx>:
> John Bradford writes:
>  > Quote from Jonathan Kamens <jik@xxxxxxxxxxxxxxxxxxxxxx>:
>  > > ... hde: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
>  > > ... hde: drive_cmd: error=0x04 { DriveStatusError }
>  > 
>  > The drive doesn't seem to understand the command it was sent.
> 
> I'm not sure what this means, but assuming that it's going to happen
> again at some point,

Maybe not - the most common cause I've seen for that message in the logs is trying to access S.M.A.R.T. information when S.M.A.R.T. is disabled.

I.E. the error should be reproducable with:

# smartctl -d /dev/hda
# smartctl -a /dev/hda

Are you sure you weren't trying to get S.M.A.R.T. info from the drive at the time the error was logged?

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/