Activity log for bug #1733068

Date Who What changed Old value New value Message
2017-11-18 13:06:56 paoletto bug added bug
2017-11-18 13:09:21 paoletto description On Ubuntu 16.04, if i plug in a USB drive, then unmount it (eject button) in nautilus, then force it to sleep (hdparm -y), the drive reports to be in standby: hdparm -C /dev/sdd /dev/sdd: drive state is: standby However, after some time during which i have not tried to access the drive, the drive seems to spin up again, and reports to be active again: hdparm -C /dev/sdd /dev/sdd: drive state is: active/idle I have been researching on google, askubuntu, irc, but apparently nobody has been able to tell what is that wakes up the drive. Everybody say that if the drive is unmounted, it should stay sleeping. Note: I also tried to add the drive partitions in fstab, so to force gvfs to ignore the drive. Even this failed to keep the drive sleeping. I have not been able to test this on 14.04 yet, but 14.04 successfully keeps internal SATA drives asleep even when mounted unless i explicitly access them. On Ubuntu 16.04, if i plug in a USB drive, then unmount it (eject button) in nautilus, then force it to sleep (hdparm -y), the drive reports to be in standby: hdparm -C /dev/sdd /dev/sdd:  drive state is: standby However, after some time during which i have not tried to access the drive, the drive seems to spin up again, and reports to be active again: hdparm -C /dev/sdd /dev/sdd:  drive state is: active/idle I have been researching on google, askubuntu, irc, but apparently nobody has been able to tell what is that wakes up the drive. Everybody say that if the drive is unmounted, it should stay sleeping. Note: I also tried to add the drive partitions in fstab, so to force gvfs to ignore the drive. Even this failed to keep the drive sleeping. I have not been able to test this on 14.04 yet, but 14.04 successfully keeps internal SATA drives asleep even when mounted unless i explicitly access them. One additional question i would have, at this point, is also whether there is some tool to check what process tries to access the device. Or some sort of tcpdump for SATA..
2017-11-18 16:22:21 Ubuntu Foundations Team Bug Bot tags bot-comment
2017-11-19 17:27:36 paoletto bug added subscriber Phillip Susi
2017-11-20 16:18:57 Brian Murray tags bot-comment bot-comment xenial
2017-11-20 16:19:25 Brian Murray affects ubuntu nautilus (Ubuntu)
2017-11-23 21:51:06 Sebastien Bacher affects nautilus (Ubuntu) ubuntu
2017-12-07 14:59:11 paoletto bug watch added https://bugzilla.redhat.com/show_bug.cgi?id=1351305
2017-12-16 16:59:36 paoletto description On Ubuntu 16.04, if i plug in a USB drive, then unmount it (eject button) in nautilus, then force it to sleep (hdparm -y), the drive reports to be in standby: hdparm -C /dev/sdd /dev/sdd:  drive state is: standby However, after some time during which i have not tried to access the drive, the drive seems to spin up again, and reports to be active again: hdparm -C /dev/sdd /dev/sdd:  drive state is: active/idle I have been researching on google, askubuntu, irc, but apparently nobody has been able to tell what is that wakes up the drive. Everybody say that if the drive is unmounted, it should stay sleeping. Note: I also tried to add the drive partitions in fstab, so to force gvfs to ignore the drive. Even this failed to keep the drive sleeping. I have not been able to test this on 14.04 yet, but 14.04 successfully keeps internal SATA drives asleep even when mounted unless i explicitly access them. One additional question i would have, at this point, is also whether there is some tool to check what process tries to access the device. Or some sort of tcpdump for SATA.. On Ubuntu 16.04, if i plug in a USB drive, then unmount it (eject button) in nautilus, then force it to sleep (hdparm -y), the drive reports to be in standby: hdparm -C /dev/sdd /dev/sdd:  drive state is: standby However, after some time during which i have not tried to access the drive, the drive seems to spin up again, and reports to be active again: hdparm -C /dev/sdd /dev/sdd:  drive state is: active/idle I have been researching on google, askubuntu, irc, but apparently nobody has been able to tell what is that wakes up the drive. Everybody say that if the drive is unmounted, it should stay sleeping. Note: I also tried to add the drive partitions in fstab, so to force gvfs to ignore the drive. Even this failed to keep the drive sleeping. I have not been able to test this on 14.04 yet, but 14.04 successfully keeps internal SATA drives asleep even when mounted unless i explicitly access them. One additional question i would have, at this point, is also whether there is some tool to check what process tries to access the device. Or some sort of tcpdump for SATA.. *UPDATE* I managed to test this on 14.04, and as expected, the disk spins down almost immediately, and stays spun down, and after approximately half hour (maybe less) it goes in standby (disk led blinking regularly: http://gph.is/2yKy20M) and stays like that. Also, unlike 16.04, dmesg stays clean without repeating messages about meaningless driver sense errors
2017-12-16 17:15:03 paoletto bug added subscriber Alan Stern
2023-06-02 11:25:26 Paul White bug added subscriber Paul White
2023-06-02 11:26:07 Paul White ubuntu: status New Incomplete
2023-08-03 10:51:34 Paul White ubuntu: status Incomplete Invalid