Udisks and udisks-glue fail to start

Help and Support Raspberry Pi
1

Hi,

on my RPi2 that has been running for months, I cannot access my external HDD anymore. Apparently, udisks and udisks-glue fail to start at boot:

osmc@osmc:~$ sudo systemctl status udisks.service
  • udisks.service - Disk Manager (legacy version)
    Loaded: loaded (/lib/systemd/system/udisks.service; static; vendor preset: enabled)
    Active: failed (Result: signal) since Tue 2018-07-31 08:55:06 CEST; 8min ago
    Docs: man:udisks(7)
    Process: 530 ExecStart=/usr/lib/udisks/udisks-daemon --no-debug (code=killed, signal=SEGV)
    Main PID: 530 (code=killed, signal=SEGV)

Jul 31 08:55:06 osmc systemd[1]: Starting Disk Manager (legacy version)…
Jul 31 08:55:06 osmc systemd[1]: udisks.service: Main process exited, code=killed, status=11/SEGV
Jul 31 08:55:06 osmc systemd[1]: Failed to start Disk Manager (legacy version).
Jul 31 08:55:06 osmc systemd[1]: udisks.service: Unit entered failed state.
Jul 31 08:55:06 osmc systemd[1]: udisks.service: Failed with result ‘signal’.
osmc@osmc:~$ sudo systemctl status udisks-glue.service

  • udisks-glue.service - mount disks automatically with standby
    Loaded: loaded (/lib/systemd/system/udisks-glue.service; enabled; vendor preset: enabled)
    Active: failed (Result: signal) since Tue 2018-07-31 08:54:42 CEST; 8min ago
    Process: 250 ExecStart=/usr/bin/udisks-glue --foreground (code=killed, signal=SEGV)
    Process: 193 ExecStartPre=/bin/bash -c sudo rmdir /media/*/ 2>/dev/null; time udevadm settle; exit 0 (code=exited, status=0/SUCCESS)
    Main PID: 250 (code=killed, signal=SEGV)

Jul 31 08:54:41 osmc systemd[1]: Starting mount disks automatically with standby…
Jul 31 08:54:41 osmc bash[193]: /bin/bash: /dev/null: Permission denied
Jul 31 08:54:42 osmc systemd[1]: Started mount disks automatically with standby.
Jul 31 08:54:42 osmc systemd[1]: udisks-glue.service: Main process exited, code=killed, status=11/SEGV
Jul 31 08:54:42 osmc systemd[1]: udisks-glue.service: Unit entered failed state.
Jul 31 08:54:42 osmc systemd[1]: udisks-glue.service: Failed with result ‘signal’.

This seems like a duplicate of this issue: New install - disk manager (udisks, udisks-glue) fails to start. However, this was resolved by an update from last year, while my system runs the latest stable update.

2

Hi,

We need full logs not snippets to diagnose this issue:

also what does journalctl report?

Thanks tom.

3

Hi,

thanks a lot for the reply. Full logs are available at:

http://paste.osmc.tv/pipametoju

The output of journalctl:

osmc@osmc:~$ journalctl -u udisks.service
– Logs begin at Thu 2016-11-03 18:16:42 CET, end at Tue 2018-07-31 11:07:55 CEST. –
Jul 31 08:55:06 osmc systemd[1]: Starting Disk Manager (legacy version)…
Jul 31 08:55:06 osmc systemd[1]: udisks.service: Main process exited, code=killed, status=11/SEGV
Jul 31 08:55:06 osmc systemd[1]: Failed to start Disk Manager (legacy version).
Jul 31 08:55:06 osmc systemd[1]: udisks.service: Unit entered failed state.
Jul 31 08:55:06 osmc systemd[1]: udisks.service: Failed with result ‘signal’.
osmc@osmc:~$ journalctl -u udisks-glue.service
– Logs begin at Thu 2016-11-03 18:16:42 CET, end at Tue 2018-07-31 11:07:55 CEST. –
Jul 31 08:54:41 osmc systemd[1]: Starting mount disks automatically with standby…
Jul 31 08:54:41 osmc bash[193]: /bin/bash: /dev/null: Permission denied
Jul 31 08:54:42 osmc systemd[1]: Started mount disks automatically with standby.
Jul 31 08:54:42 osmc systemd[1]: udisks-glue.service: Main process exited, code=killed, status=11/SEGV
Jul 31 08:54:42 osmc systemd[1]: udisks-glue.service: Unit entered failed state.
Jul 31 08:54:42 osmc systemd[1]: udisks-glue.service: Failed with result ‘signal’.

Thanks!
Koen

4

Looks like you messed up your repository line

deb http://apt.osmc.tv stretch main universe

5

Hi,

I’m not sure what you mean by that. Even then, when I replace the sources.list by the clean version from here: Osmc update doesn't works - solved! - #9 by ActionA, the system seems up to date:

osmc@osmc:~$ cat /etc/apt/sources.list
deb Index of /debian stretch main contrib non-free

deb Index of /debian stretch-updates main contrib non-free

deb http://security.debian.org/ stretch/updates main contrib non-free

deb http://apt.osmc.tv stretch main
osmc@osmc:~$ sudo apt-get update
Hit:1 http://security.debian.org stretch/updates InRelease
Ign:2 Index of /debian stretch InRelease
Hit:3 Index of /debian stretch-updates InRelease
Hit:5 Index of /debian stretch Release
Hit:4 Index of /osmc/osmc/apt stretch InRelease
Reading package lists… Done
osmc@osmc:~$ sudo apt-get dist-upgrade
Reading package lists… Done
Building dependency tree
Reading state information… Done
Calculating upgrade… Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Koen

6

Well I meant that you have changed the repository line which might have created issues.
But as you seems upto date that seemed not causing any issue.

Only other thing I spotted in the logs is Process '/lib/udev/hdparm' failed with exit code 5. after your external disk is recognized

7

Ok, that might be the issue. Any idea on how to resolve this or process detailed logs on this process?

8

Not really but have you tried with another drive/stick?

9

Yes, both ways actually: the external HDD does work on my Ubuntu laptop, other USB sticks are also not recognized by OSMC.

Udisks fails at boot even when no storage device is attached.

10

Suggest a clean install on a second SD card. If that works than can try to reinstall certain libraries and packages