Debian 10 slow initialization

Gonzalo_VC · 04-17-2023, 08:12 AM

Hello, everybody. I am using Debian GNU/Linux 10 (buster; kernel= Linux 5.4.16-polilinux-amd64) in a (brazilian) Positivo / Vaio notebook. The boot process is extremely long. The hard drive led keeps blinking (or stays on) for long minutes even after the DE (Gnome 3.30.2) is displayed. Since I have used other distros in other PCs in the last 15 years, I know what is fast and what is slow and this laptop is a shame.
The HD info is: WDC WD10SPZX-00Z10T0 ...
I guess is something like the system indexing files in the HD, or something like that, that keeps the machine busy and almost unresponsive in every start up process.
Of course the same machine (that has an i7 processor!) should be much faster with an SSD, but still: any suggestions on how to solve/improve this situation?

Thanks!

szboardstretcher · 04-17-2023, 09:10 AM

Run systemd-analyze to look at your boot process and related start times,. from there you might be able to intuit what is slowing things down:

Code:

systemd-analyze blame

Gonzalo_VC · 04-18-2023, 08:19 AM

Interesting. I'll take a look. Thank you.

PS: I did it and got a few information, only... Please, see below.
However, I guess something else is taking place outside these services. Perhaps the searching/indexing files in the HD is the problem and not listed, here (looks like something windows OS does and GNU/Linux could be more efficient when doing...). I really don't know. I just have this hypothesis.

usuario@vaio:~$ systemd-analyze blame
23.435s plymouth-quit-wait.service
15.380s fwupd.service
11.816s snapd.service
9.717s NetworkManager-wait-online.service
9.325s vboxdrv.service
8.380s ModemManager.service
7.557s udisks2.service
6.367s dev-sda2.device
6.008s accounts-daemon.service
5.426s NetworkManager.service
4.638s networking.service
4.579s avahi-daemon.service
4.575s ofono.service
4.575s rsyslog.service
4.528s lm-sensors.service
4.527s led.service
4.525s bluetooth.service
4.501s pppd-dns.service
4.497s systemd-logind.service
4.492s wpa_supplicant.service
4.349s dundee.service
3.512s dev-loop0.device
2.990s dev-loop2.device
2.624s dev-loop7.device
2.418s dev-loop5.device
2.198s colord.service
2.182s dev-loop9.device
2.173s dev-loop10.device
2.077s dev-loop8.device
1.739s dev-loop1.device
1.637s dev-loop3.device
1.582s apparmor.service
1.480s snapd.seeded.service
1.467s systemd-fsck@dev-disk-by\x2duuid-CECF\x2d0F54.service
1.287s dev-loop6.device
1.248s systemd-fsck@dev-disk-by\x2duuid-18c...2a9d1d2.service
1.123s user@1001.service
1.007s snap-core-14946.mount
1.000s dev-loop4.device
974ms systemd-tmpfiles-setup.service
947ms snap-core-14784.mount
912ms polkit.service
879ms systemd-backlight@backlight:intel_backlight.service
811ms systemd-udevd.service
810ms snap-core18-2714.mount
726ms snap-gtk\x2dcommon\x2dthemes-1534.mount
665ms upower.service
661ms systemd-rfkill.service
645ms snap-kompozer-4.mount
642ms snap-gtk\x2dcommon\x2dthemes-1535.mount
615ms warsaw.service
593ms snap-bare-5.mount
564ms snap-core18-2721.mount
557ms keyboard-setup.service
(lines 1 to 54)

jailbait · 04-18-2023, 05:39 PM

Quote:

Originally Posted by Gonzalo_VC

Interesting. I'll take a look. Thank you.

PS: I did it and got a few information, only... Please, see below.
However, I guess something else is taking place outside these services. Perhaps the searching/indexing files in the HD is the problem and not listed, here (looks like something windows OS does and GNU/Linux could be more efficient when doing...). I really don't know. I just have this hypothesis.

usuario@vaio:~$ systemd-analyze blame
23.435s plymouth-quit-wait.service
15.380s fwupd.service
11.816s snapd.service

9.717s NetworkManager-wait-online.service

9.325s vboxdrv.service
8.380s ModemManager.service
7.557s udisks2.service
6.367s dev-sda2.device
6.008s accounts-daemon.service

