Comment 82 for bug 435190

(In reply to comment #8)
> Interesting. Please try to boot into runlevel 3 (to avoid the desktop starting
> devkit-disks-daemon), ensure that devkit-disks-daemon isn't running and then
> put the drive asleep (or wait until it is asleep). Then as root run this
> command

I killed devkit-disks-daemon, and used hdparm 9.15's -S option to set the timeout to 5 seconds, then waited at least that amount of time.

> # /usr/libexec/devkit-disks-helper-ata-smart-collect /dev/sdb 1
>
> replacing /dev/sdb with whatever disk it is. If the drive is asleep we should
> print
>
> Disk /dev/sdb is asleep and nowakeup option was passed
>
> and exit with exit code 2. Otherwise it will dump a base64 encoded blob of the
> smart data to stdout and exit with exit code 0.

I did this, and heard the drive spin up, and shortly afterwards I got the base64 blob.

> If this wakes up the disk it's probably a libatasmart bug - we've already
> identified a few issues with detecting whether a disk is asleep/awake in
> libatasmart (which is why I'm adding the libatasmart author to the Cc).

libatasmart 0.12-3.fc11 and DeviceKit-disks-004-3.fc11 here.