Mageia forum

After last update - 15 august 2019 - boot Mageia 7 became terribly slow.
Did any body else experience similar phenomenon?
Mine is Mageia 7 dual screen cinnamon
jjf

I have the latest updates and haven't experienced any slowdown on boot. What's the output of the "systemd-analyze critical-chain" command on your terminal?

Code: Select all

systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

graphical.target @48.177s
└─multi-user.target @48.177s
  └─smb.service @44.002s +4.174s
    └─nmb.service @34.786s +9.214s
      └─network-online.target @34.527s
        └─network.target @34.481s
          └─network-up.service @21.024s +13.456s
            └─basic.target @21.022s
              └─mandriva-everytime.service @11.314s +9.707s
                └─local-fs.target @11.312s
                  └─local-fs-pre.target @11.281s
                    └─systemd-tmpfiles-setup-dev.service @4.191s +1.622s
                      └─kmod-static-nodes.service @3.696s +493ms
                        └─systemd-journald.socket @3.683s
                          └─system.slice @3.586s
                            └─-.slice @3.586s


JJF

I suppose there's nothing wrong there, apart from some network delays. Maybe there's some issue with Cinnamon (I'm sorry, I can't help you with that, never used it)

Same very slow boot when logging into Plasma
Any clue?

You could save at least 20s from disabling network-up and mandriva-everytime services. As root

Code: Select all

systemctl mask mandriva-everytime.service
systemctl disable network-up.service

But it would be more helpful if you could run the following as root and then afterwards attach the resulting file boot.svg here:

Code: Select all

systemd-analyze plot > boot.svg

Also, as you only mention slow boot, I suppose the slow part if before the display manager actually starts?
Please also show the output as root of

Code: Select all

dkms status

1. boot.svg attached
2. The slow part starts after I enter the login name and password
3.

Code: Select all

