Joe Morris (NTM) wrote:
Joachim Schrod wrote:
On a related note, for other readers: In 10.0, smartmontools don't
work with SATA disks. Anybody knows if this has changed in 10.1 or
10.2, with a more recent kernel?
It must, it works on 9.3. There was an option in the config file for
SATA drives in 9.3.
Hmm, doesn't work here.
I assume that you mean smartd.conf with the config file. There is a
comment that one should use -d ata for SATA disks. Well:
puma:/etc # smartctl -d ata -i /dev/sda
smartctl version 5.33 [i686-pc-linux-gnu] Copyright (C) 2002-4
Bruce Allen
Home page is http://smartmontools.sourceforge.net/
Smartctl: Device Read Identity Failed (not an ATA/ATAPI device)
A mandatory SMART command failed: exiting. To continue, add one
or more '-T permissive' options.
If I use the default for /dev/sda, or make them explicitly SCSI devices:
puma:/etc # smartctl -d scsi -i /dev/sda
smartctl version 5.33 [i686-pc-linux-gnu] Copyright (C) 2002-4
Bruce Allen
Home page is http://smartmontools.sourceforge.net/
Device: ATA ST3200822AS Version: 3.01
SATA disks accessed via libata are not currently supported by
smartmontools. When libata is given an ATA pass-thru ioctl()
then an
additional '-d libata' device type will be added to smartmontools.
Well, the promised device type libata doesn't exist yet:
puma:/etc # smartctl -d libata -i /dev/sda
smartctl version 5.33 [i686-pc-linux-gnu] Copyright (C) 2002-4
Bruce Allen
Home page is http://smartmontools.sourceforge.net/
=======> INVALID ARGUMENT TO -d: libata
=======> VALID ARGUMENTS ARE: ata, scsi, 3ware,N <=======
Use smartctl -h to get a usage summary
Thus, I don't see how I can make it work with smartmontools from the
distribution.
Am I doing something wrong here?
Joachim
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Joachim Schrod Email: [EMAIL PROTECTED]
Roedermark, Germany
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
