some issues, causes openSuSE 12.1 to boot slow

Hi
i have 12.1 on my computer but it takes something around 20 seconds to show me the gdm/kdm. i think that it must be less than this, so i’ve posted a picture showing were the boot process spends most of it’s time. the photo is at bottom of the post (sorry for quality, awful HTC camera :slight_smile: ) and these the issues i’m talking about:

  • first it fails to execute ifup-sysctl at the 3rd line. what is the problem? how can it be solved?
  • seconds it seems that it is doing a fsck. as far as i can remember, fsck was mandatory only one time in about 50 boots; but it does it every time. is everything ok? or it is the problem?
  • after that it shows an error with graphics card. what does it say? is it a real problem? also my graphics card is nvidia, but it talks about intel. what is it?
  • just after the previous error, it prints an error about SN06. it think it is a problem with vaio laptops, huh? because i had it in ubuntu too.
  • the last line takes the most time, or it seems so. i think it is showing the fsck report, and telling that just everything is ok! after printing this line, the system sticks maybe around 4-5 seconds, that is really annoying. i don’t know whether this lines consumes this time or the processes that are executed after that are doing this. is there any better log to look into?

this is the phto of lines printed during the boot process:
http://s3.kkloud.com/gett/static/scaled/98qT4gD-0.enqbbygtmjnstt9.jpg

if you think additional info/log is required, just let me know. thanx in advance for any help/idea to solve this :wink:

20 seconds? Isn’t too bad.

/var/log/messages
Might help.

sorry, i have entered wrong timings. i rebooted the system and measured again with a clock:
from grub menu to gdm, takes 57 seconds. in the line after “Mounting root” it sticks around 10 seconds, and it takes near 30 seconds after the last line.

On 2012-02-15 21:16, sazary wrote:
>
> Hi
> i have 12.1 on my computer but it takes something around 20 seconds to
> show me the gdm/kdm. i think that it must be less than this, so i’ve
> posted a picture showing were the boot process spends most of it’s time.

In a terminal, as root, run:


systemd-analyze blame

and find out where the time is spent. Alternatively, you can also do


systemd-analyze plot > p.svg

Then you can use “display p.svg” to see the graphics, or use the tool you
prefer. The graphics shows where time is used.

> - seconds it seems that it is doing a fsck. as far as i can remember,
> fsck was mandatory only one time in about 50 boots; but it does it
> every time. is everything ok? or it is the problem?

I don’t remember, but some filesystem types are quick checked on every boot.

> - the last line takes the most time, or it seems so. i think it is

It just seems so, it is doing things that do not print any message.

But 20 seconds is fast.


Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

On 2012-02-15 21:56, sazary wrote:
>
> sorry, i have entered wrong timings. i rebooted the system and measured
> again with a clock:
> from grub menu to gdm, takes 57 seconds. in the line after “Mounting
> root” it sticks around 10 seconds, and it takes near 30 seconds after
> the last line.

The method I posted will tell you the exact timing and where it waits.


Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

wow! really thanx! that was a powerful tool. based on it’s output, it takes 55 seconds to boot, that i think is way too long. this is the blame output:


  7172ms localnet.service
  6920ms systemd-vconsole-setup.service
  5682ms cycle.service
  5246ms var-lock.mount
  4985ms media.mount
  4949ms var-run.mount
  4919ms udev-trigger.service
  4917ms dev-hugepages.mount
  4884ms sys-kernel-security.mount
  4855ms sys-kernel-debug.mount
  4855ms bootsplash-startup.service
  4839ms dev-mqueue.mount
  4836ms remount-rootfs.service
  4764ms udev.service
  4739ms systemd-remount-api-vfs.service
  2948ms systemd-sysctl.service
  1031ms bootsplash-quit.service
   677ms systemd-readahead-replay.service
   644ms systemd-readahead-collect.service
   603ms systemd-logind.service
   387ms syslog.service
   246ms SuSEfirewall2_setup.service
   207ms apparmor.service
   201ms cups.service
   187ms systemd-tmpfiles-setup.service
   185ms xdm.service
   181ms dbus.service
   171ms NetworkManager.service
   169ms avahi-daemon.service
   151ms console-kit-log-system-start.service
   145ms rc-local.service
   140ms fbset.service
   135ms systemd-user-sessions.service
   133ms ntp.service
   130ms irq_balancer.service
   130ms microcode.ctl.service
   129ms cpufreq.service
   126ms network.service
   122ms SuSEfirewall2_init.service
   114ms purge-kernels.service
    89ms haveged.service
    85ms pcscd.service
    81ms acpid.service
    78ms mcelog.service
    72ms network-remotefs.service
    67ms splash_early.service
    51ms bluez-coldplug.service
    48ms auditd.service
    38ms console-kit-daemon.service
    37ms splash.service
    29ms home.mount
    27ms rpcbind.service
     4ms accounts-daemon.service
     0ms sys-fs-fuse-connections.mount

and this is the plot output:
http://i.imgur.com/1YqB2.jpg

based on the image, i think that the problematic process is NetworkManager, exactly “NetworkManager-wait-online.service”. am i right? if yes, then what should i do?

thanx :wink:

On 2012-02-16 08:26, sazary wrote:
> based on the image, i think that the problematic process is
> NetworkManager, exactly “NetworkManager-wait-online.service”. am i
> right? if yes, then what should i do?

Look at the log to see what it does. Wait for an IP? Wait for wifi? Wait
for a network share?


Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

But you’ve said that most of the time is spent on the screen that you’ve posted and it has nothing to do with networking directly. The posted picture shows that most of the time is spent on fsck. Network services may take a long time to set up, because it cannot find network configuration script file at first and fsck on /dev/sda5 (this partition is mounted as “/”, right?) is run to fix it. I am not sure, but I think it may work this way.

fsck shouldn’t run every time you boot if you haven’t told the OS to do so - there might be something wrong with your hard drive, especially with partition /dev/sda5.

EDIT: I’ve checked and I get the same screen during boot, including missing network script and fsck, but It hangs only for a second at it.