Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#72543 - [udisks2] udisks spins up hdd every 10 minutes
Attached to Project:
Arch Linux
Opened by Vladislav Tyulbashev (vtyulb) - Monday, 25 October 2021, 20:26 GMT
Last edited by Balló György (City-busz) - Tuesday, 06 June 2023, 11:50 GMT
Opened by Vladislav Tyulbashev (vtyulb) - Monday, 25 October 2021, 20:26 GMT
Last edited by Balló György (City-busz) - Tuesday, 06 June 2023, 11:50 GMT
|
DetailsProblem exists in udisks2-2.9.4-1
I think that everything is broken since october 2021 (problem was never seen before), however downgrading to 2.9.1 did not help (or there was yet another problem with that version). Udisks just looking some smart metadata from every disk every 10 minutes, which spins up unused hdd drive. This is very loud and annoying. Moreover it will probably kill hdd soon enough. Logs: journalctl for sda events: https://pastebin.com/cbqKDh2a # fatrace udisksd(6326): O / udisksd(6326): C / udisksd(6326): CO / udisksd(6326): CO / udisksd(6326): CO / udisksd(6326): CO / udisksd(6326): CO / udisksd(6326): CO / udisksd(6326): O / udisksd(6326): C / udisksd(6326): CO / Manual workaround for survival: smartctl --smart=off /dev/sda Thread at manjaro forum: https://forum.manjaro.org/t/hdd-spinning-up-every-10min/86381/51 Same bug at ubuntu tracker: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1373318 Same bug at github: https://github.com/storaged-project/udisks/issues/407 I propose applying old patch from github to our udisks2 version. |
This task depends upon
Comment by Balló György (City-busz) -
Tuesday, 06 June 2023, 11:50 GMT
This is an upstream bug, and no patches are accepted by upstream yet.