dkms status
virtualbox, 5.2.6-1.mga6, 4.14.16-desktop-1.mga6, x86_64: installed-binary from 4.14.16-desktop-1.mga6
virtualbox, 5.2.2-1.mga6, 4.14.10-desktop-1.mga6, x86_64: installed-binary from 4.14.10-desktop-1.mga6
virtualbox, 5.1.26-1.mga6, 4.9.50-desktop-1.mga6, x86_64: installed-binary from 4.9.50-desktop-1.mga6
virtualbox, 5.1.26-1.mga6, 4.9.40-desktop-1.mga6, x86_64: installed-binary from 4.9.40-desktop-1.mga6
virtualbox, 5.2.8-1.mga6, 4.14.30-desktop-3.mga6, x86_64: installed-binary from 4.14.30-desktop-3.mga6
virtualbox, 6.0.8-1.mga6, 4.14.121-desktop-1.mga6, x86_64: installed-binary from 4.14.121-desktop-1.mga6
virtualbox, 5.1.10-1.1.mga5, 4.4.32-desktop-1.mga5, x86_64: installed-binary from 4.4.32-desktop-1.mga5
virtualbox, 6.0.8-1.mga6, 4.14.119-desktop-1.mga6, x86_64: installed-binary from 4.14.119-desktop-1.mga6
virtualbox, 5.1.22-1.mga5, 4.4.68-desktop-1.mga5, x86_64: installed-binary from 4.4.68-desktop-1.mga5
virtualbox, 6.0.6-1.mga6, 4.14.106-desktop-1.mga6, x86_64: installed-binary from 4.14.106-desktop-1.mga6
virtualbox, 6.0.10-1.mga7, 5.1.18-desktop-1.mga7, x86_64: installed-binary from 5.1.18-desktop-1.mga7
virtualbox, 5.2.18-1.mga6, 4.14.69-desktop-1.mga6, x86_64: installed-binary from 4.14.69-desktop-1.mga6
virtualbox, 5.1.18-1.mga5, 4.4.50-desktop-2.mga5, x86_64: installed-binary from 4.4.50-desktop-2.mga5
virtualbox, 5.1.18-1.mga5, 4.4.55-desktop-1.mga5, x86_64: installed-binary from 4.4.55-desktop-1.mga5
virtualbox, 5.2.24-1.mga6, 4.14.100-desktop-1.mga6, x86_64: installed-binary from 4.14.100-desktop-1.mga6
virtualbox, 6.0.10-1.mga7, 5.1.20-desktop-2.mga7, x86_64: installed-binary from 5.1.20-desktop-2.mga7
virtualbox, 5.1.22-1.mga5, 4.4.59-desktop-1.mga5, x86_64: installed-binary from 4.4.59-desktop-1.mga5
virtualbox, 5.2.12-1.mga6, 4.14.44-desktop-2.mga6, x86_64: installed-binary from 4.14.44-desktop-2.mga6
virtualbox, 5.1.22-1.mga5, 4.4.65-desktop-1.mga5, x86_64: installed-binary from 4.4.65-desktop-1.mga5
virtualbox, 5.2.14-1.mga6, 4.14.56-desktop-1.mga6, x86_64: installed-binary from 4.14.56-desktop-1.mga6
virtualbox, 6.0.8-1.mga7, 5.1.14-desktop-1.mga7, x86_64: installed-binary from 5.1.14-desktop-1.mga7
virtualbox, 5.2.14-1.mga6, 4.14.50-desktop-2.mga6, x86_64: installed-binary from 4.14.50-desktop-2.mga6
virtualbox, 6.0.10-1.mga7, 5.2.7-desktop-1.mga7, x86_64: installed-binary from 5.2.7-desktop-1.mga7
virtualbox, 6.0.6-1.mga6, 4.14.116-desktop-1.mga6, x86_64: installed-binary from 4.14.116-desktop-1.mga6
virtualbox, 5.2.6-1.mga6, 4.14.13-desktop-1.mga6, x86_64: installed-binary from 4.14.13-desktop-1.mga6
virtualbox, 5.2.6-1.mga6, 4.14.18-desktop-1.mga6, x86_64: installed-binary from 4.14.18-desktop-1.mga6
virtualbox, 5.2.12-1.mga6, 4.14.40-desktop-1.mga6, x86_64: installed-binary from 4.14.40-desktop-1.mga6
virtualbox, 5.2.2-1.mga6, 4.9.56-desktop-1.mga6, x86_64: installed-binary from 4.9.56-desktop-1.mga6
virtualbox, 5.2.8-1.mga6, 4.14.25-desktop-1.mga6, x86_64: installed-binary from 4.14.25-desktop-1.mga6
virtualbox, 5.2.8-1.mga6, 4.14.20-desktop-1.mga6, x86_64: installed-binary from 4.14.20-desktop-1.mga6
virtualbox, 5.1.22-1.mga5, 4.4.74-desktop-1.mga5, x86_64: installed-binary from 4.4.74-desktop-1.mga5
virtualbox, 5.2.22-1.1.mga6, 4.14.78-desktop-1.mga6, x86_64: installed-binary from 4.14.78-desktop-1.mga6
virtualbox, 5.1.26-1.mga6, 4.9.43-desktop-1.mga6, x86_64: installed-binary from 4.9.43-desktop-1.mga6
virtualbox, 5.2.18-1.mga6, 4.14.65-desktop-1.mga6, x86_64: installed-binary from 4.14.65-desktop-1.mga6
virtualbox, 6.0.8-1.mga6, 4.14.127-desktop-1.mga6, x86_64: installed-binary from 4.14.127-desktop-1.mga6
virtualbox, 5.2.18-1.mga6, 4.14.70-desktop-2.mga6, x86_64: installed-binary from 4.14.70-desktop-2.mga6
virtualbox, 5.2.24-1.mga6, 4.14.104-desktop-2.mga6, x86_64: installed-binary from 4.14.104-desktop-2.mga6
virtualbox, 5.2.24-1.mga6, 4.14.89-desktop-1.mga6, x86_64: installed-binary from 4.14.89-desktop-1.mga6
virtualbox, 5.2.14-1.mga6, 4.14.62-desktop-2.mga6, x86_64: installed-binary from 4.14.62-desktop-2.mga6


