Nicolas STRANSKY wrote:
Le 05/16/2006 01:13 AM, Tejun Heo a écrit :
Hi,
I've been using libata-tj for a couple of days and for now it's working
without problem, my SI-3112 is finally working :) Thanks !
How does it work w/o libata-tj?
smartctl and smartd used to work fine. But I was using a different
controler (Promise PDC20376).
Your drive/controller causes HSM violation probably while executing a
SMART command (maybe during PIO-in during READ DATA?, maybe we need to
dump feature, too). Can you try 'smartctl -d ata -a /dev/sdx' and
report the result and how the kernel acts during that command?
You can find attached the result of the smartctl. It went fine and there
was no kernel message associated. But if I try to reproduce smartd
command, then "smartctl -d ata -a -o on -S on /dev/sda" causes the same
error I showed in the first post, and smartctl fails with this error:
Error SMART Enable Auto-save failed: I/O error
Smartctl: SMART Enable Attribute Autosave Failed.
Hmmm.. That measn SMART ENABLE/DISABLE ATTRIBUTE AUTOSAVE command fails.
But weirdly it fails with DRQ (ready for data) bit set, thus
triggering HSM violation. My guess is the drive doesn't support that
command and when it aborts, it sends funky status. I think you can
safely ignore the error or remove -S on from smartd configuration.
If you've got some time though, I'd like to see what's really going on.
Can you modify #undef ATA_DEBUT to #define ATA_DEBUG in
include/linux/libata.h and post the kernel messages after issuing above
command? Be warned that it will produce a LOT of messages while booting
if you're using SATA disks for your system, and it can considerably slow
down booting.
--
tejun
-
: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
