Unusually slow boot on computer with separate boot partition. [SOLVED]

cowlitzron · 2014/03/28, 19:34:23

I have Siduction on two computers. On one of them I have a separate boot partition and I dual boot with Windows 7. I have an unusual slow boot on that computer. The boot partition is ext2. I have root and home partitions that are ext4. The last systemd analyze report shows a total boot time of 3 minutes and 10.836 seconds of which 3 minutes and 5.956 seconds is show loading up userspace. My /etc/fstab is below.

UUID=AACED2E5CED2A8B9 /media/disk1part1 ntfs auto,users,ro,dmask=0022,fmask=0133,nls=utf8 0 0
UUID=5292D3DB92D3C1A1 /media/disk1part2 ntfs auto,users,rw,dmask=0022,fmask=0133,nls=utf8 0 0
UUID=90ab705d-7948-4724-bd9a-2e9f69990d47 /boot ext2 defaults,relatime,errors=remount-ro 0 2
UUID=b6de525c-802e-43a1-8083-163a3a5fc5b2 / ext4 defaults,relatime,errors=remount-ro 0 1
UUID=6686db98-d6b0-4b54-bb39-5578507902b0 none swap sw 0 0
UUID=4fca0560-36b4-41ab-8755-c206ffe220b3 /home ext4 defaults,relatime,errors=remount-ro 0 2

The other computer which has /boot in the root partition, boots up in less than 20 seconds. So, I wonder if systemd is having problems with mounting when there is a separate boot partition?

devil · 2014/03/28, 22:30:56

Can we see the relevant part of systemd-analyze blame?

greetz
devil

cowlitzron · 2014/03/29, 00:01:46

Quote from: devil on 2014/03/28, 22:30:56
Can we see the relevant part of systemd-analyze blame?

greetz
devil

Here is the portion of systemd-analyze blame with processes taking up over half a second.

6.813s systemd-udev-settle.service
4.937s dirmngr.service
4.812s keyboard-setup.service
4.428s systemd-suspend.service
3.617s avahi-daemon.service
3.542s systemd-logind.service
2.809s loadcpufreq.service
2.764s acpi-fakekey.service
2.309s network-manager.service
1.771s systemd-fsck-root.service
1.714s bootlogs.service
1.396s systemd-modules-load.service
1.298s nfs-common.service
1.268s lightdm.service
1.214s networking.service
1.212s kdm.service
1.188s hdparm.service
1.125s sys-kernel-debug.mount
1.124s dev-mqueue.mount
1.123s dev-hugepages.mount
1.072s systemd-udev-trigger.service
902ms lm-sensors.service
879ms resolvconf.service
857ms irqbalance.service
830ms systemd-fsck@dev-disk-by\x2duuid-4fca0560\x2d36b4\x2d41ab\x2d8755\x2dc206ffe220b3.service
776ms systemd-udevd.service
767ms acpi-support.service
756ms media-disk1part1.mount
726ms lvm2-activation-early.service
694ms systemd-update-utmp-runlevel.service
691ms glances.service
592ms media-disk1part2.mount
586ms screen-cleanup.service
584ms rpcbind.service
584ms saned.service
561ms vnstat.service
558ms systemd-remount-fs.service
552ms systemd-fsck@dev-disk-by\x2duuid-90ab705d\x2d7948\x2d4724\x2dbd9a\x2d2e9f69990d47.service

The times aren't out of the ordinary. I am wondering if it is failing to start up more than one service at a time? I'd like to know if it is a problem with having a separate boot partition with ext2?

devil · 2014/03/29, 00:34:25

You were saying in your first post:

QuoteThe last systemd analyze report shows a total boot time of 3 minutes and 10.836 seconds of which 3 minutes and 5.956 seconds is show loading up userspace.

I cannot see that in your paste.
I have no idea how a separate boot partition plays with systemd, never had one or the need for it.

greetz
devil

GoinEasy9 · 2014/03/29, 03:56:18

When I used Fedora, they recommended, and I had, a separate /boot partition. I don't think that using systemd with or without a separate /boot partition should make any difference in speed. If you're using Grub2 to boot both Windows 7 and siduction, I'd start investigating there.

You can also type "journalctl -b" in a terminal and see if there are any errors that show up during boot.

Looking at your whole systemd-analyze blame would also be helpful, like devil asked. Copy/Paste it in a code field.

Just my 2 cents.

cowlitzron · 2014/03/30, 01:05:29

Here is the complete systemd-analyze blame field:

Code Select


