public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* lib(p)ata SMART support?
@ 2006-06-27 11:55 Andrey Borzenkov
  2006-06-27 12:16 ` Erik Mouw
  2006-06-27 13:40 ` Jeff Garzik
  0 siblings, 2 replies; 5+ messages in thread
From: Andrey Borzenkov @ 2006-06-27 11:55 UTC (permalink / raw)
  To: linux-kernel

-----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-----

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: lib(p)ata SMART support?
  2006-06-27 11:55 lib(p)ata SMART support? Andrey Borzenkov
@ 2006-06-27 12:16 ` Erik Mouw
  2006-06-27 12:46   ` Andrey Borzenkov
  2006-06-27 13:40 ` Jeff Garzik
  1 sibling, 1 reply; 5+ messages in thread
From: Erik Mouw @ 2006-06-27 12:16 UTC (permalink / raw)
  To: Andrey Borzenkov; +Cc: linux-kernel

On Tue, Jun 27, 2006 at 03:55:12PM +0400, Andrey Borzenkov wrote:
> 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

-- 
+-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 --
| Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: lib(p)ata SMART support?
  2006-06-27 12:16 ` Erik Mouw
@ 2006-06-27 12:46   ` Andrey Borzenkov
  2006-06-27 13:34     ` Erik Mouw
  0 siblings, 1 reply; 5+ messages in thread
From: Andrey Borzenkov @ 2006-06-27 12:46 UTC (permalink / raw)
  To: Erik Mouw; +Cc: linux-kernel

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tuesday 27 June 2006 16:16, Erik Mouw wrote:
> On Tue, Jun 27, 2006 at 03:55:12PM +0400, Andrey Borzenkov wrote:
> > 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-----

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: lib(p)ata SMART support?
  2006-06-27 12:46   ` Andrey Borzenkov
@ 2006-06-27 13:34     ` Erik Mouw
  0 siblings, 0 replies; 5+ messages in thread
From: Erik Mouw @ 2006-06-27 13:34 UTC (permalink / raw)
  To: Andrey Borzenkov; +Cc: linux-kernel

On Tue, Jun 27, 2006 at 04:46:39PM +0400, Andrey Borzenkov wrote:
> On Tuesday 27 June 2006 16:16, Erik Mouw wrote:
> > 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

-- 
+-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 --
| Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: lib(p)ata SMART support?
  2006-06-27 11:55 lib(p)ata SMART support? Andrey Borzenkov
  2006-06-27 12:16 ` Erik Mouw
@ 2006-06-27 13:40 ` Jeff Garzik
  1 sibling, 0 replies; 5+ messages in thread
From: Jeff Garzik @ 2006-06-27 13:40 UTC (permalink / raw)
  To: Andrey Borzenkov; +Cc: linux-kernel

Andrey Borzenkov wrote:
> -----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.

If you are using smartmontools, you need to pass "-d ata" to the tools.

	Jeff




^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2006-06-27 13:40 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-06-27 11:55 lib(p)ata SMART support? Andrey Borzenkov
2006-06-27 12:16 ` Erik Mouw
2006-06-27 12:46   ` Andrey Borzenkov
2006-06-27 13:34     ` Erik Mouw
2006-06-27 13:40 ` Jeff Garzik

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox