Slow bootup

zaivala · 2019-11-10 06:48

Q4OS is the slowest boot on my system. I have run systemd-analyze blame on it... but I don't know what to do to fix any of it. Any suggestions would be helpful.

Attachments:

systemd-analyze.txt, Size: 3.04 KiB, Downloads: 668

Dai_trying · 2019-11-10 10:04

It looks like you are running on traditional HDD rather than SSD so I would say it looks quite normal for the setup you appear to have, I use SSD's now and the boot times are considerably quicker.

How long does it actually take to get to your desktop from power-on?

Also have you compared the output from the other OS's to see what they report?

deanr · 2019-11-10 10:20

Dai_trying wrote:

It looks like you are running on traditional HDD rather than SSD so I would say it looks quite normal for the setup you appear to have, I use SSD's now and the boot times are considerably quicker.

Agree. I switched all of my machines now to SSDs. It's probably the simplest and most effective way of speeding up a PC considerably (x5/6 I believe) - and cheap too nowadays if we're talking about a desktop.

You could even consider using a combination of these:

https://www.amazon.co.uk/Benfei-SATA-Ad … s9dHJ1ZQ==

https://www.amazon.co.uk/Crucial-CT240B … 179&sr=8-4

Or even one of these:

https://www.amazon.co.uk/Docking-Statio … 689&sr=8-3

In either case, these ways mean that you don't even need to open up your computer

Last edited by deanr (2019-11-10 10:23)

zaivala · 2019-11-10 17:48

Dai_trying wrote:

It looks like you are running on traditional HDD rather than SSD so I would say it looks quite normal for the setup you appear to have, I use SSD's now and the boot times are considerably quicker.
How long does it actually take to get to your desktop from power-on?
Also have you compared the output from the other OS's to see what they report?

Iwill get you that data (actual bootup time) on my next boot.

And yes, I have systemd-analyze blame files saved for each of my distros. The Q4OS is by far the longest, in terms of number of entries and in terms of the long times of the top entries. If you look at the text file, you'll see how long that is.

Dai_trying · 2019-11-10 17:56

I did read the text file and 45 seconds on a spinning disc (traditional HDD) does not seem out of the ordinary, and the reason I asked about the time it actually takes is because it might differ from what systemd-analyze reports...

EDIT: And my system typically boot from pressing power button to desktop around 10 seconds

Last edited by Dai_trying (2019-11-10 17:58)

crosscourt · 2019-11-10 18:40

Im running the KDE version but with a conventional 5400rpm drive on my laptop thats has only one OS installed it takes about 25-28 seconds to boot.

zaivala · 2019-11-10 18:54

OK, I get the KDE symbol at 0:55 and full desktop at 1:20. I timed a number of distros on my old T430 with spinning metal only, and all of them came in under 0:51. THe current machine is an Intel i5-7200U with 16 Gb RAM,it has a 256 Mb M.2 SSD and a 1 TB 7200 RPM spinning rust disk. I have confirmed that Q4OS is on sda2, the second partition of the spinning disk.

I tried to take a screenshot, but apparently Q4OS does not come with such a program. I need to look to install one.

My time was clocked on my phone's stopwatch, I booted to the multiboot menu, and hit the Start button at the same time as selecting Q4OS from the menu. So that does not include the time getting to the boot menu, which I thought was fair to exclude.

Last edited by zaivala (2019-11-10 18:58)

Dai_trying · 2019-11-10 19:10

So it looks like there is a time difference between what systemd-analyze reports and what you are timing, this would suggest (to me) other possible errors with your system. If it were me I would check for errors in logs to see if I could find something and probably start with the easiest one :-

sudo dmesg | grep -i "fail\|error"

EDIT:
screenshots are easy with Q4OS, simply press your printscreen key (PrtScr) and then right click the desktop and select Paste Clipboard Contents

Last edited by Dai_trying (2019-11-10 19:13)

crosscourt · 2019-11-10 19:12

Grub screen to KDE login is 20 seconds, then 5-8 seconds till it boots to the GUI. I use a Dell E6420 laptop with i5 2.6ghz cpu, 8gb of ram and a WD 5400rpm 2.5 hard drive. Thats actually pretty standard for me with any Debian based KDE distro in regards to boot times.

zaivala · 2019-11-10 19:34

