SATL support for hdparm?

SATL support for hdparm?

[Lennert Buytenhek]

[ please CC, not on the list ]

Hi,

I have a bunch of SATA disks hanging off a SAS expander on which I
would like to disable APM (using hdparm -B).  This doesn't work as-is,
and from reading:

	http://smartmontools.sourceforge.net/smartmontools_scsi.html

it appears that I'd need to hack hdparm to use the ATA PASS THROUGH
SCSI command to make it talk to SATA disks behind a SAS expander, as
was already done for smartctl.  Did anyone implement something like
this for hdparm yet by any chance?


thanks,
Lennert

Re: SATL support for hdparm?

[Mark Lord]

Lennert Buytenhek wrote:
> [ please CC, not on the list ]
> 
> Hi,
> 
> I have a bunch of SATA disks hanging off a SAS expander on which I
> would like to disable APM (using hdparm -B).  This doesn't work as-is,
> and from reading:
> 
> 	http://smartmontools.sourceforge.net/smartmontools_scsi.html
> 
> it appears that I'd need to hack hdparm to use the ATA PASS THROUGH
> SCSI command to make it talk to SATA disks behind a SAS expander, as
> was already done for smartctl.  Did anyone implement something like
> this for hdparm yet by any chance?
..

It actually does that already.  What version are you trying with?
Grab the latest from sourceforge (9.10 or 9.11) and try again.

If it still doesn't work with that, then let me know and we'll sort it out.

Cheers
-- 
Mark Lord
Real-Time Remedies Inc.
mlord@pobox.com

Re: SATL support for hdparm?

[Lennert Buytenhek]

On Sat, Feb 14, 2009 at 06:57:33PM -0500, Mark Lord wrote:

> > I have a bunch of SATA disks hanging off a SAS expander on which I
> > would like to disable APM (using hdparm -B).  This doesn't work as-is,
> > and from reading:
> >
> >	http://smartmontools.sourceforge.net/smartmontools_scsi.html
> >
> > it appears that I'd need to hack hdparm to use the ATA PASS THROUGH
> > SCSI command to make it talk to SATA disks behind a SAS expander, as
> > was already done for smartctl.  Did anyone implement something like
> > this for hdparm yet by any chance?
> 
> It actually does that already.  What version are you trying with?

I tried with 9.10.  Ah yes, now I see that the man page mentions SAT,
but it doesn't appear to be detecting that it needs to do that.


> Grab the latest from sourceforge (9.10 or 9.11) and try again.
> 
> If it still doesn't work with that, then let me know and we'll sort
> it out.

I get this when trying to set -B 254 (in an attempt to turn off head
unload/load -- these are WD drives that do that quite frequently):

	[root@heth hdparm-9.10]# ./hdparm -B 254 /dev/sdb

	/dev/sdb:
	 setting Advanced Power Management level to 0xfe (254)
	 HDIO_DRIVE_CMD failed: Input/output error
	[root@heth hdparm-9.10]# 

I don't see it issuing any SG_IO ioctls with command byte being 0xA1
or 0xA5 -- I don't see it issuing SG_IO at all:

	[...]
	open("/dev/sdb", O_RDONLY|O_NONBLOCK)   = 3
	fstat(1, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 2), ...}) = 0
	mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x2b9e17076000
	write(1, "\n", 1)                       = 1
	write(1, "/dev/sdb:\n", 10)             = 10
	write(1, " setting Advanced Power Manageme"..., 55) = 55
	ioctl(3, 0x31f, 0x7fff93a336b0)         = -1 EINVAL (Invalid argument)
	dup(2)                                  = 4
	fcntl(4, F_GETFL)                       = 0x8002 (flags O_RDWR|O_LARGEFILE)
	brk(0)                                  = 0xf97b000
	brk(0xf99c000)                          = 0xf99c000
	fstat(4, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 2), ...}) = 0
	mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x2b9e17077000
	lseek(4, 0, SEEK_CUR)                   = -1 ESPIPE (Illegal seek)
	write(4, " HDIO_DRIVE_CMD failed: Invalid "..., 41) = 41
	close(4)                                = 0
	munmap(0x2b9e17077000, 4096)            = 0
	close(3)                                = 0
	exit_group(0)                           = ?

