Very long time booting after upgrading from 42.3 to 15.0

Hi!
I have recently upgraded my notebook from leap 42.3 to 15.0 (yes, I am a tad behind, sorry!) and I’ve found that boot takes much much longer than 42.3 or even than my laptop running Tumbleweed.
I did a bit of research and I think there are two suspects:

# systemd-analyze blame  | head -20
    1min 30.131s clamd.service
         27.796s plymouth-quit-wait.service
         12.243s ca-certificates.service
          7.116s postfix.service
          6.817s display-manager.service
          6.410s SuSEfirewall2_init.service
          6.368s lvm2-monitor.service
          5.854s apparmor.service
          5.109s initrd-switch-root.service
          4.087s nscd.service
          4.080s alsa-restore.service
          3.995s bluetooth.service
          3.253s btrfsmaintenance-refresh.service
          2.550s windscribe.service
          2.175s polkit.service
          1.755s systemd-udevd.service
          1.634s fwupd.service
          1.630s SuSEfirewall2.service
          1.447s colord.service
          1.198s systemd-journal-flush.service

clamd.service seems to take remarkably long. My question is, what can I do to fix this? or, where can I find more information about this problem?

In the second place:

# grep resume /etc/default/grub
GRUB_CMDLINE_LINUX_DEFAULT="resume=/dev/sda2 splash=silent quiet showopts resume=/dev/sda2 splash=silent quiet showopts resume=/dev/sda2 splash=silent quiet showopts resume=/dev/sda2 splash=silent quiet showopts"

(where sda2 is the root partition)
This looks rather repetitive, is it supposed to be like this? It doesn’t look quite right. I’ve compared it to my Tumbleweed result running the same command and it doesn’t repeat the same parameter, but I don’t dare chopping it off without asking first.

Perhaps these are all irrelevant, and I should be looking elsewhere? Leap does boot and runs smoothly, but it takes a surprisingly long time to do so.

Thank you in advance for all the help and ideas that you can kindly provide.

Did you modified the order of the boot sequence on your BIOS ?

Yes, that looks repetitive. No, it is not supposed to look like that.

I suggest you edit the file and clean that up (remove all repetitions). And then update “/boot/grub2/grub.cfg” so that the changes make it to there.

It might be easier to use Yast bootloader to make those changes. Those repetitions will appear in the kernel parameters tab. And Yast will automatically update grub.cfg when you are done.

Thank you so much for your kind reply, nrickert.

I used yast bootloader to remove the repetitions, and it has improved, although it is still slower than 42.3, and most lines in the boot sequence appear twice. Hmm… Is there anywhere else I should look for info? Thank you once again!

(Perhaps 15.0 is expected to be slower on the same machine 42.3 was running, in which case I might just need better hardware)

Hi, Asimov, thanks for your kind reply. It doesn’t seem to be a problem with the BIOS’s boot sequence.

Indeed. I don’t use it, so don’t know how much time it should consume, but AV software on Windows is a big resource gobbler. Does clamd take that long to startup on every boot?

The slowest of my 64 bit PCs isn’t too terrible (rotating rust):

# inxi -GxxSCa
System:    Host: gx62b Kernel: 4.12.14-lp150.12.61-default x86_64 bits: 64 compiler: gcc v: 7.4.0
           parameters: root=LABEL=28os150 ipv6.disable=1 net.ifnames=0 noresume mitigations=auto consoleblank=0 vga=791
           video=1024x768@60 video=1440x900@60 5
           Desktop: Trinity R14.0.6 tk: Qt 3.5.0 wm: Twin dm: TDM Distro: openSUSE Leap 15.0
CPU:       Topology: Single Core model: Intel Pentium 4 bits: 64 type: MT arch: Netburst Presler family: F (15) model-id: 6
           stepping: 4 microcode: 4 L1 cache: 16 KiB L2 cache: 2048 KiB
           flags: lm nx pae sse sse2 sse3 bogomips: 12768
           Speed: 3192 MHz min/max: N/A Core speeds (MHz): 1: 3192 2: 3192
...
Graphics:  Device-1: Intel 82945G/GZ Integrated Graphics vendor: Dell driver: i915 v: kernel bus ID: 00:02.0
           chip ID: 8086:2772
           Display: server: X.Org 1.19.6 driver: intel unloaded: fbdev,modesetting,vesa resolution: 1680x1050~60Hz
           OpenGL: renderer: Mesa DRI Intel 945G v: 1.4 Mesa 18.0.2 direct render: Yes
# systemd-analyze blame | head -n20
         19.166s lvm2-monitor.service
          6.830s wicked.service
          5.853s auditd.service
          5.531s systemd-fsck@dev-disk-by\x2dlabel-15suse123.service
          5.491s initrd-switch-root.service
          5.473s systemd-journal-flush.service
          5.380s systemd-udevd.service
          4.894s systemd-fsck@dev-disk-by\x2dlabel-08home.service
          4.217s systemd-fsck@dev-disk-by\x2dlabel-14suse122.service
          3.537s systemd-fsck@dev-disk-by\x2dlabel-09pub.service
          2.837s kbdsettings.service
          2.734s systemd-fsck@dev-disk-by\x2dlabel-07suse121.service
          2.092s systemd-fsck@dev-disk-by\x2dlabel-10usrlcl.service
          1.957s display-manager.service
          1.799s alsa-restore.service
          1.790s fbset.service
          1.739s avahi-daemon.service
          1.689s wickedd-dhcp6.service
          1.682s wickedd-auto4.service
          1.682s wickedd-dhcp4.service