Dai_trying wrote:

So it looks like there is a time difference between what systemd-analyze reports and what you are timing, this would suggest (to me) other possible errors with your system. If it were me I would check for errors in logs to see if I could find something and probably start with the easiest one :-
sudo dmesg | grep -i "fail\|error"
EDIT:
screenshots are easy with Q4OS, simply press your printscreen key (PrtScr) and then right click the desktop and select Paste Clipboard Contents

zaivala@zaivala-pc-q4os:~$ sudo dmesg | grep -i "fail\|error"
[sudo] password for zaivala:
[ 0.386155] acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM
[ 0.459408] pci 0000:02:02.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[ 0.459412] pci 0000:02:02.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[ 4.261241] mmc0: error -110 whilst initialising SD card
[ 6.411683] mmc0: error -110 whilst initialising SD card
[ 7.743509] systemd[1]: Failed to bump fs.file-max, ignoring: Invalid argument
[ 8.520181] mmc0: error -110 whilst initialising SD card
[ 13.164229] thermal thermal_zone3: failed to read out thermal zone (-61)
zaivala@zaivala-pc-q4os:~$

I note the errors installing SD card. I had forgotten I even had that there, and it's not formatted, so that could be the problem there.

So screenshots are easy... except it takes at least 4 clicks (PrtSc, click to desktop, right-click desktop, select paste), compared to most distros where it's just PrtSc, plus the ability in many to select which part of the window you want to capture. Needs work here, I would suggest.

Last edited by zaivala (2019-11-10 19:37)

Dai_trying · 2019-11-10 19:50

zaivala wrote:

I note the errors installing SD card. I had forgotten I even had that there, and it's not formatted, so that could be the problem there.

Please let us know how much difference it makes.

zaivala wrote:

So screenshots are easy... except it takes at least 4 clicks (PrtSc, click to desktop, right-click desktop, select paste), compared to most distros where it's just PrtSc, plus the ability in many to select which part of the window you want to capture. Needs work here, I would suggest.

I beg to differ here, this is simply an always there option to get a screenshot even before you install a desktop profile and IMO a low footprint extremely reliable feature of Q4OS, if I have to click a couple of times more than some other distros I can live with that, and if I want a feature rich option I install ksnapshot-trinity and have more bells and whistles.

And my VM's boot is even quicker than my laptop

dai@dai-pc:~$ systemd-analyze
Startup finished in 2.808s (kernel) + 1.185s (userspace) = 3.994s
graphical.target reached after 1.176s in userspace
dai@dai-pc:~$ systemd-analyze blame
           395ms dev-vda1.device
           313ms udisks2.service
           299ms NetworkManager-wait-online.service
           186ms systemd-logind.service
           179ms systemd-timesyncd.service
           167ms wpa_supplicant.service
           148ms keyboard-setup.service
           134ms NetworkManager.service
           133ms avahi-daemon.service
           109ms rsyslog.service
           107ms systemd-journald.service
            97ms networking.service
            94ms systemd-tmpfiles-setup.service
            84ms user@1000.service
            82ms systemd-modules-load.service
            81ms systemd-journal-flush.service
            65ms spice-vdagentd.service
            57ms ssh.service
            54ms systemd-udev-trigger.service
            54ms polkit.service
            51ms systemd-random-seed.service
            37ms tdm.service
            36ms systemd-tmpfiles-setup-dev.service
            36ms ifupdown-pre.service
            35ms systemd-udevd.service
            32ms dev-disk-by\x2duuid-dc18ece7\x2d71a0\x2d4ed9\x2d914c\x2d9d6c6a6704ec.swap
            30ms systemd-sysctl.service
            29ms alsa-restore.service
            28ms systemd-update-utmp.service
            25ms kmod-static-nodes.service
            24ms dev-mqueue.mount
            24ms sys-kernel-debug.mount
            19ms user-runtime-dir@1000.service
            18ms console-setup.service
            16ms systemd-sysusers.service
            16ms systemd-remount-fs.service
            13ms systemd-user-sessions.service
            12ms dev-hugepages.mount
            11ms hddtemp.service
             7ms systemd-update-utmp-runlevel.service

q4osteam · 2019-11-10 20:37

