lib(p)ata SMART support?
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Using legacy drivers I can use any SMART tools out there; HDD does support SMART. Running libata + pata_ali, smartctl claims device does not support SMART. This is sort of regression when switching from legacy drivers.
- -andrey
libata version 1.30 loaded.
ACPI: PCI Interrupt 0000:00:04.0[A]: no GSI
ata1: PATA max UDMA/100 cmd 0x1F0 ctl 0x3F6 bmdma 0xEFF0 irq 14 scsi0 : pata_ali
ata1.00: configured for UDMA/33
Vendor: ATA Model: IC25N020ATDA04-0 Rev: DA3O
Type: Direct-Access ANSI SCSI revision: 05
ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xEFF8 irq 15 scsi1 : pata_ali
ata2.00: configured for PIO4
Vendor: TOSHIBA Model: DVD-ROM SD-C2502 Rev: 1313
Type: CD-ROM ANSI SCSI revision: 05
SCSI device sda: 39070080 512-byte hdwr sectors (20004 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
SCSI device sda: 39070080 512-byte hdwr sectors (20004 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
sda: sda1 sda2
sd 0:0:0:0: Attached scsi disk sda
{pts/0}% sudo smartctl -i /dev/sda
smartctl version 5.36 [i586-mandriva-linux-gnu] Copyright (C) 2002-6 Bruce Allen
Home page is http://smartmontools.sourceforge.net/
Device: ATA IC25N020ATDA04-0 Version: DA3O
Serial number: 63A63GY1081
Device type: disk
Local Time is: Tue Jun 27 15:54:27 2006 MSD
Device does not support SMART
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
iD8DBQFEoRyhR6LMutpd94wRAh/6AJsENQEibwUqGrP2q7cSIpDy9fIedgCfV6Y2 COg2D+QL58CNlKBGXvnrM6Q=
=DDES
-----END PGP SIGNATURE-----
Quoted 3 lines · Andrey Borzenkov
Using legacy drivers I can use any SMART tools out there; HDD does support SMART. Running libata +
pata_ali, smartctl claims device does not support SMART. This is sort of regression when switching from legacy drivers.
Try smartctl -d ata.
Erik
Signature · 2 lines
+-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 -- | Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Quoted 8 lines · Erik Mouw
Quoted 4 lines · Andrey Borzenkov
Using legacy drivers I can use any SMART tools out there; HDD does support SMART. Running libata +
pata_ali, smartctl claims device does not support SMART. This is sort of regression when switching from legacy drivers.Try smartctl -d ata.
Right, it works. thank you. I wonder if it possible to automatically find the correct device type?
- -andrey
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
iD8DBQFEoSiwR6LMutpd94wRAgTwAKC8l0kOgyrSHQ8S8lwhn1S7HRXU+QCfdsw5 HP5fUV3FjibIDzxvIWQJDU0=
=Mjin
-----END PGP SIGNATURE-----
Quoted 6 lines · Andrey Borzenkov
Quoted 2 lines · Erik Mouw
Try smartctl -d ata.
Right, it works. thank you. I wonder if it possible to automatically find the correct device type?
The current implementation guesses the device type by device name, which apparently doesn't work with libata. I don't know if there's a better way to figure out.
Erik
Signature · 2 lines
+-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 -- | Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands
Quoted 4 lines · Andrey Borzenkov
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1Using legacy drivers I can use any SMART tools out there; HDD does support SMART. Running libata +
pata_ali, smartctl claims device does not support SMART. This is sort of regression when switching from legacy drivers.
If you are using smartmontools, you need to pass "-d ata" to the tools.
Jeff