Re: SATL support for hdparm?

[Mark Lord]

Lennert Buytenhek wrote:
> On Sat, Feb 14, 2009 at 06:57:33PM -0500, Mark Lord wrote:
> 
>>> I have a bunch of SATA disks hanging off a SAS expander on which I
>>> would like to disable APM (using hdparm -B).  This doesn't work as-is,
>>> and from reading:
>>>
>>> 	http://smartmontools.sourceforge.net/smartmontools_scsi.html
>>>
>>> it appears that I'd need to hack hdparm to use the ATA PASS THROUGH
>>> SCSI command to make it talk to SATA disks behind a SAS expander, as
>>> was already done for smartctl.  Did anyone implement something like
>>> this for hdparm yet by any chance?
>> It actually does that already.  What version are you trying with?
> 
> I tried with 9.10.  Ah yes, now I see that the man page mentions SAT,
> but it doesn't appear to be detecting that it needs to do that.
> 
> 
>> Grab the latest from sourceforge (9.10 or 9.11) and try again.
>>
>> If it still doesn't work with that, then let me know and we'll sort
>> it out.
> 
> I get this when trying to set -B 254 (in an attempt to turn off head
> unload/load -- these are WD drives that do that quite frequently):
> 
> 	[root@heth hdparm-9.10]# ./hdparm -B 254 /dev/sdb
> 
> 	/dev/sdb:
> 	 setting Advanced Power Management level to 0xfe (254)
> 	 HDIO_DRIVE_CMD failed: Input/output error
> 	[root@heth hdparm-9.10]# 
> 
> I don't see it issuing any SG_IO ioctls with command byte being 0xA1
> or 0xA5 -- I don't see it issuing SG_IO at all:
..

That would be because it didn't see SG_IO defined in the header files
against which it was compiled.  Have a look at your /usr/include/scsi/sg.h
file and ensure it has SG_IO defined in there.

Cheers
-- 
Mark Lord
Real-Time Remedies Inc.
mlord@pobox.com

Re: SATL support for hdparm?

[Lennert Buytenhek]

On Sat, Feb 14, 2009 at 07:09:12PM -0500, Mark Lord wrote:

> >>>I have a bunch of SATA disks hanging off a SAS expander on which I
> >>>would like to disable APM (using hdparm -B).  This doesn't work as-is,
> >>>and from reading:
> >>>
> >>>	http://smartmontools.sourceforge.net/smartmontools_scsi.html
> >>>
> >>>it appears that I'd need to hack hdparm to use the ATA PASS THROUGH
> >>>SCSI command to make it talk to SATA disks behind a SAS expander, as
> >>>was already done for smartctl.  Did anyone implement something like
> >>>this for hdparm yet by any chance?
> >>It actually does that already.  What version are you trying with?
> >
> >I tried with 9.10.  Ah yes, now I see that the man page mentions SAT,
> >but it doesn't appear to be detecting that it needs to do that.
> >
> >
> >>Grab the latest from sourceforge (9.10 or 9.11) and try again.
> >>
> >>If it still doesn't work with that, then let me know and we'll sort
> >>it out.
> >
> >I get this when trying to set -B 254 (in an attempt to turn off head
> >unload/load -- these are WD drives that do that quite frequently):
> >
> >	[root@heth hdparm-9.10]# ./hdparm -B 254 /dev/sdb
> >
> >	/dev/sdb:
> >	 setting Advanced Power Management level to 0xfe (254)
> >	 HDIO_DRIVE_CMD failed: Input/output error
> >	[root@heth hdparm-9.10]# 
> >
> >I don't see it issuing any SG_IO ioctls with command byte being 0xA1
> >or 0xA5 -- I don't see it issuing SG_IO at all:
> 
> That would be because it didn't see SG_IO defined in the header files
> against which it was compiled.  Have a look at your /usr/include/scsi/sg.h
> file and ensure it has SG_IO defined in there.