@vietvet70
Thanks for reporting. The "kde-spectacle" package to create snapshots will be added into the basic and full desktop Plasma profile in the next Q4OS media revision.

q4osteam · 2019-11-10 20:39

Anyway, you can use just PrintScreen + ctrl-v keyboard shorcuts. That needs no mouse click at all.

zaivala · 2019-11-11 06:33

I really fail to see how it helps me any to talk about your VM or SSD usage. I'm asking about how to fix an issue, not be told I could do something else.

At any rate, with the SD card pulled, it still takes 1:24 (aka 84 seconds). Interesting that this time is actually 4 seconds longer.

Last edited by zaivala (2019-11-11 06:41)

q4osteam · 2019-11-11 09:09

zaivala wrote:

I really fail to see how it helps me any to talk about your VM or SSD usage. I'm asking about how to fix an issue ...

The boot time info from another installations could be helpful really, as it gives us a real comparable data.

If you would provide "journal.log" from the Q4OS and another Debian based system after a fresh boot, we will be able to check and compare them to reveal the cause of slow Q4OS bootup on your hardware.

Command to create compressed "journal.log":
$ sudo journalctl | gzip > /tmp/journal.log.gz

Dai_trying · 2019-11-11 09:52

zaivala wrote:

I really fail to see how it helps me any to talk about your VM or SSD usage. I'm asking about how to fix an issue, not be told I could do something else.

My apologies, I thought I would add this extra data to the thread just for comparison but I guess I should have kept it to myself, it wont happen again...

zaivala · 2019-11-11 16:22

Dai_trying wrote:

zaivala wrote:
I really fail to see how it helps me any to talk about your VM or SSD usage. I'm asking about how to fix an issue, not be told I could do something else.
My apologies, I thought I would add this extra data to the thread just for comparison but I guess I should have kept it to myself, it wont happen again...

