The current Beta channel for RHEL4 deliver S.M.A.R.T. support for SATA drives.
The smartctl utility needs "-d ata" parametr to work with SATA drive. This
should be picked up automagically as smartctl knows about SATA drive and
complain that one should use "-d libata" (which is wrong too).
Expected result: smartctl works without complains on SATA drives too.
The autodetection of SATA drives must be implemented upstream before we can
consider backporting that to older RHEL releases.
Actual version of smartctl fails on i386 and x86_64 without telling a user that
"-d ata" should be used to see SMART logs and values. This suggestion has been
removed since this bug has been filled. Why?
Current version does not suggest wrong "libata" parameter to the user as error
message or in the man page.
However smartd daemon does nor run tests on SATA discs because lack of
autodetection. How one should monitor discs in enterprise environment? See bug
smartctl /dev/sda (sda is SATA disc) does not return error code even fails on SATA
With -a parameter, returns code 4.
This is wrong, please fix.
Please use one bug report for one bug. Also always please add the exact package
version to the report.
Filled as bug #207324.
Re comment #2: This is probably caused by some change in kernel as there was no
change in the smartctl binary which could affect that. This change must have
broken the SATA detection in the smartmontools SCSI driver.
As of kernel-utils-2.4-13.1.83 the bug still exists:
smartctl -a /dev/sda - returns 4 (this is Ok)
smartctl /dev/sda - returns 0 (this is not Ok, see comment #3)
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
smartctl now autodetects SATA disks and doesn't need any parameter (-d ata).
Tested with kernel-utils-2.4-14.1.117
*** This bug has been marked as a duplicate of bug 206334 ***