Slow boot due udisks2.service


on new Leap 42.3 installation the boot is extremely slow, main issue is udisks2.service - about 30 s, see the list below.
I have 3 HDD’s - 1) 2TB monted as /home and 2) SSD 120 GB with operating system.
3) Another SSD 120 GB with Windows 10, there is no booting issue on Windows.
Any idea what can be the rootcause?

Many Thanks


tomas:~ # systemd-analyze blame
22.696s udisks2.service
1.139s postfix.service
1.096s SuSEfirewall2.service
803ms var-lib-machines.mount
770ms srv.mount
769ms boot-grub2-x86_64\x2defi.mount
685ms usr-local.mount
653ms opt.mount
604ms display-manager.service
599ms tmp.mount
569ms boot-grub2-i386\x2dpc.mount
533ms var-lib-libvirt-images.mount
533ms var-tmp.mount
471ms var-lib-mariadb.mount
456ms \x2esnapshots.mount
408ms apparmor.service
385ms var-lib-mailman.mount
370ms var-spool.mount
367ms var-log.mount
283ms var-lib-pgsql.mount
261ms var-crash.mount
258ms dev-sdb2.device
225ms var-cache.mount
211ms home.mount
199ms SuSEfirewall2_init.service
174ms upower.service
168ms var-opt.mount
153ms ModemManager.service
151ms systemd-journal-flush.service
139ms var-lib-mysql.mount
134ms auditd.service
114ms user@1000.service
111ms NetworkManager.service
108ms var-lib-named.mount
84ms rc-local.service
82ms nscd.service
82ms alsa-restore.service
58ms avahi-daemon.service
54ms systemd-vconsole-setup.service
50ms systemd-udev-trigger.service
49ms polkit.service
45ms systemd-udevd.service
43ms ntpd.service
23ms dev-disk-by\x2duuid-08122837\x2d1fa8\x2d4245\x2d8334\x2dcb82d25ed773.swap
21ms systemd-fsck@dev-disk-by\x2duuid-6f240473\x2d854a\x2d426b\x2d9835\x2d7b09f86ff22e.service
16ms systemd-journald.service
15ms plymouth-read-write.service
15ms systemd-remount-fs.service
14ms plymouth-start.service
12ms sys-kernel-debug.mount
12ms iscsi.service
11ms dev-disk-by\x2duuid-a9ca7ce5\x2daa9f\x2d4fa2\x2d8f66\x2d10c27b3af1f2.swap
11ms rtkit-daemon.service
11ms dev-hugepages.mount
11ms mcelog.service
10ms dev-mqueue.mount
10ms kmod-static-nodes.service
9ms wpa_supplicant.service
9ms systemd-fsck-root.service
9ms systemd-logind.service
9ms systemd-sysctl.service
8ms systemd-tmpfiles-setup-dev.service
8ms systemd-udev-root-symlink.service
7ms systemd-update-utmp.service
6ms systemd-tmpfiles-setup.service
6ms dracut-shutdown.service
5ms systemd-user-sessions.service

Nothing depends on this service normally so its startup time hardly matters. “systemd-analyze critical-chain” is usually more useful in this case.

The critical chain shows following list, the real boot time from boot menu until GUI is ready is about 50s: @2.953s
└─ @2.953s
└─cron.service @2.953s
└─postfix.service @1.753s +1.198s
└─ @1.730s
└─ntpd.service @1.694s +35ms
└─ @1.691s
└─wpa_supplicant.service @2.408s +12ms
└─ @1.400s
└─ @1.400s
└─dbus.socket @1.400s
└─ @1.400s
└─systemd-update-utmp.service @1.394s +5ms
└─auditd.service @1.261s +131ms
└─ @1.202s
└─var-lib-pgsql.mount @467ms +734ms
└─dev-disk-by\x2duuid-f86d5fa8\x2dd5c6\x2d408f\x2da790\x2d3998c5e7f2f9.device @456ms