Well, it does seem to have those:

	[root@heth hdparm-9.10]# grep SG_IO /usr/include/scsi/sg.h
	    char orphan;        /* 0 -> normal request, 1 -> from interruped SG_IO */
	    char sg_io_owned;   /* 0 -> complete with read(), 1 -> owned by SG_IO */
	#define SG_IO 0x2285   /* similar effect as write() followed by read() */
	/* How to treat EINTR during SG_IO ioctl(), only in SG 3.x series */
	[root@heth hdparm-9.10]# strings hdparm | grep SG_IO
	ioctl(fd,SG_IO)
	SG_IO: sb[]
	SG_IO: desc[]
	SG_IO: ATA_%u status=0x%x, host_status=0x%x, driver_status=0x%x
	SG_IO: bad response (not CHECK_CONDITION)
	SG_IO: bad/missing sense data, sb[]
	[root@heth hdparm-9.10]# 

Turns out I was stracing /sbin/hdparm and not ./hdparm (doh).  If I
strace the right binary I get:

	ioctl(3, SG_IO, {'S', SG_DXFER_NONE, cmd[12]=[a1, 06, 20, 05, fd, 00, 00, 00, 40, ef, 00, 00], mx_sb_len=32, iovec_count=0, dxfer_len=0, timeout=5000, flags=0, status=02, masked_status=01, sb[22]=[72, 0b, 00, 00, 00, 00, 00, 0e, 09, 0c, 00, 04, 00, fd, 00, 00, 00, 00, 00, 00, 40, 51], host_status=0, driver_status=0x8, resid=0, duration=1, info=0x1}) = 0

Does that mean the drive doesn't support SET_FEATURES/{05,85} (weird)?

Re: SATL support for hdparm?

[Douglas Gilbert]

Lennert Buytenhek wrote:
> [ please CC, not on the list ]
> 
> Hi,
> 
> I have a bunch of SATA disks hanging off a SAS expander on which I
> would like to disable APM (using hdparm -B).  This doesn't work as-is,
> and from reading:
> 
> 	http://smartmontools.sourceforge.net/smartmontools_scsi.html
> 
> it appears that I'd need to hack hdparm to use the ATA PASS THROUGH
> SCSI command to make it talk to SATA disks behind a SAS expander, as
> was already done for smartctl.  Did anyone implement something like
> this for hdparm yet by any chance?

I need to update that document to state that later versions
of hdparm do indeed use the SAT pass-through mechanism and
hdparm should work in your situation.

So follow Mark Lord's advice.

Doug Gilbert

Re: SATL support for hdparm?

[Mark Lord]

Lennert Buytenhek wrote:
..
> Turns out I was stracing /sbin/hdparm and not ./hdparm (doh).  If I
> strace the right binary I get:
> 
> 	ioctl(3, SG_IO, {'S', SG_DXFER_NONE, cmd[12]=[a1, 06, 20, 05, fd, 00, 00, 00, 40, ef, 00, 00], mx_sb_len=32, iovec_count=0, dxfer_len=0, timeout=5000, flags=0, status=02, masked_status=01, sb[22]=[72, 0b, 00, 00, 00, 00, 00, 0e, 09, 0c, 00, 04, 00, fd, 00, 00, 00, 00, 00, 00, 40, 51], host_status=0, driver_status=0x8, resid=0, duration=1, info=0x1}) = 0
> 
> Does that mean the drive doesn't support SET_FEATURES/{05,85} (weird)?
..

Dunno.. do this instead, and show the output:

  hdparm --verbose -B /dev/sdb

-- 
Mark Lord
Real-Time Remedies Inc.
mlord@pobox.com

Re: SATL support for hdparm?

[Mark Lord]

