Switched to systemd, now 2 minutes added to boot time  [Solved]

Help with the version of MX KDE officially released by the Development Team.
When asking for help, use Quick System Info from MX Tools. It will be properly formatted using the following steps.
1. Click on Quick System Info in MX Tools
2. Right click in your post and paste.
Message
Author
User avatar
paul1149
Posts: 531
Joined: Fri Dec 29, 2017 11:39 am

Switched to systemd, now 2 minutes added to boot time

#1 Post by paul1149 »

I just made the switch to systemd. It went without event, except that suddenly the boot time multiplied many times over. The delay occurs just after the dynamic MX logo (which is way-cool, BTW, great work!) completes its composition. If I hit the down arrow key, I see what's going on under the hood:
systemd boot delay -ff.png
It looks like fsck is taking its time.

I don't see why switching to systemd would cause this.

It's happening even after going into fstab and changing fsck options to 2 (after boot) for all but the root drive.

@Charlie Brown suggested this diagnostic:

Code: Select all

systemd-analyze critical-chain ; systemd-analyze blame
And that yielded this:

Code: Select all

$ systemd-analyze critical-chain ; systemd-analyze blame >> ~/Desktop/boot_delay.txt
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

graphical.target @1min 37.208s
└─multi-user.target @1min 37.208s
  └─smbd.service @1min 37.128s +80ms
    └─nmbd.service @1min 37.040s +86ms
      └─network-online.target @1min 36.997s
        └─NetworkManager-wait-online.service @1min 30.484s +6.512s
          └─NetworkManager.service @1min 30.468s +14ms
            └─dbus.service @1min 30.428s +38ms
              └─basic.target @1min 30.370s
                └─sockets.target @1min 30.370s
                  └─dbus.socket @1min 30.370s
                    └─sysinit.target @1min 30.359s
                      └─systemd-binfmt.service @1.323s +917ms
                        └─proc-sys-fs-binfmt_misc.mount @2.222s +15ms
                          └─systemd-journald.socket @197ms
                            └─system.slice @170ms
                              └─-.slice @170ms

6.512s NetworkManager-wait-online.service
 917ms systemd-binfmt.service
 450ms cpufrequtils.service
 212ms udisks2.service
 186ms tlp.service
 163ms dev-nvme0n1p2.device
 160ms smartmontools.service
 149ms ufw.service
 140ms user@1000.service
 125ms nfs-server.service
  86ms nmbd.service
  85ms lvm2-monitor.service
  80ms systemd-udev-trigger.service
  80ms smbd.service
  60ms accounts-daemon.service
  59ms media-WD1000.mount
  59ms loadcpufreq.service
  57ms proc-fs-nfsd.mount
  48ms systemd-logind.service
  43ms avahi-daemon.service
  43ms systemd-fsck@dev-disk-by\x2dlabel-homeMX\x2d500.service
  41ms systemd-fsck@dev-disk-by\x2duuid-FFB7\x2d1E73.service
  40ms upower.service
  40ms systemd-journald.service
  39ms polkit.service
  39ms ModemManager.service
  39ms samba-ad-dc.service
  38ms dbus.service
  37ms lm-sensors.service
  33ms networking.service
  32ms systemd-udevd.service
  31ms systemd-tmpfiles-clean.service
  26ms nfs-idmapd.service
  25ms systemd-modules-load.service
  25ms systemd-journal-flush.service
  24ms nfsdcld.service
  22ms plymouth-quit-wait.service
  22ms plymouth-quit.service
  21ms media-NVMe_930.mount
  21ms plymouth-start.service
  19ms chrony.service
  17ms nfs-blkmap.service
  15ms proc-sys-fs-binfmt_misc.mount
  14ms cups.service
  14ms NetworkManager.service
  13ms plymouth-read-write.service
  12ms e2scrub_reap.service
  11ms nextdns.service
  10ms user-runtime-dir@1000.service
   9ms dev-hugepages.mount
   9ms colord.service
   9ms boot-efi.mount
   9ms systemd-tmpfiles-setup.service
   9ms dev-mqueue.mount
   9ms systemd-tmpfiles-setup-dev.service
   9ms wpa_supplicant.service
   9ms alsa-restore.service
   8ms sys-kernel-debug.mount
   8ms nfs-mountd.service
   8ms sys-kernel-tracing.mount
   8ms rsyslog.service
   7ms keyboard-setup.service
   7ms kmod-static-nodes.service
   7ms modprobe@fuse.service
   6ms modprobe@configfs.service
   6ms modprobe@drm.service
   5ms systemd-remount-fs.service
   5ms rpc-statd.service
   5ms home.mount
   5ms systemd-random-seed.service
   5ms systemd-sysusers.service
   4ms ifupdown-pre.service
   4ms systemd-update-utmp-runlevel.service
   4ms systemd-sysctl.service
   4ms systemd-update-utmp.service
   4ms systemd-user-sessions.service
   4ms rpcbind.service
   3ms rc-local.service
   2ms console-setup.service
   2ms rpc-statd-notify.service
   2ms rtkit-daemon.service
   1ms modprobe@dm_mod.service
   1ms openvpn.service
   1ms run-rpc_pipefs.mount
   1ms sys-kernel-config.mount
   1ms modprobe@efi_pstore.service
   1ms modprobe@loop.service
   1ms sys-fs-fuse-connections.mount
 996us network-manager.service
  15us blk-availability.service
