Siduction Forum > Software - Support

 udisks2.service

(1/3) > >>

unklarer:
Moin!

Seit längerer Zeit habe ich auf einem Desktop mit der LXDE -und auch KDE-Plasma Installation ein identisches Problem mit den Startzeiten. Das hier ist noch moderat:

--- Code: ---$ systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

graphical.target @36.796s
└─udisks2.service @20.111s +16.685s
  └─basic.target @19.951s
    └─paths.target @19.951s
      └─cups.path @19.950s
        └─sysinit.target @19.725s
          └─systemd-timesyncd.service @16.992s +2.732s
            └─systemd-tmpfiles-setup.service @16.360s +513ms
              └─local-fs.target @16.353s
                └─media-DATEN.mount @16.199s +152ms
                  └─dev-sda6.device @16.170s
--- End code ---

Die Systeme sind beide bis dato aktuell.

--- Code: ---$ inxi -SMD
System:    Host: sidLXDE Kernel: 5.1.18-towo.1-siduction-amd64 x86_64 bits: 64 Desktop: LXDE 0.10.0
           Distro: siduction 15.1.0 Paint It Black - lxde - (201601171107)
Machine:   Type: Desktop Mobo: ASUSTeK model: P5Q-PRO v: Rev 1.xx serial: <root required> BIOS: American Megatrends v: 2102
           date: 02/23/2009
Drives:    Local Storage: total: 465.77 GiB used: 56.97 GiB (12.2%)
           ID-1: /dev/sda vendor: Seagate model: ST3250820AS size: 232.89 GiB
           ID-2: /dev/sdb vendor: Western Digital model: WD2502ABYS-23B7A0 39M4511 42C0463IBM size: 232.89 GiB

--- End code ---
Die fstab

--- Code: ---$ cat /etc/fstab
UUID=ff169da5-8f35-467e-92c3-d117823796f7     /                    ext4         defaults,relatime,errors=remount-ro           0    1   
UUID=045398f2-dfbc-4cc5-99c5-dca098051969     none                 swap         sw                                            0    0   
UUID=C61C-895C                                /media/DATEN         vfat         auto,users,rw,quiet,umask=000,iocharset=utf8  0    0   
UUID=6EDE-B072                                /media/Distris       vfat         auto,users,rw,quiet,umask=000,iocharset=utf8  0    0   

--- End code ---

Charakteristisch ist immer wieder das:

--- Code: ---$ systemctl status udisks2.service
● udisks2.service - Disk Manager
   Loaded: loaded (/lib/systemd/system/udisks2.service; enabled; vendor preset: enabled)
   Active: active (running) since Sun 2019-07-21 11:16:38 CEST; 45min ago
     Docs: man:udisks(8)
 Main PID: 550 (udisksd)
    Tasks: 5 (limit: 4915)
   Memory: 8.6M
   CGroup: /system.slice/udisks2.service
           └─550 /usr/lib/udisks2/udisksd

Jul 21 11:16:21 sidLXDE systemd[1]: Starting Disk Manager...
Jul 21 11:16:23 sidLXDE udisksd[550]: udisks daemon version 2.8.3 starting
Jul 21 11:16:26 sidLXDE udisksd[550]: failed to load module crypto: libbd_crypto.so.2: cannot open shared object file: No such file or directory
Jul 21 11:16:26 sidLXDE udisksd[550]: failed to load module mdraid: libbd_mdraid.so.2: cannot open shared object file: No such file or directory
Jul 21 11:16:28 sidLXDE udisksd[550]: Failed to load the 'mdraid' libblockdev plugin
Jul 21 11:16:28 sidLXDE udisksd[550]: Failed to load the 'crypto' libblockdev plugin
Jul 21 11:16:38 sidLXDE udisksd[550]: Acquired the name org.freedesktop.UDisks2 on the system message bus
Jul 21 11:16:38 sidLXDE systemd[1]: Started Disk Manager.

--- End code ---

Weder mit mdraid, noch mit crypto, habe ich was am Hut... Hat wer eine Idee?   :)

piper:
I think if you install


--- Code: ---apt install libblockdev-crypto2 libblockdev-mdraid2
--- End code ---