Lennert Buytenhek wrote:
..
>>> 	[root@heth hdparm-9.10]# ./hdparm -B 254 /dev/sdb
..
> 	ioctl(3, SG_IO, {'S', SG_DXFER_NONE, cmd[12]=[a1, 06, 20, 05, fd, 00, 00, 00, 40, ef, 00, 00], mx_sb_len=32, iovec_count=0, dxfer_len=0, timeout=5000, flags=0, status=02, masked_status=01, sb[22]=[72, 0b, 00, 00, 00, 00, 00, 0e, 09, 0c, 00, 04, 00, fd, 00, 00, 00, 00, 00, 00, 40, 51], host_status=0, driver_status=0x8, resid=0, duration=1, info=0x1}) = 0
> 
> Does that mean the drive doesn't support SET_FEATURES/{05,85} (weird)?
..

The -I (IDENTIFY) flag will tell whether the drive supports Advanced Power 
Management, so try that.

Also, not all drives like 254.  To turn it off, use -B 255 instead.

Cheers
-- 
Mark Lord
Real-Time Remedies Inc.
mlord@pobox.com

Re: SATL support for hdparm?

[Lennert Buytenhek]

On Sat, Feb 14, 2009 at 07:15:36PM -0500, Mark Lord wrote:

> >Turns out I was stracing /sbin/hdparm and not ./hdparm (doh).  If I
> >strace the right binary I get:
> >
> >	ioctl(3, SG_IO, {'S', SG_DXFER_NONE, cmd[12]=[a1, 06, 20, 05, fd, 
> >	00, 00, 00, 40, ef, 00, 00], mx_sb_len=32, iovec_count=0, 
> >	dxfer_len=0, timeout=5000, flags=0, status=02, masked_status=01, 
> >	sb[22]=[72, 0b, 00, 00, 00, 00, 00, 0e, 09, 0c, 00, 04, 00, fd, 00, 
> >	00, 00, 00, 00, 00, 40, 51], host_status=0, driver_status=0x8, 
> >	resid=0, duration=1, info=0x1}) = 0
> >
> >Does that mean the drive doesn't support SET_FEATURES/{05,85} (weird)?
> ..
> 
> Dunno.. do this instead, and show the output:
> 
>  hdparm --verbose -B /dev/sdb

	[root@heth hdparm-9.10]# ./hdparm --verbose -B 254 /dev/sdb

	/dev/sdb:
	 setting Advanced Power Management level to 0xfe (254)
	outgoing cdb:  a1 06 20 05 fe 00 00 00 40 ef 00 00 00 00 00 00
	SG_IO: ATA_12 status=0x2, host_status=0x0, driver_status=0x8
	SG_IO: sb[]:  72 0b 00 00 00 00 00 0e 09 0c 00 04 00 fe 00 00 00 00 00 00 40 51 00 00 00 00 00 00 00 00 00 00
	SG_IO: desc[]:  09 0c 00 04 00 fe 00 00 00 00 00 00
	      ATA_12 stat=51 err=04 nsect=fe lbal=00 lbam=00 lbah=00 dev=40
	I/O error, ata_op=0xef ata_status=0x51 ata_error=0x04
	 HDIO_DRIVE_CMD failed: Input/output error
	[root@heth hdparm-9.10]# 

Re: SATL support for hdparm?

[Lennert Buytenhek]

On Sat, Feb 14, 2009 at 07:17:35PM -0500, Mark Lord wrote:

> >>>	[root@heth hdparm-9.10]# ./hdparm -B 254 /dev/sdb
> ..
> >	ioctl(3, SG_IO, {'S', SG_DXFER_NONE, cmd[12]=[a1, 06, 20, 05, fd, 
> >	00, 00, 00, 40, ef, 00, 00], mx_sb_len=32, iovec_count=0, 
> >	dxfer_len=0, timeout=5000, flags=0, status=02, masked_status=01, 
> >	sb[22]=[72, 0b, 00, 00, 00, 00, 00, 0e, 09, 0c, 00, 04, 00, fd, 00, 
> >	00, 00, 00, 00, 00, 40, 51], host_status=0, driver_status=0x8, 
> >	resid=0, duration=1, info=0x1}) = 0
> >
> >Does that mean the drive doesn't support SET_FEATURES/{05,85} (weird)?
> ..
> 
> The -I (IDENTIFY) flag will tell whether the drive supports Advanced Power 
> Management, so try that.
> 
> Also, not all drives like 254.  To turn it off, use -B 255 instead.