Well, your system needs 130 seconds initialising the kernel until it actually starts systemd and the rest of the init process. Could also be some kind of hardware issue.

I'd also remove most of those virtualbox kernel modules, all the ones apart from the one for the kernel you're using or the 3 most recent ones or so.

There's also some more you can clean up:

systemd-journal-flush.service (17.118s)

=> clean older journal entries, try as root with

Code: Select all

journalctl --vacuum-size=100M


mandriva-everytime.service (10.578s)

=> mask this with

Code: Select all

systemctl mask mandriva-everytime.service


network-up.service (12.581s)
speech-dispatcherd.service (7.829s)

=> disable those if you don't need them.

Apart from all that either there's some kind of hardware problem or that is a really slow box, as quite a lot of simple services each take several seconds to load.

I am not at the box right now.
I will clean it according to your recommendations.
However, I do not understand why it did slow down ( significantly) only after the last update.
Is there a specific item that could have caused it?
JJF

Doktor5000
You suggested to disable as follows:

network-up.service (12.581s)
speech-dispatcherd.service (7.829s)
=> disable those if you don't need them.

Can you, please, tell me how?

JJF

Services can be managed through Mageia Control Centre->System

If you like to use systemd commands then it would be as root from a terminal:

Code: Select all

systemctl disable network-up.service

to disable the service and:

Code: Select all

systemctl mask network-up.service

to mask it so next time it gets not started if any other service might need it.

But of course you can also use the Mageia Control Center.

Doktor 5000
The boot still takes more than 120Secs.
Is there nay way to shorten it?
JJF

Yes, you could buy an SSD and install Mageia on that.

And the other thing as mentioned before:

Well, your system needs 130 seconds initialising the kernel until it actually starts systemd and the rest of the init process. Could also be some kind of hardware issue.

You must be joking as boot process slowed down significantly only after the last update..
JJF

Why should I be joking, and how does that disprove the fact that a hardware issue could still exist ?

The slow boot question was related to my home box.
At your suggestion I tested the box in my office
This box has windows 10, some other linux distro and mageia 6 installed on the same disk and behave very normal for 2 years or so.
I than Upgraded Mageia 6 to 7.
It took
3 mins and 15 secs
from selecting Mageia (in the boot-up screen) up until the splash username and password request appeared !!
This was not the case before I upgraded Mageia 6 to 7
The probability that the 2 different boxes need hardware check after upgrade does not sound normal to me
On another box in my office, a stand alone Mageia 7 boots-up very fast.
I have the feeling the the combination of Windows and Mageia 7 specifically is troublesome
Can you relate??
Tks JJF

Doktor5000

I posted 3 topics that seem to me to be related:

viewtopic.php?f=7&t=13029
viewtopic.php?f=7&t=12997
viewtopic.php?f=7&t=12865

On the disk where both Windows 7 and Mageia 7 are installed, I have 200GB of unformated partition

Could you, possibly, guide me how to freshly install mageia 7 on the free space, keeping the current files intacked and accessible, making the new installation my default boot? with the same user name and password?
(I am used to the mageia flavour since the days of Mandriva and prefer Cinnamon as my desktop. In addition, I consider myself as a newbe to Linux).
A step by step instructions will be appreciated)

Tks
JJF

JJF wrote:I have the feeling the the combination of Windows and Mageia 7 specifically is troublesome
Can you relate??

No, I can't relate, I also have a dualboot with Win 7 and upgraded from Mageia 6 and it doesn't take several minutes to boot.

Look at
viewtopic.php?f=7&t=12865