Boot delay

[Helio Mendonça]

Hi
I noticed in the last days that my Proxmox is taking more time to boot then normal.
When I watched the boot messages I can see the following:

Reading all physical volumes. This may take a while...
Found volume group "pve" using metadata type lvm2
/sbin/modprobe failed: 1
Can't process LV pve/data: thin-pool target support  missing from kernel?
Can't process LV pve/vm-121-disk-0: thin target support  missing from kernel?
Can't process LV pve/vm-121-disk-1: thin target support  missing from kernel?
Can't process LV pve/vm-121-disk-2: thin target support  missing from kernel?
Can't process LV pve/vm-122-disk-0: thin target support  missing from kernel?
2 logical volume(s) in volume group "pve" now active
/dev/mapper/pve-root: clean, 90523/6291456 files, 1529743/25165824 blocks
[  *** ] A start job is running for udev Wait for Complete Device Initialization (26s / 3min)_

After a delay of 26s the boot continues!
What is causing this 26s delay?
Can I avoid it or it is normal?

Regards

 

[Helio Mendonça]

After Googling a bit I ran the following command that confirm a 27s delay due to systemd-udev-settle.service:

root@pve:~# /usr/bin/systemd-analyze blame
         27.102s systemd-udev-settle.service
          5.413s pve-daily-update.service
          4.581s pve-guests.service
          2.009s systemd-modules-load.service
          1.290s pve-cluster.service
          1.245s pve-container@122.service

 

[maykel5353]

Same problem... In my case, hp proliant G7. At the moment, I executed this command and reboot machine:

systemctl mask ifupdown-service
systemctl mask systemd-udev-settle



2min 245ms systemd-udev-settle.service
1.964s pveproxy.service
1.798s systemd-modules-load.service
1.626s pve-guests.service
1.537s pvedaemon.service
1.059s pve-cluster.service
1.029s pve-ha-crm.service
1.025s pve-ha-lrm.service
966ms pvestatd.service
948ms pve-firewall.service
855ms pvesr.service
680ms lvm2-monitor.service
596ms dev-mapper-pve\x2droot.device
572ms spiceproxy.service
516ms postfix@-.service
448ms pvebanner.service
272ms lvm2-pvscan@8:3.service
243ms networking.service
195ms systemd-udev-trigger.service
194ms dev-pve-swap.swap
128ms systemd-journald.service
85ms rrdcached.service
78ms user@0.service
65ms zfs-share.service
62ms systemd-timesyncd.service
60ms systemd-logind.service
56ms ssh.service
44ms apparmor.service
42ms lxc.service
36ms rsyslog.service
35ms qmeventd.service
31ms smartmontools.service
30ms pve-lxc-syscalld.service
30ms systemd-udevd.service
30ms ksmtuned.service
29ms dev-mqueue.mount
28ms run-rpc_pipefs.mount
27ms systemd-tmpfiles-setup.service
27ms kmod-static-nodes.service
26ms keyboard-setup.service
24ms sys-kernel-debug.mount
24ms pvefw-logger.service
22ms systemd-remount-fs.service
20ms pvenetcommit.service
20ms systemd-sysusers.service
20ms rpcbind.service
18ms open-iscsi.service
18ms zfs-volume-wait.service
18ms systemd-journal-flush.service
17ms systemd-tmpfiles-setup-dev.service
16ms lxc-net.service
16ms zfs-mount.service
16ms iscsid.service
14ms systemd-random-seed.service
14ms dev-hugepages.mount
13ms systemd-update-utmp.service
12ms user-runtime-dir@0.service
12ms systemd-update-utmp-runlevel.service
11ms blk-availability.service
10ms systemd-user-sessions.service
9ms systemd-sysctl.service
7ms console-setup.service
6ms rbdmap.service
5ms nfs-config.service
4ms sys-kernel-config.mount
3ms sys-fs-fuse-connections.mount
2ms postfix.service