Boot time takes much longer after apt upgrade

General Discussion
1

Running Dietpi v9.8.0, I have upgraded (apt upgrade) two different machines RPI4 yesterday, this is the only changes I made. The boot time changes from few seconds to more than 1 minute.
Is there anyone with the sames issue ?

1 Like
2

best is to check boot times

systemd-analyze blame
systemd-analyze critical-chain
1 Like
3

Here is the output of both commands:

$ systemd-analyse blame
10.560s ifup@wlan0.service
 2.174s ifupdown-pre.service
  819ms dev-mmcblk0p2.device
  457ms rpi-eeprom-update.service
  425ms dpkg-db-backup.service
  393ms systemd-fsck@dev-disk-by\x2dpartuuid-6b2e6707\x2d01.service
  388ms user@1000.service
  324ms systemd-udev-trigger.service
  267ms keyboard-setup.service
  251ms networking.service
  248ms dbus.service
  240ms systemd-logind.service
  235ms dietpi-ramlog.service
  211ms ssh.service
  211ms systemd-fsck-root.service
  191ms polkit.service
  176ms loadcpufreq.service
  149ms lightdm.service
  147ms dietpi-preboot.service
  143ms systemd-journald.service
  136ms systemd-timesyncd.service
  135ms systemd-udevd.service
  107ms modprobe@drm.service
   99ms fake-hwclock.service
   97ms systemd-remount-fs.service
   97ms systemd-binfmt.service
   90ms dev-mqueue.mount
   89ms sys-kernel-debug.mount
   88ms sys-kernel-tracing.mount
   82ms modprobe@configfs.service
   80ms modprobe@fuse.service
   75ms kmod-static-nodes.service
   69ms systemd-tmpfiles-setup.service
   63ms cpufrequtils.service
   59ms systemd-modules-load.service
   58ms systemd-sysusers.service
   57ms systemd-sysctl.service
   57ms systemd-journal-flush.service
   53ms systemd-random-seed.service
   41ms systemd-tmpfiles-setup-dev.service
   36ms user-runtime-dir@1000.service
   35ms systemd-update-utmp.service
   31ms var-swap.swap
   30ms boot.mount
   26ms alsa-restore.service
   23ms console-setup.service
   21ms tmp.mount
   20ms systemd-rfkill.service
   20ms systemd-user-sessions.service
   19ms systemd-update-utmp-runlevel.service
   17ms proc-sys-fs-binfmt_misc.mount
   13ms sys-fs-fuse-connections.mount
   11ms modprobe@dm_mod.service
   10ms modprobe@loop.service
   10ms sys-kernel-config.mount
   10ms var-log.mount
    9ms modprobe@efi_pstore.service

$ systemd-analyse critical-chain
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 31.094s
└─lightdm.service @1min 30.943s +149ms
  └─systemd-user-sessions.service @13.894s +20ms
    └─network.target @13.865s
      └─ifup@wlan0.service @3.303s +10.560s
        └─network-pre.target @3.273s
          └─ifupdown-pre.service @1.097s +2.174s
            └─systemd-udev-trigger.service @762ms +324ms
              └─systemd-udevd-kernel.socket @678ms
                └─system.slice @650ms
                  └─-.slice @650ms

Do you have an idea?

4

I guess you are running a desktop using automatic login with user dietpi. If yes, see Booting on Pi4 Mate - this now has a 1,5 minute delay

5

Yes, indeed I use automatic login with user dietpi and automatically launch LXDE.
You can close this topic; I will switch to the topic you mentioned above.
Thanks.