You are not logged in.
I have an internal hard disk. I automount it by fstab it looks like this:
UUID=54f6de6b-3dc3-47ee-9aaf-68dae250b623 /run/media/navailable/HDD ext4 rw,relatime 0 0
I set Standby timeout 3 minutes and APM (Advanced Power Management) for 50 on gnome-disk-utility but it does not spin down after 3 minutes pass. How to solve this issue? Thanks. ![]()
Last edited by navailable (2022-08-01 20:26:19)
We live in a kingdom of b#shit.
Offline
Stop accessing it.
If there's a lot of data, gnomes file indexer is probably … indexing it.
See whether you can get it to standby or sleep w/ hdparm -y/-Y and try the behavior from a multi-user.target (console) login to get gnome out of the way.
Offline
I don't use Gnome but I have a package named tracker3 is that the reason of indexing? Maybe I can stop indexing.
We live in a kingdom of b#shit.
Offline
The why do you use
on gnome-disk-utility
?
Don't use that, use hdparm.
Is the tracker process running?
Offline
hdparm -y can spin down the drive but it spins up right after that.
tracker is not running.
It only spins down when I unmount it.
We live in a kingdom of b#shit.
Offline
Check "sudo lsof | grep 'navailable/HDD'" - something™ is accessing the drive.
Offline
tried sudo lsof | grep 'run/media/navailable/HDD'
it says: lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs
Output information may be incomplete.
We live in a kingdom of b#shit.
Offline
Since there's some gvfs, try from the multi-user.target still (just to figure whether this is by some session tool or eg. upower/udisks - make sure there's no graphical session, don't just switch the VT)
Offline
Finally It spun down after some couple hours maybe there was some indexing. Solved!
This is how it looks in fstab
UUID=c306d357-94a5-4da3-bc22-198525e6a902 /run/media/navailable/HDD ext4 rw,relatime 0 0We live in a kingdom of b#shit.
Offline