Created attachment 116525 [details] the output of 'udisksctl dump' I used Gnome Disks to set my 3 hard drives to spin down after 10 minutes of inactivity. The tool created three files in /etc/udisks2/ named: MAXTOR-STM3250310AS-6RY0XFMX.conf SAMSUNG-HD252HJ-S17HJ9CQ716173.conf WDC-WD1002FAEX-00Z3A0-WD-WCATR8328627.conf The content of the three files is the same: # See udisks(8) for the format of this file. [ATA] StandbyTimeout=120 The setting is respected across reboots, but if I suspend my computer, after resuming the disks never spin down. Steps to reproduce: 1. Use Gnome Disks to set the standby timeout of some hard drive to 5 seconds (or edit the file in /etc/udisks2 manually) -> Immediately after saving the file, `udisksctl monitor` says: /org/freedesktop/UDisks2/drives/MAXTOR_STM3250310AS_6RY0XFMX: org.freedesktop.UDisks2.Drive: Properties Changed Configuration: {'ata-pm-standby': <1>} -> Five seconds after saving the file, the drive parks its heads, Gnome Disks shows a 💤 icon, and `hdparm -C /dev/sd?` says 'drive state is: standby' 2. Suspend the computer. 3. Wake up the computer. -> All drives spin up. I think this is inevitable. 4. Wait five seconds. Result: The drive does not spin down. If you issue `hdparm -S 1 /dev/sd?` immediately after resuming the drive does spin down after five seconds. Expected result: The drive always spins down after the specified timeout like it did before suspending.
Created attachment 116526 [details] the output of 'udevadm info --export-db' (as root)
Created attachment 116527 [details] the output of 'cat /proc/self/mountinfo'
Created attachment 116528 [details] the output of 'cat /etc/fstab'
I think this is a duplicate of bug 63041.
I agree. *** This bug has been marked as a duplicate of bug 63041 ***
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.