Nothing jumps out at me there.

I'd like to resolve this, but I can go back to SysVinit if necessary, assuming that would resolve it.

QSI follows.

Thanks.

Code: Select all

System:
  Kernel: 6.1.0-13-amd64 [6.1.55-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-13-amd64 root=UUID=<filter> ro quiet splash
    init=/lib/systemd/systemd
  Desktop: KDE Plasma v: 5.27.5 wm: kwin_x11 vt: 7 dm: SDDM Distro: MX-23.1_KDE_x64 Libretto
    October 15 2023 base: Debian GNU/Linux 12 (bookworm)
Machine:
  Type: Desktop Mobo: Micro-Star model: MAG B550 TOMAHAWK (MS-7C91) v: 2.0
    serial: <superuser required> UEFI: American Megatrends LLC. v: A.F0 date: 10/19/2023
CPU:
  Info: model: AMD Ryzen 5 5600X bits: 64 type: MT MCP arch: Zen 3+ gen: 4 level: v3 note: check
    built: 2022 process: TSMC n6 (7nm) family: 0x19 (25) model-id: 0x21 (33) stepping: 0
    microcode: 0xA20102B
  Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache: L1: 384 KiB
    desc: d-6x32 KiB; i-6x32 KiB L2: 3 MiB desc: 6x512 KiB L3: 32 MiB desc: 1x32 MiB
  Speed (MHz): avg: 2465 high: 2800 min/max: 2200/4650 boost: enabled scaling:
    driver: acpi-cpufreq governor: ondemand cores: 1: 2779 2: 2200 3: 2800 4: 2798 5: 2237 6: 2237
    7: 2799 8: 2239 9: 2228 10: 2799 11: 2236 12: 2239 bogomips: 88806
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow mitigation: safe RET
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW, STIBP: always-on, RSB
    filling, PBRSB-eIBRS: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: AMD Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X] driver: amdgpu v: kernel
    arch: GCN-4 code: Arctic Islands process: GF 14nm built: 2016-20 pcie: gen: 3 speed: 8 GT/s
    lanes: 8 ports: active: DVI-D-1,HDMI-A-1 empty: none bus-ID: 2b:00.0 chip-ID: 1002:699f
    class-ID: 0300 temp: 37.0 C
  Device-2: Sunplus Innovation SPCA2281 Web Camera type: USB driver: snd-usb-audio,uvcvideo
    bus-ID: 1-5.4.3:7 chip-ID: 1bcf:2281 class-ID: 0102
  Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9 compositor: kwin_x11 driver: X:
    loaded: amdgpu unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: amdgpu display-ID: :0
    screens: 1
  Screen-1: 0 s-res: 2720x1024 s-dpi: 96 s-size: 719x270mm (28.31x10.63") s-diag: 768mm (30.24")
  Monitor-1: DVI-D-1 mapped: DVI-D-0 pos: top-left model: ViewSonic VP191b serial: <filter>
    built: 2004 res: 1280x1024 hz: 60 dpi: 86 gamma: 1.2 size: 376x310mm (14.8x12.2")
    diag: 487mm (19.2") ratio: 5:4 modes: max: 1280x1024 min: 720x400
  Monitor-2: HDMI-A-1 mapped: HDMI-A-0 pos: primary,bottom-r model: Dell SE198WFP
    serial: <filter> built: 2008 res: 1440x900 hz: 60 dpi: 90 gamma: 1.2
    size: 408x255mm (16.06x10.04") diag: 481mm (18.9") ratio: 16:10 modes: max: 1440x900
    min: 720x400
  API: OpenGL v: 4.6 Mesa 23.1.2-1~mx23ahs renderer: AMD Radeon RX 550 / 550 Series (polaris12
    LLVM 15.0.6 DRM 3.49 6.1.0-13-amd64) direct-render: Yes
Audio:
  Device-1: AMD Baffin HDMI/DP Audio [Radeon RX 550 640SP / 560/560X] driver: snd_hda_intel
    v: kernel bus-ID: 1-5.4.3:7 pcie: chip-ID: 1bcf:2281 gen: 3 speed: 8 GT/s class-ID: 0102 lanes: 8
    bus-ID: 2b:00.1 chip-ID: 1002:aae0 class-ID: 0403
  Device-2: AMD Starship/Matisse HD Audio vendor: Micro-Star MSI driver: snd_hda_intel v: kernel
    pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 2d:00.4 chip-ID: 1022:1487 class-ID: 0403
  Device-3: Sunplus Innovation SPCA2281 Web Camera type: USB driver: snd-usb-audio,uvcvideo
  API: ALSA v: k6.1.0-13-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Micro-Star MSI
    driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: e000 bus-ID: 05:00.0
    chip-ID: 10ec:8168 class-ID: 0200
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-2: Realtek RTL8125 2.5GbE vendor: Micro-Star MSI driver: r8169 v: kernel pcie: gen: 2
    speed: 5 GT/s lanes: 1 port: d000 bus-ID: 2a:00.0 chip-ID: 10ec:8125 class-ID: 0200
  IF: eth1 state: down mac: <filter>
Drives:
  Local Storage: total: 2.27 TiB used: 948.76 GiB (40.7%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:2 vendor: Samsung model: SSD 980 500GB size: 465.76 GiB
    block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: 1B4QFXO7 temp: 33.9 C scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Samsung model: SSD 970 EVO Plus 1TB size: 931.51 GiB
    block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: 4B2QEXM7 temp: 33.9 C scheme: GPT
  ID-3: /dev/sda maj-min: 8:0 vendor: Western Digital model: WD10EZEX-00UJTA0 size: 931.51 GiB
    block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: N/A serial: <filter> rev: 1A01
    scheme: GPT
Partition:
  ID-1: / raw-size: 38.96 GiB size: 38.06 GiB (97.67%) used: 15.52 GiB (40.8%) fs: ext4
    dev: /dev/nvme0n1p2 maj-min: 259:4
  ID-2: /boot/efi raw-size: 500 MiB size: 499 MiB (99.80%) used: 568 KiB (0.1%) fs: vfat
    dev: /dev/nvme0n1p1 maj-min: 259:3
  ID-3: /home raw-size: 408.16 GiB size: 400.69 GiB (98.17%) used: 33.14 GiB (8.3%) fs: ext4
    dev: /dev/nvme0n1p3 maj-min: 259:5
Swap:
  Alert: No swap data was found.
Sensors:
  System Temperatures: cpu: 51.5 C mobo: N/A gpu: amdgpu temp: 37.0 C
  Fan Speeds (RPM): N/A
Repos:
  Packages: 2948 pm: dpkg pkgs: 2942 libs: 1723 tools: apt,apt-get,aptitude,nala pm: rpm pkgs: 0
    pm: flatpak pkgs: 6
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list
    1: deb [arch=amd64] https://brave-browser-apt-release.s3.brave.com/ stable main
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/megasync.list
    1: deb [signed-by=/usr/share/keyrings/meganz-archive-keyring.gpg] https://mega.nz/linux/repo/Debian_12/ ./
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bookworm main non-free
    2: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bookworm ahs
  Active apt repos in: /etc/apt/sources.list.d/nextdns.list
    1: deb [signed-by=/etc/apt/keyrings/nextdns.gpg] https://repo.nextdns.io/deb stable main
  Active apt repos in: /etc/apt/sources.list.d/syncthing.list
    1: deb https://apt.syncthing.net/ syncthing stable
  Active apt repos in: /etc/apt/sources.list.d/vivaldi-snapshot.list
    1: deb [arch=amd64] https://repo.vivaldi.com/snapshot/deb/ stable main
  Active apt repos in: /etc/apt/sources.list.d/zulu-openJDK.list
    1: deb [arch=amd64] http://repos.azulsystems.com/debian stable main
  Active apt repos in: /etc/apt/sources.list.d/zulu-openjdk.list
    1: deb [ arch=amd64 ] https://repos.azul.com/zulu/deb/ stable main
Info:
  Processes: 331 Uptime: 24m wakeups: 0 Memory: 15.54 GiB used: 4.53 GiB (29.1%) Init: systemd
  v: 252 target: graphical (5) default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI
You do not have the required permissions to view the files attached to this post.
MX-19-KDE x64, on Ryzen 5, 16GB RAM, SSD. Nvidia graphics.

Charlie Brown

Re: Switched to systemd, now 2 minutes added to boot time

#2 Post by Charlie Brown »

paul1149 wrote: Tue Dec 19, 2023 6:20 pm... all but the root drive...
... But ... that was what I meant :) (Others can still stay with 2)

Yes, normally it's (advised) to be 1 for /

0 - Never
1- At Boot
2- After Boot

Charlie Brown

Re: Switched to systemd, now 2 minutes added to boot time

#3 Post by Charlie Brown »

Code: Select all

sudo systemctl disable NetworkManager-wait-online.service
You can also use the "MX Service Manager" to disable that.

User avatar
j2mcgreg
Global Moderator
Posts: 7174
Joined: Tue Oct 23, 2007 12:04 pm

Re: Switched to systemd, now 2 minutes added to boot time  [Solved]

#4 Post by j2mcgreg »

It could be spending time looking for the missing swap space. You can add a swapfile to see if it helps by following these directions:
https://www.digitalocean.com/community/ ... -debian-11
HP 15; ryzen 3 5300U APU; 500 Gb SSD; 8GB ram
HP 17; ryzen 3 3200; 500 GB SSD; 12 GB ram
Idea Center 3; 12 gen i5; 256 GB ssd;

In Linux, newer isn't always better. The best solution is the one that works.

User avatar
paul1149
Posts: 531
Joined: Fri Dec 29, 2017 11:39 am

Re: Switched to systemd, now 2 minutes added to boot time

#5 Post by paul1149 »

Charlie Brown wrote: Tue Dec 19, 2023 6:25 pm
paul1149 wrote: Tue Dec 19, 2023 6:20 pm... all but the root drive...
... But ... that was what I meant :) (Others can still stay with 2)

Yes, normally it's (advised) to be 1 for /

0 - Never
1- At Boot
2- After Boot
Charlie, sorry, I don't get this. All drives are now 2, except the Swap drive with is 0, and root is 1. The reference I was working from said root had to be 1, and that made sense to me. Beside, it's a 39GB partition on a 500GB NVMe, which I think would process very quickly?
MX-19-KDE x64, on Ryzen 5, 16GB RAM, SSD. Nvidia graphics.

User avatar
paul1149
Posts: 531
Joined: Fri Dec 29, 2017 11:39 am

Re: Switched to systemd, now 2 minutes added to boot time

#6 Post by paul1149 »

j2mcgreg wrote: Tue Dec 19, 2023 6:31 pm It could be spending time looking for the missing swap space. You can add a swapfile to see if it helps by following these directions:
https://www.digitalocean.com/community/ ... -debian-11
It does seem to be something to do with the swap drive. I have the drive specced in fstab, and I ran 'sudo mount -a' with no hiccups, so I don't see why there would be a problem at boot.
MX-19-KDE x64, on Ryzen 5, 16GB RAM, SSD. Nvidia graphics.

User avatar
paul1149
Posts: 531
Joined: Fri Dec 29, 2017 11:39 am

Re: Switched to systemd, now 2 minutes added to boot time

#7 Post by paul1149 »

Ok, I was afraid to disable NetworkManager-wait-online.service, but on investigation it seems to be completely unnecessary for a simple workstation. So I did. However, that made no difference at all. The boot still wasted 1.5m on checking the swap device.

Maybe redoing the swap is a good idea. It definitely is fsck, and it definitely has something to do with swap.
Last edited by paul1149 on Tue Dec 19, 2023 7:21 pm, edited 1 time in total.
MX-19-KDE x64, on Ryzen 5, 16GB RAM, SSD. Nvidia graphics.

Charlie Brown

Re: Switched to systemd, now 2 minutes added to boot time

#8 Post by Charlie Brown »

Maybe it's not flagged as swap on GParted or so ...?

Or the one in fstab shows another uuid for swap (wrong place) ...

Just compare the uuids with fstab:

Code: Select all

lsblk -f

User avatar
paul1149
Posts: 531
Joined: Fri Dec 29, 2017 11:39 am

Re: Switched to systemd, now 2 minutes added to boot time

#9 Post by paul1149 »

Ok, the swap entry in fstab was messed up real good. I made the corrections, and the machine now sails through the boot process.

I ran free -m -t to check the swap, and got:

Code: Select all

               total        used        free      shared  buff/cache   available
Mem:           15911        3841       10209          84        2272       12069
Swap:          18578           0       18578
Total:         34490        3841       28788
Which I think is ok.

But an attempt at hibernation failed. I have more swap than RAM, but the machine rebooted rather than restoring the previous session. So that's something I will have to clean up at some point (I've seldom used hibernation anyway).

Thanks all for your helpful input. The major part of the pains switching over are resolved.

Be well!
MX-19-KDE x64, on Ryzen 5, 16GB RAM, SSD. Nvidia graphics.

Charlie Brown

Re: Switched to systemd, now 2 minutes added to boot time

#10 Post by Charlie Brown »

paul1149 wrote: Tue Dec 19, 2023 7:56 pm... But an attempt at hibernation failed. ...rebooted rather than restoring the previous session...

Code: Select all

lsblk -f | grep swap

Code: Select all

echo RESUME=UUID=XXX | sudo tee /etc/initramfs-tools/conf.d/resume ; sudo update-initramfs -uk all
Reboot.


(Just copy-paste the uuid number from the 1st output in place of XXX . i.e. ...=UUID=62958266-3d47-4620-ab1e-c56e6142abb8 | sudo tee ... )

Post Reply

Return to “MX KDE Official Release”