-B 255 gives the same thing.  -I gives:

/dev/sdb:

ATA device, with non-removable media
        Model Number:       WDC WD10EACS-00C7B0                     
        Serial Number:      WD-WCASJ2076861
        Firmware Revision:  01.01B01
        Transport:          Serial, SATA 1.0a, SATA II Extensions, SATA Rev 2.5
Standards:
        Supported: 8 7 6 5 
        Likely used: 8
Configuration:
        Logical         max     current
        cylinders       16383   16383
        heads           16      16
        sectors/track   63      63
        --
        CHS current addressable sectors:   16514064
        LBA    user addressable sectors:  268435455
        LBA48  user addressable sectors: 1953525168
        device size with M = 1024*1024:      953869 MBytes
        device size with M = 1000*1000:     1000204 MBytes (1000 GB)
        cache/buffer size  = 16384 KBytes
Capabilities:
        LBA, IORDY(can be disabled)
        Queue depth: 32
        Standby timer values: spec'd by Standard, with device specific minimum
        R/W multiple sector transfer: Max = 16  Current = 0
        Recommended acoustic management value: 128, current value: 254
        DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6 
             Cycle time: min=120ns recommended=120ns
        PIO: pio0 pio1 pio2 pio3 pio4 
             Cycle time: no flow control=120ns  IORDY flow control=120ns
Commands/features:
        Enabled Supported:
           *    SMART feature set
                Security Mode feature set
           *    Power Management feature set
           *    Write cache
           *    Look-ahead
           *    Host Protected Area feature set
           *    WRITE_BUFFER command
           *    READ_BUFFER command
           *    NOP cmd
           *    DOWNLOAD_MICROCODE
                Power-Up In Standby feature set
           *    SET_FEATURES required to spinup after power up
                SET_MAX security extension
                Automatic Acoustic Management feature set
           *    48-bit Address feature set
           *    Device Configuration Overlay feature set
           *    Mandatory FLUSH_CACHE
           *    FLUSH_CACHE_EXT
           *    SMART error logging
           *    SMART self-test
           *    General Purpose Logging feature set
           *    WRITE_{DMA|MULTIPLE}_FUA_EXT
           *    64-bit World wide name
           *    WRITE_UNCORRECTABLE_EXT command
           *    {READ,WRITE}_DMA_EXT_GPL commands
           *    Segmented DOWNLOAD_MICROCODE
           *    SATA-I signaling speed (1.5Gb/s)
           *    SATA-II signaling speed (3.0Gb/s)
           *    Native Command Queueing (NCQ)
           *    Phy event counters
                DMA Setup Auto-Activate optimization
           *    Software settings preservation
           *    SMART Command Transport (SCT) feature set
           *    SCT Long Sector Access (AC1)
           *    SCT LBA Segment Access (AC2)
           *    SCT Error Recovery Control (AC3)
           *    SCT Features Control (AC4)
           *    SCT Data Tables (AC5)
                unknown 206[12] (vendor specific)
                unknown 206[13] (vendor specific)
Security: 
        Master password revision code = 65534
                supported
        not     enabled
        not     locked
        not     frozen
        not     expired: security count
                supported: enhanced erase
        276min for SECURITY ERASE UNIT. 276min for ENHANCED SECURITY ERASE UNIT.
Logical Unit WWN Device Identifier: 50014ee2576dc3c6
        NAA             : 5
        IEEE OUI        : 0014ee
        Unique ID       : 2576dc3c6
Checksum: correct


cheers,
Lennert

Re: SATL support for hdparm?

[Mark Lord]

