Mageia forum

A while back I was using Mageia 2 on my Dell laptop and I really liked it except for one thing. That thing was that it took an age to boot up and shut down so one day after being fed up of waiting for the OS to boot up I decided I would use another distro. I have a copy of Mageia 3 on disk as well as Mageia 4 beta 1 on disk and am considering installing Mageia 3 but I am a little concerned that the boot up and shut down speed has not been fixed.

I would like to et some feedback, both positive and negative of using Mageia 3, is it an improvement of Mageia 2?

Boot time has been just fine here and with many other users, since Mageia 1. And boot time has always been improved, got a little better with every release.

Did you at least take a look which step in the boot process took unusually long? Also, what does "an age" mean in particular? One minute, 5 minutes, an hour, more/less?

EDIT:
It would be good to provide at least the output of

Code: Select all

systemd-analyze

and

Code: Select all

systemd-analyze blame

What's also quite good is

Code: Select all

systemd-analyze plot > boot.svg

and then examine the resulting boot.svg image with e.g. Firefox to see which part takes really long.
You may need to install systemd-tools for those commands.

Here's mine for Mageia 3:

Code: Select all

[doktor5000@Mageia3 ~]$ systemd-analyze
Startup finished in 2844ms (kernel) + 2050ms (initramfs) + 44316ms (userspace) = 49211ms

[doktor5000@Mageia3 ~]$ systemd-analyze blame
 28498ms network-up.service
  4460ms ntpdate.service
  2240ms mandriva-everytime.service
  1224ms systemd-udev-settle.service
   403ms bluetooth.service
   376ms NetworkManager.service
   334ms microcode_ctl.service
   321ms wine.service
   287ms lm_sensors.service
   280ms mandi.service
   250ms iptables.service
   238ms sensord.service
   230ms partmon.service
   225ms virtualbox.service
   221ms systemd-logind.service
   220ms resolvconf.service
   214ms upower.service
   207ms udisksd.service
   198ms avahi-daemon.service
   198ms ip6tables.service
   197ms msec.service
   164ms acpid.service
   163ms media-win_c.mount
   161ms ksm.service
   151ms hddtemp.service
   148ms saslauthd.service
   136ms cpupower.service
   120ms libvirt-guests.service
   118ms nscd.service
   101ms fedora-loadmodules.service
   101ms systemd-readahead-replay.service
    96ms systemd-udev-trigger.service
    91ms sshd.service
    87ms systemd-readahead-collect.service
    85ms fedora-readonly.service
    75ms dev-mqueue.mount
    70ms mandriva-kmsg-loglevel.service
    65ms mandriva-save-dmesg.service
    62ms proc-sys-fs-binfmt_misc.mount
    61ms mandriva-boot-links.service
    59ms systemd-user-sessions.service
    47ms freshclam.service
    44ms systemd-udevd.service
    39ms tmp.mount
    36ms dev-hugepages.mount
    35ms systemd-remount-fs.service
    35ms teamviewerd.service
    34ms fedora-wait-storage.service
    34ms udisks2.service
    32ms systemd-vconsole-setup.service
    30ms systemd-modules-load.service
    30ms chroot_home.mount
    28ms systemd-sysctl.service
    27ms chroot_root.mount
    25ms sys-kernel-debug.mount
    24ms polkit.service
    23ms ksmtuned.service
    18ms systemd-tmpfiles-setup.service
    18ms home.mount
    11ms rtkit-daemon.service
    10ms sys-fs-fuse-connections.mount
     7ms ntpd.service

Thanks for the tip, when I install Mageia 3 and I have the same issue I will perform the above commands to identify to culprit

Mageia 3 is pretty fast - but if you still feel the need to speed up boot time you can do so with systemd:

Code: Select all

sudo systemctl enable systemd-readahead-collect systemd-readahead-replay

More here

Isn't this by default wanted by default.target, meaning that it's enabled by default?

An age?, like Dok said, how long?
Never considered Mageia to be slow to boot, unless there's been a driver issue, Here's mine : This is with auto log-on enabled.

Code: Select all

[pete@com1 ~]$ systemd-analyze
Startup finished in 1112ms (kernel) + 1202ms (initramfs) + 11893ms (userspace) = 14208ms
[pete@com1 ~]$ systemd-analyze blame
  4469ms ntpdate.service
  3100ms network-up.service
  2885ms mandriva-everytime.service
   714ms systemd-udev-settle.service
   383ms NetworkManager.service
   193ms polkit.service
   156ms fedora-storage-init.service
   114ms mandi.service
   108ms nfs-lock.service
    88ms resolvconf.service
    76ms partmon.service
    69ms speech-dispatcherd.service
    64ms fedora-readonly.service
    60ms fedora-storage-init-late.service
    59ms microcode_ctl.service
    58ms var-lib-nfs-rpc_pipefs.mount
    58ms virtualbox.service
    51ms systemd-udev-trigger.service
    42ms smb.service
    42ms dev-mqueue.mount
    41ms systemd-udevd.service
    40ms systemd-vconsole-setup.service
    40ms mandriva-kmsg-loglevel.service
    39ms dev-hugepages.mount
    39ms hddtemp.service
    39ms sys-kernel-debug.mount
    38ms udisks2.service
    38ms systemd-remount-fs.service
    37ms wine.service
    32ms bluetooth.service
    31ms colord.service
    28ms upower.service
    28ms msec.service
    26ms systemd-logind.service
    24ms avahi-daemon.service
    24ms colord-sane.service
    23ms udisksd.service
    17ms lm_sensors.service
    11ms sshd.service
    10ms rtkit-daemon.service
     9ms cpupower.service
     9ms mandriva-save-dmesg.service
     8ms sensord.service
     8ms home.mount
     7ms proc-sys-fs-binfmt_misc.mount
     7ms systemd-user-sessions.service
     6ms systemd-readahead-collect.service
     6ms acpid.service
     6ms systemd-readahead-replay.service
     5ms xinetd.service
     5ms rpcbind.service
     5ms ntpd.service
     4ms systemd-modules-load.service
     4ms mandriva-boot-links.service
     3ms nfs-idmap.service
     3ms fedora-wait-storage.service
     3ms systemd-sysctl.service
     2ms systemd-tmpfiles-setup.service
     2ms tmp.mount
     1ms osspd.service
     1ms sys-fs-fuse-connections.mount

This is a desktop btw.

A lot is gonna depend on hardware to be frank. HDD speed and what not.

Yep, but even with SSD blocking factor is often network service. So there's definitely still room for cleaning up or reducing the number of services and their start-up time.
Like in your case, 4 seconds for ntpdate and 3 seconds for network-up - they will partly run in parallel, but still ...