I’m using OpenSuSE 13.1 with kernel 3.14.4-30.gbebeb6f-desktop . Filesystem of root is btrfs. I think culprit is filesystem of root. I also noticed system is checking filesystem of /home(ext4) on every boot. On default kernel of this release the problem also occur.
I have checked system startup time and it was one minute 20 seconds. I don’t have ssd hard drive. On virtual machine (VirtualBox) running on this same computer system starts very fast. System on virtual machine don’t use btrfs as root filesystem.
On 2014-06-01 15:46, Lachu wrote:
>
> I have checked system startup time and it was one minute 20 seconds.
That in itself is not bad.
Telcontar:~ # systemd-analyze
Startup finished in 13.365s (kernel) + 1min 32.088s (userspace) = 1min 45.453s
Telcontar:~ #
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
For all virtual machines, there is a bootup bug. Download and run the script I reference in the Forum thread in every Guest to fix.
http://forums.opensuse.org/showthread.php/498287-Save-at-least-30-seconds-every-time-you-boot-a-Virtualization-Guest?p=2645295#post2645295
I’ve found this problem so far to affect VMware, VirtualBox and KVM. Probably affects “all” virtualization technologies.
I don’t know what Desktop you’re running, if KDE then over a minute and possibly about a minute and a half for a new machine with relatively few services running can be expected. If you want to trim faster bootup times, try a different Desktop. My VMs typically shutdown within 15 seconds unless I have a very big app running which has to shut down gracefully.
TSU
After moving from 13.2 to Tumbleweed my system boot in 37 seconds and shutdown very fast. This was true until yesterday. My system boots in one minute now. I checked systemd-analyze blame and it shows:
31.423s dev-sda1.device
21.471s systemd-udev-settle.service
16.694s systemd-journald.service
12.060s systemd-journal-flush.service
31.423s dev-sda1.device
21.471s systemd-udev-settle.service
16.694s systemd-journald.service
12.060s systemd-journal-flush.service
11.382s display-manager.service
10.941s systemd-tmpfiles-clean.service
9.137s apache2.service
8.368s postfix.service
7.240s libvirtd.service
4.909s ModemManager.service
3.231s sshd.service
3.025s NetworkManager.service
2.958s vboxdrv.service
2.896s dvb.service
2.717s systemd-fsck@dev-disk-by\x2duuid-9705bf5a\x2d3bb1\x2d46ea\x2db67f\x2d6e5b0418cd94.service
2.404s lvm2-activation-early.service
2.400s dev-disk-by\x2duuid-13df39a5\x2d20ae\x2d4c26\x2da7cf\x2deef1fe75fa88.swap
2.296s polkit.service
2.278s usr-local.mount
2.052s var-opt.mount
2.043s systemd-udevd.service
2.034s boot-grub2-x86_64\x2defi.mount
1.945s alsa-restore.service
1.932s nscd.service
1.682s avahi-daemon.service
1.502s wpa_supplicant.service
1.362s tmp.mount
1.278s srv.mount
1.157s systemd-tmpfiles-setup.service
1.091s opt.mount
855ms systemd-remount-fs.service
808ms sys-kernel-debug.mount
808ms dev-mqueue.mount
562ms systemd-udev-trigger.service
543ms lvm2-activation-net.service
542ms systemd-udev-root-symlink.service
530ms kmod-static-nodes.service
528ms systemd-tmpfiles-setup-dev.service
516ms systemd-update-utmp.service
493ms bluetooth.service
450ms systemd-user-sessions.service
390ms iscsi.service
372ms dev-hugepages.mount
301ms var-tmp.mount
283ms home.mount
250ms \x2esnapshots.mount
31.423s dev-sda1.device
31.423s dev-sda1.device
21.471s systemd-udev-settle.service
16.694s systemd-journald.service
12.060s systemd-journal-flush.service
11.382s display-manager.service
10.941s systemd-tmpfiles-clean.service
9.137s apache2.service
8.368s postfix.service
7.240s libvirtd.service
4.909s ModemManager.service
3.231s sshd.service
3.025s NetworkManager.service
2.958s vboxdrv.service
2.896s dvb.service
2.717s systemd-fsck@dev-disk-by\x2duuid-9705bf5a\x2d3bb1\x2d46ea\x2db67f\x2d6e5b0418cd94.service
2.404s lvm2-activation-early.service
2.400s dev-disk-by\x2duuid-13df39a5\x2d20ae\x2d4c26\x2da7cf\x2deef1fe75fa88.swap
2.296s polkit.service
2.278s usr-local.mount
2.052s var-opt.mount
2.043s systemd-udevd.service
2.034s boot-grub2-x86_64\x2defi.mount
1.945s alsa-restore.service
1.932s nscd.service
1.682s avahi-daemon.service
1.502s wpa_supplicant.service
I restarted my system many times and it boot in one minute all of time! Log shows, dev-sda1 (root filesystem of btrfs type) unit takes very long time. Maybe filesystem check? But this is not case - system boot in one minute every time!
check the partition with the BTRFS utilities maybe run fsck on it too, check logs.
I have performed defragmentation on my root and restart machine. My system now boots not in 1 minute 10 seconds, but in 52 seconds. But this is still not 37 seconds. What can I do? I decided to update dracut, but I haven’t update anything before my system slows down.
When system boot, there’s many messages like :
systemd-udevd[402]: maximum number (136) of children reached