Sorry, it just sidetracked from the issue. If I had lots of money I would buy another SSD (I just had to talk my wife into letting me get a $1 Humble Book BUndle). I work on metal, not in VMs, because I do a podcast on distrohopping, and we want to basically report the experience a new user would have. (Also, sadly, I have yet to use a VM, although in my defense I've only had machines with sufficient memory for VMs a couple of months now, donated by one of my listeners.)

zaivala · 2019-11-11 16:25

q4osteam wrote:

The boot time info from another installations could be helpful really, as it gives us a real comparable data.
If you would provide "journal.log" from the Q4OS and another Debian based system after a fresh boot, we will be able to check and compare them to reveal the cause of slow Q4OS bootup on your hardware.
Command to create compressed "journal.log":
$ sudo journalctl | gzip > /tmp/journal.log.gz

I could have installed MX for a closer comparison, but I have files from Linux Mint, Bodhi 5.1, and Pearl Desktop 8 for comparison. I do understand that they are Ubuntu-based, not pure Debian, but there should be enough in common for a fair comparison. I could have added another but thought this should be enough.

I'm a bit confused... I attach more than one file and it only shows the last file... shouldn't it show all attached files?

zaivala · 2019-11-11 16:28

q4osteam wrote:

The boot time info from another installations could be helpful really, as it gives us a real comparable data.
If you would provide "journal.log" from the Q4OS and another Debian based system after a fresh boot, we will be able to check and compare them to reveal the cause of slow Q4OS bootup on your hardware.
Command to create compressed "journal.log":
$ sudo journalctl | gzip > /tmp/journal.log.gz

I could have installed MX for a closer comparison, but I have files from Linux Mint, Bodhi 5.1, and Pearl Desktop 8 for comparison. I do understand that they are Ubuntu-based, not pure Debian, but there should be enough in common for a fair comparison. I could have added another but thought this should be enough.

I got an error message that the file exceeds maximum file length.. these files are very different lengths...

Yes, the system will not accept the shortest of my other three files. The file for Bodhi is 945Kb, for Pearl 8 is 1.5 Mb, and for Mint is 4.2 Mb.

Last edited by zaivala (2019-11-11 16:33)

Attachments:

q4os.journal.log.gz, Size: 28.78 KiB, Downloads: 581

Dai_trying · 2019-11-11 17:52

Do you have the systemd-analyze results for the other distro's on the same hardware?

q4osteam · 2019-11-11 18:10

zaivala wrote:

Yes, the system will not accept the shortest of my other three files. The file for Bodhi is 945Kb, for Pearl 8 is 1.5 Mb, and for Mint is 4.2 Mb.

Files > 300KiB are not allowed to attach in the forum. You are welcome to e-mail your logs to support@q4os.org , we will check them out as well. By far the best for comparison would be journal log from a Debian based OS, so MX would be a good candidate.

The difference in protocol size, 28 KB for Q4OS and more than 1 MB for other systems, looks a bit suspicious.

zaivala · 2019-11-11 23:57

At the present time, I do not have any straight Debian on my machine except for Q4OS. I have Ubuntu Budgie, Pearl Desktop 8, Linux Mint 19.2, and Bodhi 5.1 in addition to Q4OS. As we are trying to compare boot times on my machine, and as in specific we are talking about my spinning metal drive, it would be hard to go install something just to check boot time, and a new installation usually has a shorter boot time anyhow.

q4osteam · 2019-11-12 08:20

zaivala wrote:

Yes, the system will not accept the shortest of my other three files. The file for Bodhi is 945Kb, for Pearl 8 is 1.5 Mb, and for Mint is 4.2 Mb.
... At the present time, I do not have any straight Debian on my machine except for Q4OS. I have Ubuntu Budgie, Pearl Desktop 8, Linux Mint 19.2, and Bodhi 5.1

Well, so please e-mail journal logs you actually collected to support@q4os.org . We will analyze them out, try to compare with the Q4OS one, and post a result here as you provide it.

zaivala · 2019-11-12 18:34

I will need to go collect those again. I did a truly stupid thing I thought I was no longer capable of and wiped my backup drive trying to format an SD card; the gathered files were on that drive. Not my finest moment. GPartEd has been trying to recover the data on that for 20 hours now, and I don't know when I should just give up. I have a not-quite-recent backup on another external drive but it did not contain that data. However, I may have those files on the individual partitions still, or I can run the command again.

zaivala · 2019-11-28 05:12

I went through today and (using a stopwatch, not relying on systemd-analyze) clocked each of my boots on this machine. There are 6 total distros booting on this machine... but I should ignore the two which boot from the M.2 SSD. So that leaves:

Sabayon 19.03 MATE - 0:38
Bodhi 5.1.0 - 0:59
Ubuntu Budgie 19.10 - 0:48
Q4OS 3.8 Centaurus (Buster) - 1:34

These are all booting on a 1 Tb spinning metal disk, running on a Galago Pro 2 with 16 Gb RAM (more specs are available).

It has been noted by a friend whom I've talked into trying Q4OS that the version of KDE Plasma in use is 5.14.5, whereas the latest version is 5.17. How much can this be contributing to the slowdown? And is it possible to update KDE?

Q4OS Forum

#1 2019-11-10 06:48

Slow bootup

#2 2019-11-10 10:04

Re: Slow bootup

#3 2019-11-10 10:20

Re: Slow bootup

#4 2019-11-10 17:48

Re: Slow bootup

#5 2019-11-10 17:56

Re: Slow bootup

#6 2019-11-10 18:40

Re: Slow bootup

#7 2019-11-10 18:54

Re: Slow bootup

#8 2019-11-10 19:10

Re: Slow bootup

#9 2019-11-10 19:12

Re: Slow bootup

#10 2019-11-10 19:34

Re: Slow bootup

#11 2019-11-10 19:50

Re: Slow bootup

#12 2019-11-10 20:37

Re: Slow bootup

#13 2019-11-10 20:39

Re: Slow bootup

#14 2019-11-11 06:33

Re: Slow bootup

#15 2019-11-11 09:09

Re: Slow bootup

#16 2019-11-11 09:52

Re: Slow bootup

#17 2019-11-11 16:22

Re: Slow bootup

#18 2019-11-11 16:25

Re: Slow bootup

#19 2019-11-11 16:28

Re: Slow bootup

#20 2019-11-11 17:52

Re: Slow bootup

#21 2019-11-11 18:10

Re: Slow bootup

#22 2019-11-11 23:57

Re: Slow bootup

#23 2019-11-12 08:20

Re: Slow bootup

#24 2019-11-12 18:34

Re: Slow bootup

#25 2019-11-28 05:12

Re: Slow bootup

Board footer