I have an at least similar issue on 12.10 quantal with spindown: I want to spin down my external USB drive /dev/sdc as fast as possible: in /etc/hdparm.conf:
/dev/sdc { spindown_time = 1 }
that works, although I get
$ sudo hdparm -C /dev/sdc /dev/sdc: SG_IO: bad/missing sense data, sb[]: f0 00 01 00 50 40 00 0a 00 00 00 00 00 1d 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 drive state is: unknown
but after resume from suspend, it doesn't work anymore.
my workaround is /etc/pm/sleep.d/20-hdparm
#!/bin/bash case "$1" in thaw|resume) hdparm -S 1 /dev/sdc ;;
esac
and that works, anyway, spindown settings shouldn't get lost on suspend/resume in the first place.
So what is most reasonable? * Deal with that issue in this bug? * Reopen bug https://bugs.launchpad.net/ubuntu/+source/hdparm/+bug/738757 which is closer to the problem I got? * Open a new bug?
I have an at least similar issue on 12.10 quantal with spindown:
I want to spin down my external USB drive /dev/sdc as fast as possible:
in /etc/hdparm.conf:
/dev/sdc {
spindown_time = 1
}
that works, although I get
$ sudo hdparm -C /dev/sdc
/dev/sdc:
SG_IO: bad/missing sense data, sb[]: f0 00 01 00 50 40 00 0a 00 00 00 00 00 1d 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
drive state is: unknown
but after resume from suspend, it doesn't work anymore.
my workaround is sleep.d/ 20-hdparm
/etc/pm/
#!/bin/bash
case "$1" in
thaw|resume)
hdparm -S 1 /dev/sdc
;;
esac
and that works, anyway, spindown settings shouldn't get lost on suspend/resume in the first place.
So what is most reasonable? /bugs.launchpad .net/ubuntu/ +source/ hdparm/ +bug/738757 which is closer to the problem I got?
* Deal with that issue in this bug?
* Reopen bug https:/
* Open a new bug?