![](https://seccdn.libravatar.org/avatar/abdee805d4df05af9a496107100c582c.jpg?s=120&d=mm&r=g)
* Patrick Shanahan <paka@opensuse.org> [11-11-19 13:50]:
* Andrei Borzenkov <arvidjaar@gmail.com> [11-11-19 13:14]:
11.11.2019 16:37, Patrick Shanahan пишет:
short relief, one reboot and failed on next.
attempting systemctl reload udisks2.service provides: http://wahoo.no-ip.org/~paka/udisks2.fail1.txt
and polkit.service is loaded/running
systemctl status udisks2.service provides: 08:34 crash: ~ # systemctl status udisks2.service ● udisks2.service - Disk Manager Loaded: loaded (/usr/lib/systemd/system/udisks2.service; disabled; vendor preset: disabled) Active: failed (Result: timeout) since Mon 2019-11-11 08:31:26 EST; 3min 8s ago Docs: man:udisks(8) Process: 31577 ExecStart=/usr/lib/udisks2/udisksd (code=killed, signal=KILL) Main PID: 31577 (code=killed, signal=KILL)
Nov 11 08:28:26 crash udisksd[31577]: udisks daemon version 2.8.3 starting Nov 11 08:28:26 crash udisksd[31577]: Can't load configuration file /etc/udisks2/udisks2.conf Nov 11 08:29:56 crash systemd[1]: udisks2.service: start operation timed out. Terminating. Nov 11 08:31:26 crash systemd[1]: udisks2.service: State 'stop-sigterm' timed out. Killing. Nov 11 08:31:26 crash systemd[1]: udisks2.service: Killing process 31577 (udisksd) with signal SIGKILL. Nov 11 08:31:26 crash systemd[1]: udisks2.service: Killing process 31723 (xfs_info) with signal SIGKILL. Nov 11 08:31:26 crash systemd[1]: udisks2.service: Killing process 31730 (xfs_spaceman) with signal SIGKILL.
Sounds like you have filesystem/disk issues so commands querying filesystem hang.
Nov 11 08:31:26 crash systemd[1]: udisks2.service: Main process exited, code=killed, status=9/KILL Nov 11 08:31:26 crash systemd[1]: udisks2.service: Failed with result 'timeout'. Nov 11 08:31:26 crash systemd[1]: Failed to start Disk Manager.
so disable all unnecessary mounts and re-enable one at a time until similar failure or should fresh logs after reboot give an indication?
and the result is errant cifs/sshfs mounts to a recently updated win10 box. windoz continually creates problems. tks for the help and path, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org