Lennert Buytenhek wrote:
,,
>>  hdparm --verbose -B /dev/sdb
> 
> 	[root@heth hdparm-9.10]# ./hdparm --verbose -B 254 /dev/sdb
> 
> 	/dev/sdb:
> 	 setting Advanced Power Management level to 0xfe (254)
> 	outgoing cdb:  a1 06 20 05 fe 00 00 00 40 ef 00 00 00 00 00 00
> 	SG_IO: ATA_12 status=0x2, host_status=0x0, driver_status=0x8
> 	SG_IO: sb[]:  72 0b 00 00 00 00 00 0e 09 0c 00 04 00 fe 00 00 00 00 00 00 40 51 00 00 00 00 00 00 00 00 00 00
> 	SG_IO: desc[]:  09 0c 00 04 00 fe 00 00 00 00 00 00
> 	      ATA_12 stat=51 err=04 nsect=fe lbal=00 lbam=00 lbah=00 dev=40
..

Ahh.. there ya go.  Mmmm.. You *could* try again with hdparm-9.11
(on Sourceforge now.. forgot to upload it earlier).

The difference being, 9.11 will use ATA_16 instead of ATA_12 by default for SAT.
Some enclosures care about that, but drives shouldn't care.

Cheers
-- 
Mark Lord
Real-Time Remedies Inc.
mlord@pobox.com

Re: SATL support for hdparm?

[Mark Lord]

Ahh.. yes, that drive does NOT support -B.
It is missing this feature:

            *    Advanced Power Management feature set

Cheers
-- 
Mark Lord
Real-Time Remedies Inc.
mlord@pobox.com

Re: SATL support for hdparm?

[Lennert Buytenhek]

On Sat, Feb 14, 2009 at 07:20:20PM -0500, Mark Lord wrote:

> >> hdparm --verbose -B /dev/sdb
> >
> >	[root@heth hdparm-9.10]# ./hdparm --verbose -B 254 /dev/sdb
> >
> >	/dev/sdb:
> >	 setting Advanced Power Management level to 0xfe (254)
> >	outgoing cdb:  a1 06 20 05 fe 00 00 00 40 ef 00 00 00 00 00 00
> >	SG_IO: ATA_12 status=0x2, host_status=0x0, driver_status=0x8
> >	SG_IO: sb[]:  72 0b 00 00 00 00 00 0e 09 0c 00 04 00 fe 00 00 00 00 
> >	00 00 40 51 00 00 00 00 00 00 00 00 00 00
> >	SG_IO: desc[]:  09 0c 00 04 00 fe 00 00 00 00 00 00
> >	      ATA_12 stat=51 err=04 nsect=fe lbal=00 lbam=00 lbah=00 dev=40
> ..
> 
> Ahh.. there ya go.  Mmmm.. You *could* try again with hdparm-9.11
> (on Sourceforge now.. forgot to upload it earlier).
> 
> The difference being, 9.11 will use ATA_16 instead of ATA_12 by default for 
> SAT.
> Some enclosures care about that, but drives shouldn't care.

OK, that gives the same error:

	[root@heth hdparm-9.11]# ./hdparm -B 254 --verbose /dev/sdb

	/dev/sdb:
	 setting Advanced Power Management level to 0xfe (254)
	outgoing cdb:  85 06 20 00 05 00 fe 00 00 00 00 00 00 40 ef 00
	SG_IO: ATA_16 status=0x2, host_status=0x0, driver_status=0x8
	SG_IO: sb[]:  72 0b 00 00 00 00 00 0e 09 0c 00 04 00 fe 00 00 00 00 00 00 40 51 00 00 00 00 00 00 00 00 00 00
	SG_IO: desc[]:  09 0c 00 04 00 fe 00 00 00 00 00 00
	      ATA_16 stat=51 err=04 nsect=fe lbal=00 lbam=00 lbah=00 dev=40
	I/O error, ata_op=0xef ata_status=0x51 ata_error=0x04
	 HDIO_DRIVE_CMD failed: Input/output error
	[root@heth hdparm-9.11]# 

Re: SATL support for hdparm?

[Lennert Buytenhek]

On Sat, Feb 14, 2009 at 07:21:17PM -0500, Mark Lord wrote:

> Ahh.. yes, that drive does NOT support -B.
> It is missing this feature:
> 
>            *    Advanced Power Management feature set

Doh.  Thanks for the help, and sorry for the noise.

*tries to figure out how to get a firmware upgrade*


cheers,
Lennert