Siduction Forum

Siduction Forum => Software - Support => Topic started by: unklarer on 2019/07/21, 12:36:32

Title: udisks2.service
Post by: unklarer on 2019/07/21, 12:36:32

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: [Select]

$ 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
Die Systeme sind beide bis dato aktuell.

Code: [Select]

$ 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
Die fstab

Code: [Select]

$ 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   

Charakteristisch ist immer wieder das:

Code: [Select]

$ 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.

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

Title: Re: udisks2.service
Post by: piper on 2019/07/21, 14:09:12

I think if you install

Code: [Select]

apt install libblockdev-crypto2 libblockdev-mdraid2
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

Title: Re: udisks2.service
Post by: unklarer on 2019/07/21, 14:43:08

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: [Select]

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]

I will tell you if I was successful.

Title: Re: udisks2.service
Post by: unklarer on 2019/07/21, 15:07:55

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

Code: [Select]

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


Code: [Select]

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


Code: [Select]

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

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

Title: Re: udisks2.service
Post by: piper on 2019/07/21, 15:49:28

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.

Title: Re: udisks2.service
Post by: unklarer on 2019/07/21, 17:04:46

Quote from: piper

Do you use raid ?

No

Quote from: piper

...(I could throw humour here, but I have to behave  :P )

(http://www.en.kolobok.us/smiles/big_standart/acute.gif)

I'm old, have a lot of time and the userspace of 35 + x sec.  sometimes bothers me already.

The only thing the two siduction installations have in common is:
both access isos of the /media/Distris partition to play them in qemu.

but without the mount's in the fstab, I've already tested it. It wasn't better.   ;D

Title: Re: udisks2.service
Post by: melmarker on 2019/07/21, 18:17:32

Code: [Select]

apt show udisks2

If you don't need libblockdev-crypto2 and libblockdev-mdraid2 - just purge them.
Done. It maybe might be a good idea to rebuild the initramfs.

Title: Re: udisks2.service
Post by: piper on 2019/07/21, 18:32:53

Actually

Code: [Select]

apt show udisks2 -a
Usually without the -a it will throw you errors

I build my iso's without without libblockdev-crypto2 and libblockdev-mdraid2 and still have the errors, I just ignore

Title: Re: udisks2.service
Post by: unklarer on 2019/07/21, 21:04:02

Code: [Select]

systemd-analyze
Startup finished in 7.958s (kernel) + 49.229s (userspace) = 57.188s
graphical.target reached after 49.216s in userspace

I am using udisks2 in version 2.8.3-3.

It doesn't make any difference if the installation (LXDE) is done with
libblockdev-crypto2 and libblockdev-mdraid2 runs or without (KDE plasma).

There remain ~20+x sec. which udisks2 dawdles for unrecognizable reasons.

Code: [Select]

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 @49.216s
└─udisks2.service @24.367s +24.848s
  └─basic.target @24.164s
    └─sockets.target @24.164s
      └─cups.socket @24.164s
        └─sysinit.target @23.973s
          └─systemd-timesyncd.service @21.736s +2.236s
            └─systemd-tmpfiles-setup.service @21.361s +275ms
              └─systemd-journal-flush.service @3.648s +17.711s
                └─systemd-journald.service @2.917s +728ms
                  └─systemd-journald.socket @2.861s
                    └─-.mount @2.816s
                      └─systemd-journald.socket @2.861s


Code: [Select]

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 17:42:47 CEST; 2h 3min ago
     Docs: man:udisks(8)
 Main PID: 578 (udisksd)
    Tasks: 5 (limit: 4915)
   Memory: 13.2M
   CGroup: /system.slice/udisks2.service
           └─578 /usr/lib/udisks2/udisksd

Jul 21 17:42:22 sidLXDE systemd[1]: Starting Disk Manager...                                <----|
Jul 21 17:42:24 sidLXDE udisksd[578]: udisks daemon version 2.8.3 starting              25sec.
Jul 21 17:42:47 sidLXDE systemd[1]: Started Disk Manager.                                   <----|
Jul 21 17:42:47 sidLXDE udisksd[578]: Acquired the name org.freedesktop.UDisks2 on the system message bus

I was looking:

Code: [Select]

apt changelog udisks2
journalctl /dev/sdb
journalctl /dev/sda
journalctl _PID=578
...
-- Reboot --
Jul 21 17:42:24 sidLXDE udisksd[578]: udisks daemon version 2.8.3 starting
Jul 21 17:42:47 sidLXDE udisksd[578]: Acquired the name org.freedesktop.UDisks2 on the system message bus

journalctl -p warning -e
...
-- Reboot --
Jul 21 17:42:02 sidLXDE kernel: pci 0000:00:01.0: ASPM: current common clock configuration is broken, reconfiguring
Jul 21 17:42:02 sidLXDE kernel: i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
Jul 21 17:42:02 sidLXDE kernel: ACPI Warning: SystemIO range 0x0000000000000400-0x000000000000041F conflicts with OpRegion 0x0000000000000400-0x000000000000040F (\SMRG) (20190215/utaddress-204)
Jul 21 17:42:02 sidLXDE kernel: ACPI Warning: SystemIO range 0x0000000000000828-0x000000000000082F conflicts with OpRegion 0x0000000000000800-0x000000000000084F (\PMRG) (20190215/utaddress-204)
Jul 21 17:42:02 sidLXDE kernel: ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x000000000000053F (\GPS0) (20190215/utaddress-204)
Jul 21 17:42:02 sidLXDE kernel: ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x000000000000053F (\GPS0) (20190215/utaddress-204)
Jul 21 17:42:02 sidLXDE kernel: lpc_ich: Resource conflict(s) found affecting gpio_ich
Jul 21 17:42:02 sidLXDE kernel: resource sanity check: requesting [mem 0x000c0000-0x000dffff], which spans more than PCI Bus 0000:00 [mem 0x000d0000-0x000dffff window]
Jul 21 17:42:02 sidLXDE kernel: caller pci_map_rom+0x65/0x178 mapping multiple BARs
Jul 21 17:42:02 sidLXDE systemd[1]: Failed to bump fs.file-max, ignoring: Invalid argument
Jul 21 17:42:20 sidLXDE kernel: CX24123: cx24123_i2c_readreg: reg=0x0 (error=-121)
Jul 21 17:42:20 sidLXDE kernel: CX24123: wrong demod revision: 87
Jul 21 17:42:20 sidLXDE kernel: FAT-fs (sdb6): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Jul 21 17:42:20 sidLXDE kernel: FAT-fs (sda6): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Jul 21 17:42:21 sidLXDE systemd-udevd[407]: Process '/usr/sbin/alsactl -E HOME=/run/alsa restore 0' failed with exit code 99.
Jul 21 19:43:17 sidLXDE spice-vdagent[3720]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
Jul 21 19:43:27 sidLXDE bamfdaemon[3847]: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files

Hmpf...   :(

Title: Re: udisks2.service
Post by: der_bud on 2019/07/21, 22:12:19

Ich werde das Gefühl nicht los, dass es am Mounten der vfats hängen könnte. Die Option 'auto' bedeutet automatisches einhängen beim Systemstart, sprich bei systemd-Systemen und/oder solchen die von ssd booten sehr (zu?) früh, wenn Du sie vielleicht noch garnicht brauchst,
Optionen wie 'noauto,nofail' dagegen bereiten den Mount im Hintergrund vor und hängen beim ersten wirklich benötigten Zugriff ein. Ich fahre mit ausgelagerten Datengräbern erfolgreich mit zB

Code: [Select]

LABEL="DATEN"           /media/daten    ext4       noauto,nofail,x-systemd.automount,noatime,users,rw      0       0

Title: Re: udisks2.service
Post by: piper on 2019/07/21, 23:10:14

No ssd here period

Code: [Select]

siduction
UUID=01399612-56d0-4a06-86d2-3988eb5f4961     /                    ext4         defaults,relatime,errors=remount-ro           0    1   

debian
UUID=0b128c05-4733-4e4a-b493-f0d03fcbb856 /               ext4    errors=remount-ro 0       1

suse
UUID=7bcba613-1223-4171-a152-e4da9488970d     /                    ext4         defaults,relatime,errors=remount-ro           0    1   

sidux
UUID=563741a2-74c7-4a87-9465-e95716758f7a       /               ext3    defaults        0       1

LFS
UUID=7af3fe2c-effd-469b-8093-87863ef6c0e4 /              ext4    defaults,noatime 0 1

Title: Re: udisks2.service
Post by: unklarer on 2019/07/22, 13:24:55

Quote from: der_bud

Ich werde das Gefühl nicht los,...

Danke!   :D
Zum Zeitpunkt der Versuche heute Vormittag sind beide Systeme aktuell

Die fstab, mit der ich getestet habe, hänge ich dann unten an (bin z.Z. nicht an den betreffenden Rechner).

Ergebnis ist, es wird nicht besser, egal welche Parameter ich da eintrage.   :(   Wobei ich nicht weiß, wie x-systemd.automount hier wirkt oder nicht wirkt, wenn ich dies lese:

Quote from: fstab

fstab
...
If an automount point is configured in both /etc/fstab and a unit file, the configuration in the latter takes precedence.
fstab
...
Wenn ein Autoaktivierungspunkt sowohl in /etc/fstab als auch in einer Unit-Datei konfiguriert ist, hat die Konfiguration in letzterer Vorrang.

Eine Unit-Datei habe ich händisch nicht erstellt. Ich wüßte jetzt auch nicht, wo die zu suchen wäre...
Quelle (https://www.freedesktop.org/software/systemd/man/systemd.automount.html)

Code: [Select]

# <file system>                           <mount point>  <type>  <options>  <dump>  <pass>
UUID=045398f2-dfbc-4cc5-99c5-dca098051969 swap           swap    defaults,noatime,nofail 0       0
UUID=ef032757-1572-40fc-902f-1264499961a4 /              ext4    defaults,noatime 0       1
UUID=C61C-895C                            /media/DATEN   vfat    noauto,nofail,x-systemd.automount,uid=1000,gid=1000,rw,quiet,umask=0000,shortname=mixed,iocharset=utf8   0    0   
UUID=6EDE-B072                            /media/Distris vfat    noauto,nofail,x-systemd.automount,uid=1000,gid=1000,rw,quiet,umask=0000,shortname=mixed,iocharset=utf8   0    0
 
Ich habe erst mal die Faxen dick...   :'(