5.426s NetworkManager.service
4.638s networking.service

4.579s avahi-daemon.service
4.575s ofono.service
4.575s rsyslog.service
4.528s lm-sensors.service
4.527s led.service
4.525s bluetooth.service
4.501s pppd-dns.service

4.497s systemd-logind.service
4.492s wpa_supplicant.service

4.349s dundee.service
3.512s dev-loop0.device
2.990s dev-loop2.device
2.624s dev-loop7.device
2.418s dev-loop5.device
2.198s colord.service
2.182s dev-loop9.device
2.173s dev-loop10.device
2.077s dev-loop8.device
1.739s dev-loop1.device
1.637s dev-loop3.device
1.582s apparmor.service
1.480s snapd.seeded.service
1.467s systemd-fsck@dev-disk-by\x2duuid-CECF\x2d0F54.service
1.287s dev-loop6.device
1.248s systemd-fsck@dev-disk-by\x2duuid-18c...2a9d1d2.service
1.123s user@1001.service
1.007s snap-core-14946.mount
1.000s dev-loop4.device
974ms systemd-tmpfiles-setup.service
947ms snap-core-14784.mount
912ms polkit.service
879ms systemd-backlight@backlight:intel_backlight.service
811ms systemd-udevd.service
810ms snap-core18-2714.mount
726ms snap-gtk\x2dcommon\x2dthemes-1534.mount
665ms upower.service
661ms systemd-rfkill.service
645ms snap-kompozer-4.mount
642ms snap-gtk\x2dcommon\x2dthemes-1535.mount
615ms warsaw.service
593ms snap-bare-5.mount
564ms snap-core18-2721.mount
557ms keyboard-setup.service
(lines 1 to 54)

My guess is that systemd is waiting for a response from a client system on the network before completing boot. Do you have some sort of permanent link to something else on the network?

pan64 · 04-19-2023, 01:40 AM

do you really need pppd-dns (for example)?

Gonzalo_VC · 04-19-2023, 01:57 PM

Quote:

Originally Posted by jailbait

My guess is that systemd is waiting for a response from a client system on the network before completing boot. Do you have some sort of permanent link to something else on the network?

No, I don't. That's one of the problems with this awful init system!!!

Besides bad, it has divided the FLOSS community and Debian's

jailbait · 04-20-2023, 10:49 AM

During boot systemd is waiting for the network to be established before completing the boot process (along with a lot of other services). You can issue a command that will tell systemd to not wait on establishing the network. If network initialization takes a long time then it will simply complete sometime after boot finishes.

I suggest that you try the following command:

systemctl disable NetworkManager-wait-online.service

If that doesn't solve the problem then enable the boot network wait again with:

systemctl enable NetworkManager-wait-online.service

Gonzalo_VC · 04-21-2023, 09:02 AM

Quote:

Originally Posted by jailbait

During boot systemd is waiting...

I suggest that you try the following command:

systemctl disable NetworkManager-wait-online.service

If that doesn't solve the problem then enable the boot network wait again with:

systemctl enable NetworkManager-wait-online.service

Thanks. Will try.
But what about the HD led blinking or stayin on long after the GUI is displayed? Should that be something related to systemD, too? Or is there where it waits for the network? (Sorry for my ignorance).

Gonzalo_VC · 04-26-2023, 07:59 AM

Good morning. Please, check out this htop information about the processes running already (minutes after booting, no apps open, just the Gnome GUI):

pan64 · 04-27-2023, 01:21 AM

I don't know what is that /usr/local/bin/warsaw/core, otherwise it looks normal.
Is there any progress (with that boot optimization)?

Gonzalo_VC · 04-27-2023, 03:16 PM

PS: more processes for you to see. Many gnome(shell) and system stuff like pulse-audio ("from the same producers of systemD"

).
Is it my laptop or Debian used to be much better?

pan64 · 04-28-2023, 12:33 AM

that is ok from my side. What are you looking for?

Gonzalo_VC · 04-29-2023, 07:18 AM

Quote:

Originally Posted by pan64

that is ok from my side. What are you looking for?

I'm looking for something that is demanding CPU and HD and keeps the laptop "working" after the DE is displayed, when other distros in other machines go quiet and are ready for working

Thank you all for the ideas.