Hello
When I boot my PC, the green progress bar takes an age to complete, and then i’m left staring at a black screen for 4-5 minutes before the splash appears, which takes a further 2-3 minutes to load my desktop. How do I go about finding out what is causing this painfully slow boot?
Installl systemd-analyze from the Software Manager, and run
systemd-analyze blame
After timing my boot I was able to determine that my system was booting faster than I thought. That said, things are still too slow.
Please could you take a look at the following and tell me what I can do to improve things:
colin@linux-rjqz:~> systemd-analyze blame
33481ms avahi-daemon.service
33359ms SuSEfirewall2_init.service
24940ms remount-rootfs.service
10233ms systemd-modules-load.service
7864ms systemd-vconsole-setup.service
7030ms network.service
2718ms localnet.service
2715ms udev-root-symlink.service
2120ms sys-kernel-debug.mount
2081ms dev-hugepages.mount
2036ms sys-kernel-security.mount
2030ms dev-mqueue.mount
1865ms var-lock.mount
1859ms var-run.mount
1853ms media.mount
1506ms systemd-remount-api-vfs.service
1321ms vboxdrv.service
1216ms systemd-logind.service
1195ms cycle.service
1165ms udev.service
1059ms home.mount
645ms syslog.service
637ms systemd-readahead-replay.service
532ms cpufreq.service
529ms fbset.service
491ms console-kit-log-system-start.service
480ms postfix.service
479ms ntp.service
455ms systemd-readahead-collect.service
360ms network-remotefs.service
323ms SuSEfirewall2_setup.service
320ms systemd-tmpfiles-setup.service
134ms boot.mount
126ms rc-local.service
122ms udev-trigger.service
116ms xdm.service
109ms systemd-sysctl.service
81ms systemd-user-sessions.service
74ms console-kit-daemon.service
40ms acpid.service
23ms bluez-coldplug.service
23ms upower.service
15ms rtkit-daemon.service
1ms sys-fs-fuse-connections.mount
colin@linux-rjqz:~>
Why does avahi take so much time to load? I don’t use it so I don’t really know, but it’s on top of your list.
Also the firewall service shouldn’t take so much time, at least it does not on my system.
3539ms remount-rootfs.service
2319ms systemd-modules-load.service
1852ms systemd-vconsole-setup.service
1753ms SuSEfirewall2_init.service
1569ms rc-local.service
1194ms localnet.service
996ms vmware.service
866ms media.mount
820ms var-lock.mount
786ms var-run.mount
761ms sys-kernel-security.mount
757ms sys-kernel-debug.mount
739ms vmware-USBArbitrator.service
645ms dev-hugepages.mount
632ms udev-root-symlink.service
623ms dev-mqueue.mount
610ms systemd-remount-api-vfs.service
587ms network.service
550ms hddtemp.service
494ms systemd-logind.service
473ms systemd-readahead-replay.service
449ms systemd-sysctl.service
448ms SuSEfirewall2_setup.service
382ms syslog.service
258ms systemd-readahead-collect.service
163ms systemd-tmpfiles-setup.service
131ms home.mount
128ms console-kit-log-system-start.service
97ms xdm.service
80ms console-kit-daemon.service
46ms udev.service
28ms udev-trigger.service
27ms smpppd.service
15ms systemd-user-sessions.service
[QUOTE=finders;2505135]Why does avahi take so much time to load? I don’t use it so I don’t really know, but it’s on top of your list.
Also the firewall service shouldn’t take so much time, at least it does not on my system.
Can you tell me what avahi does and what I can do to disable it? As far as the firewall is concerned, I have a hardware firewall router so I probably don't need to use the suse firewall.You can either uninstall it, delete it from /etc/init.d/ or disable it from yast. That’s how I would solve it.
But if you don’t know what it does or why it’s there, leaving it alone might be a good idea.
Maybe some of your programs depend on it, I can only guess because I don’t use it.
On 2012-11-20 10:36, finders wrote:
>
> chyrania;2504845 Wrote:
>>
>> colin@linux-rjqz:~> systemd-analyze blame
>> 33481ms avahi-daemon.service
>> 33359ms SuSEfirewall2_init.service
>> 24940ms remount-rootfs.service
>> 10233ms systemd-modules-load.service
>> 7864ms systemd-vconsole-setup.service
>> 7030ms network.service
>>
>
> Why does avahi take so much time to load? I don’t use it so I don’t
> really know, but it’s on top of your list.
Don’t be misled by analyze blame. That a service ends in thirty seconds
doesn’t mean that it is holding and delaying boot by thirty seconds.
Instead use the boot graph.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” (Minas Tirith))
Can you tell me what avahi does and what I can do to disable it?
You will need this if you want to share files and printers with Apples line of computers.
As far as my experience goes with these services, they all run in parallel by default, so if one of them stalls, others continue on top of it.
If however I use sysvinit-init and set RUN_PARALLEL=“no” then the system would run one at the time so if one of them stalls, others won’t start.
I may be wrong but that’s how it used to work before systemd. Anyway, it’s an interesting subject.
I’ve seen certain delays with sysvinit , but almost exclusively related to ifconfig, ntp and dns.
Never seen a firewall taking this long, something’s obviously wrong with it.
On 2012-11-20 17:56, finders wrote:
> Never seen a firewall taking this long, something’s obviously wrong
> with it.
it can be waiting for the network to be stablished, for example.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” (Minas Tirith))
Wouldn’t that cause ntp.service to hang as well?
This reminds me of a time when I had to get rid of network manager.
Switched to static ifup and it’d cut boot time in half, no idea if that’s still the case with systemd.
On 2012-11-20 19:56, finders wrote:
> Wouldn’t that cause ntp.service to hang as well?
Yes.
> This reminds me of a time when I had to get rid of network manager.
> Switched to static ifup and it’d cut boot time in half, no idea if
> that’s still the case with systemd.
Could be.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” (Minas Tirith))
I uninstalled avahi and disabled my firewall but these changes don’t appear to have improved my boot time. Read below for analyze blame output:
colin@linux-rjqz:~> systemd-analyze blame
38944ms network.service
13036ms remount-rootfs.service
6492ms systemd-sysctl.service
4756ms systemd-modules-load.service
4491ms systemd-vconsole-setup.service
2181ms systemd-logind.service
1762ms localnet.service
1405ms home.mount
1376ms vboxdrv.service
1185ms udev-root-symlink.service
1089ms sys-kernel-debug.mount
1033ms media.mount
1020ms dev-hugepages.mount
1016ms sys-kernel-security.mount
1009ms dev-mqueue.mount
988ms udev.service
940ms ntp.service
871ms network-remotefs.service
731ms var-lock.mount
729ms var-run.mount
705ms cycle.service
633ms systemd-remount-api-vfs.service
621ms postfix.service
428ms syslog.service
416ms systemd-readahead-replay.service
366ms systemd-tmpfiles-setup.service
252ms boot.mount
239ms udev-trigger.service
235ms console-kit-log-system-start.service
210ms systemd-readahead-collect.service
197ms fbset.service
190ms cpufreq.service
165ms rtkit-daemon.service
97ms upower.service
92ms acpid.service
75ms xdm.service
63ms console-kit-daemon.service
61ms systemd-user-sessions.service
21ms bluez-coldplug.service
12ms rc-local.service
1ms sys-fs-fuse-connections.mount
colin@linux-rjqz:~>
Any ideas?
On 2012-11-21 03:56, chyrania wrote:
>
> I uninstalled avahi and disabled my firewall but these changes don’t
> appear to have improved my boot time.
As I expected.
> Read below for analyze blame
> output:
As I said, you have to look at the graph instead.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” (Minas Tirith))
I’m not familiar with the boot graph. Would it be possible for you to point me in the right direction?
On 2012-11-22 01:06, chyrania wrote:
> I’m not familiar with the boot graph. Would it be possible for you to
> point me in the right direction?
Not at the moment, see signature. A hint instead: look at the options
the command “systemd-analyze” has.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” (Minas Tirith))
Just run “systemd-analyze plot > /tmp/boot.svg” and open the file with firefox. There you should be able to identify the critical path that causes the delay.
Do you use btrfs?