This is from my fastest (M.2 SATA SSD):

# inxi -GxxSCa
System:    Host: gb250 Kernel: 4.12.14-lp150.12.61-default x86_64 bits: 64 compiler: gcc v: 7.4.0
           parameters: BOOT_IMAGE=/boot/vmlinuz root=LABEL=k25p08s150 noresume ipv6.disable=1 net.ifnames=0 video=1024x768@60
           video=1400x900@60 5
           Desktop: Trinity R14.0.6 tk: Qt 3.5.0 wm: Twin dm: TDM Distro: openSUSE Leap 15.0
CPU:       Topology: Dual Core model: Intel Core i3-7100T bits: 64 type: MT MCP arch: Kaby Lake family: 6 model-id: 9E (158)
           stepping: 9 microcode: 8E L1 cache: 128 KiB L2 cache: 3072 KiB L3 cache: 3072 KiB
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 27264
           Speed: 800 MHz min/max: 800/3400 MHz Core speeds (MHz): 1: 800 2: 800 3: 801 4: 800
...
Graphics:  Device-1: Intel HD Graphics 630 vendor: Gigabyte driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:5912
           Display: server: X.Org 1.19.6 driver: modesetting unloaded: fbdev,vesa alternate: intel resolution: 1920x1200~60Hz
           OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2) v: 4.5 Mesa 18.0.2 compat-v: 3.0
           direct render: Yes
# systemd-analyze blame | head -n20
          2.059s kbdsettings.service
          1.871s wickedd.service
          1.269s lvm2-monitor.service
          1.029s wicked.service
           249ms initrd-switch-root.service
           201ms backup-rpmdb.service
           199ms initrd-parse-etc.service
           195ms display-manager.service
           164ms backup-sysconfig.service
           107ms logrotate.service
            99ms systemd-journal-flush.service
            93ms sshd.service
            61ms systemd-vconsole-setup.service
            57ms systemd-udevd.service
            50ms systemd-udev-trigger.service
            45ms user@0.service
            43ms chronyd.service
            41ms systemd-fsck@dev-disk-by\x2dlabel-k25p06pub.service
            40ms fbset.service
            40ms systemd-fsck@dev-disk-by\x2dlabel-k25p05home.service

Fastest PC boot I seem to recall seeing reported was about 2.6 seconds, probably on linuxquestions.org forums.

Hi, mrmazda! Thank you for your kind reply.

The notebook in question is a bit old, but it’s my most portable computer for field work, which is a large part of my job.

# inxi -GxxSCD
System:    Host: rödvatten Kernel: 5.2.0-rc4-2.gad82a9a-default x86_64 bits: 64 gcc: 9.1.1
           Desktop: Gnome 3.26.2 (Gtk 3.22.30) dm: gdm Distro: openSUSE Leap 15.0
CPU:       Quad core Intel Pentium N3540 (-MCP-) arch: Silvermont rev.8 cache: 1024 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 17326
           clock speeds: min/max: 499/2665 MHz 1: 526 MHz 2: 507 MHz 3: 1647 MHz 4: 523 MHz
Graphics:  Card: Intel Atom Processor Z36xxx/Z37xxx Series Graphics & Display bus-ID: 00:02.0 chip-ID: 8086:0f31
           Display Server: x11 (X.Org 1.19.6 ) drivers: intel (unloaded: modesetting,fbdev,vesa)
           Resolution: 1366x768@59.99hz
           OpenGL: renderer: Mesa DRI Intel Bay Trail version: 4.2 Mesa 18.0.2 (compat-v: 3.0) Direct Render: Yes
Drives:    HDD Total Size: 500.1GB (24.9% used)
           ID-1: /dev/sda model: HGST_HTS545050A7 size: 500.1GB serial: RBF50A1N0WH0UP temp: 0C

I have been looking for information online on the clamd situation, because I had clamd running with 42.3 and I have it running with Tumbleweed (different computer though) and it doesn’t even show up among the top 20 services when I do a systemd-analyze blame.
I found this https://0xacab.org/leap/platform/issues/7683 but it seems old and in any case I can’t get around to applying any of this to my situation. (Should I modify any file? If so, which one? How?)
Perhaps this is all very obvious, and I apologize for my obtuseness, but I can’t seem to find a solution by myself.

Just suggestions, since I don’t use clamd: look in /var/log. Does clamd have its own logging there? Are logs huge? Are logs getting rotated? Are logrotate and clamd configurations on your Bay Trail notebook and your TW laptop the same? Why are you using latest development kernel instead of 15.0 kernel? Is 15.0 a result of a series of upgrades going back to 13.1 or 13.2 without a fresh installation intervening?