6.162s ModemManager.service
          5.888s systemd-udev-settle.service
          5.641s NetworkManager.service
          5.601s dirmngr.service
          4.059s avahi-daemon.service
          3.988s systemd-logind.service
          3.790s systemd-fsck-root.service
          2.962s keyboard-setup.service
          2.230s systemd-fsck@dev-disk-by\x2duuid-4fca0560\x2d36b4\x2d41ab\x2d8755\x2dc206ffe220b3.service
          2.083s loadcpufreq.service
          2.035s systemd-fsck@dev-disk-by\x2duuid-90ab705d\x2d7948\x2d4724\x2dbd9a\x2d2e9f69990d47.service
          2.023s ntp.service
          1.924s lm-sensors.service
          1.708s acpi-fakekey.service
          1.643s bootlogs.service
          1.639s kdm.service
          1.562s networking.service
          1.550s lvm2-activation-early.service
          1.441s hdparm.service
          1.382s lightdm.service
          1.308s systemd-modules-load.service
          1.230s nfs-common.service
          1.115s systemd-tmpfiles-setup-dev.service
          1.015s sys-kernel-debug.mount
          1.014s dev-mqueue.mount
          1.012s dev-hugepages.mount
          1.011s media-disk1part2.mount
           976ms systemd-udev-trigger.service
           912ms media-disk1part1.mount
           815ms polkitd.service
           747ms acpi-support.service
           715ms irqbalance.service
           644ms resolvconf.service
           609ms rpcbind.service
           567ms systemd-remount-fs.service
           537ms saned.service
           527ms vnstat.service
           504ms kbd.service
           476ms systemd-user-sessions.service
           463ms keymap.service
           461ms console-kit-log-system-start.service
           429ms screen-cleanup.service
           376ms gpm.service
           349ms dns-clean.service
           339ms systemd-sysctl.service
           326ms console-setup.service
           293ms upower.service
           284ms glances.service
           259ms lvm2-activation.service
           242ms rc-local.service
           189ms ifplugd.service
           174ms systemd-update-utmp-runlevel.service
           150ms wpa_supplicant.service
           149ms boot.mount
           145ms alsa-restore.service
           141ms console-kit-daemon.service
           114ms systemd-tmpfiles-clean.service
           108ms home.mount
           105ms smartmontools.service
            94ms pppd-dns.service
            85ms systemd-tmpfiles-setup.service
            85ms motd.service
            80ms hddtemp.service
            47ms systemd-udevd.service
            45ms udisks.service
             7ms cpufrequtils.service
             5ms systemd-journal-flush.service
             3ms systemd-random-seed-load.service
             3ms sys-fs-fuse-connections.mount
             3ms run-lock.mount
             1ms run-user.mount

I also got the following error message with journalctl -b

Code Select


Mar 29 16:44:37 cowlitzSid2 systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-6686db98\x2dd6b0\x2d4b54\x2dbb39\x2d$
Mar 29 16:44:37 cowlitzSid2 systemd[1]: Dependency failed for /dev/disk/by-uuid/6686db98-d6b0-4b54-bb39-5578507902b0.

This is the uuid of my swap partition.

devil · 2014/03/30, 08:49:54

1.) please put output like above in code brackets for better readability and orevent endless scrolling. The editor offers it on a button with a #. Fixed that for ya.

2.) comment the offending line in fstab and reboot. See if it still happens

greetz
devil

sunrat · 2014/03/30, 08:54:25

Use blkid to verify that you have the correct UUID for your swap partition in fstab.
And what devil said of course,

ayla · 2014/03/30, 09:46:37

Just for info:

I had a problem a few days ago when installing another linux on my system for testing.
If I remember right, in the past when installing more then one linux systems, swap was detected and used as is -or maybe I didn't recogniced the change because before systemd it does not cause problems.
This time my swap partition was detected also but was obviously formatted new without any message.
So the uuid changed and my installed system of course timed out as above.

greets ayla

devil · 2014/03/30, 09:57:15

Never heard of that. So that clearly goes in the direction sunrat also pointed to. Check UUID with h blkid command and check if fstab has the right one.

greetz
devil

sunrat · 2014/03/30, 13:46:21

Quote from: ayla on 2014/03/30, 09:46:37
This time my swap partition was detected also but was obviously formatted new without any message.

That happened to me after installing KX Studio on another partition. Which is exactly why I made the suggestion above.

ayla · 2014/03/30, 15:20:56

I'm not quiet sure which distri it was in my case, I tried a few in the last few days, but I suspect Kali-Linux.

Whatever, I decided to use labels insteed of uuid's -as sometimes suggested here in the forum- in future to prevent such behaviour.

greets
ayla

cowlitzron · 2014/03/30, 22:01:27

I solved the problem. After, looking at blkid, I found out I had a different UUID for the swap partition than I had listed in fstab. This was caused by my having installed another distro on a usb hard drive after I installed siduction. When I installed the other distro, I formatted the swap partition used by siduction and that installer gave it a different UUID. So, in order to solve the problem, I changed the UUID in the siduction fstab to LABEL=Swap . Then, I put in the siduction DVD and booted into it. I used Gparted to add the label "Swap" to the swap partition. I rebooted into siduction. I was able to get from the GRUB menu to the login screen in less than 45 seconds. Thanks for helping me!

devil · 2014/03/30, 23:08:38

It should be around 3-10 seconds, depending on your hardware.

greetz
devil

Unusually slow boot on computer with separate boot partition. [SOLVED]

cowlitzron

cowlitzron

cowlitzron

cowlitzron