The "error" should go away, seems this bug has been around the block (launchpad, debian, redhat) a few times and upgrades break it again

We deal with debian

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873634


EDIT:
Not sure after a few years if "gdisk" is still needed, most people I read from got by with what I post above, please read the whole report if you still have errors

unklarer:
Hello piper, thank you very much for your help.   :)

I also found this one:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873706#16

But that's not quite clear to me, because I uninstalled mdadm at that time because it wasn't used.

--- Code: ---apt install libblockdev-crypto2 libblockdev-mdraid2
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.       
Statusinformationen werden eingelesen.... Fertig
Die folgenden zusätzlichen Pakete werden installiert:
  gnupg gnupg-l10n gnupg-utils gpg-wks-server libbytesize1 libvolume-key1 mdadm
Vorgeschlagene Pakete:
  parcimonie xloadimage dracut-core
Die folgenden NEUEN Pakete werden installiert:
  gnupg gnupg-l10n gnupg-utils gpg-wks-server libblockdev-crypto2 libblockdev-mdraid2 libbytesize1
  libvolume-key1 mdadm
0 aktualisiert, 9 neu installiert, 0 zu entfernen und 1 nicht aktualisiert.
Es müssen 3.751 kB an Archiven heruntergeladen werden.
Nach dieser Operation werden 10,4 MB Plattenplatz zusätzlich benutzt.
Möchten Sie fortfahren? [J/n]

--- End code ---

I will tell you if I was successful.

unklarer:
No, the first start doesn't look any better.   ???


--- Code: ---apt policy libblockdev-crypto2
libblockdev-crypto2:
  Installiert:           2.22-1
  Installationskandidat: 2.22-1
  Versionstabelle:
 *** 2.22-1 500
        500 http://httpredir.debian.org/debian unstable/main amd64 Packages
        100 /var/lib/dpkg/status

apt policy libblockdev-mdraid2
libblockdev-mdraid2:
  Installiert:           2.22-1
  Installationskandidat: 2.22-1
  Versionstabelle:
 *** 2.22-1 500
        500 http://httpredir.debian.org/debian unstable/main amd64 Packages
        100 /var/lib/dpkg/status

--- End code ---

--- Code: ---systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

graphical.target @42.422s
└─udisks2.service @19.244s +23.177s
  └─basic.target @19.134s
    └─paths.target @19.134s
      └─cups.path @19.134s
        └─sysinit.target @18.909s
          └─systemd-timesyncd.service @17.598s +1.310s
            └─systemd-tmpfiles-setup.service @17.464s +112ms
              └─systemd-journal-flush.service @3.898s +13.564s
                └─systemd-journald.service @3.178s +717ms
                  └─systemd-journald-dev-log.socket @3.176s
                    └─system.slice @2.950s
                      └─-.slice @2.950s

--- End code ---

--- Code: ---systemctl status udisks2.service
● udisks2.service - Disk Manager
   Loaded: loaded (/lib/systemd/system/udisks2.service; enabled; vendor preset: enabled)
   Active: active (running) since Sun 2019-07-21 14:56:15 CEST; 3min 37s ago
     Docs: man:udisks(8)
 Main PID: 574 (udisksd)
    Tasks: 5 (limit: 4915)
   Memory: 10.9M
   CGroup: /system.slice/udisks2.service
           └─574 /usr/lib/udisks2/udisksd

Jul 21 14:55:52 sidLXDE systemd[1]: Starting Disk Manager...
Jul 21 14:55:54 sidLXDE udisksd[574]: udisks daemon version 2.8.3 starting
Jul 21 14:56:15 sidLXDE systemd[1]: Started Disk Manager.
Jul 21 14:56:15 sidLXDE udisksd[574]: Acquired the name org.freedesktop.UDisks2 on the system message bus

--- End code ---

Maybe he has to get used to it first...    :P

piper:
I have the same "errors" as you, thats all they are to me, I ignore them.

Do you use raid ?

If so, Hard or Soft ?   (I could throw humour here, but I have to behave :P )

libblockdev-mdraid-dev package just contains header files and pkg-config files needed for development with the libblockdev-mdraid plugin/library.

Navigation

[0] Message Index

[#] Next page