I accepted the new Software upgrades today, which consisted of OS updates. On first reboot, after the second prompt for the disk encryption password, the OS slowed to a crawl. The progress bar took a long time to switch to the “PureOS” logo, then just “hung” there (or at least was very slow).
Del rebooted, which got things going again and continued the install.
LMK if anyone else had this issue today or soon after.
I noticed a double reboot (had to enter LUKS decryption password twice) after today’s upgrade. I did not enter the password quickly on the second prompt and it went to a black screen for me.
Ctrl-Alt-Del has never worked for me in the past although I didn’t try it this time. Anyway, I manually rebooted with the power switch and it seems ok
One thing that one can do after a slow boot is to issue this command at the command line;
That should tell you what was taking a long time during boot.
I have a Librem 15 v4 and was thinking the same as you on the boot up. It definitely hangs during the LUKs decryption sequence. I do not have retype my password, but it almost feels like it will crash at some point.
Has anyone found a remedy to this issue?
Can you describe the issue a bit more? How long does it hang for example? And if you have any corresponding data that might help, like the systemd-analyze blame output or log output that will help in diagnosing issues.
You can always file bugs here: https://tracker.pureos.net/
I didn’t see this delay during this weekend’s OS release.
I reached out to the Support Team. I did indeed run the systemd-analyze blame as well as systemd-analyze.
Here are my results.
Startup finished in 51.658s (kernel) + 8.999s (userspace) = 1min 657ms
graphical.target reached after 8.984s in userspace
One thing I have failed to mention in my post is the Support Team has prescribed some remedies that improved my boot up times by approximately 6 seconds.
sudo apt update
sudo apt install haveged
Restart once or twice to see if the situation improved. If not, then install the other package:
sudo apt install rng-tools
and again install.
The support team was ultra-helpful.
My boot time is similar;
I’ve filed a bug (and assigned it to myself) to try and understand how we can optimize boot a bit better. I think we can get faster start times and I’m hopeful we can avoid hanging on boot.
This happened again with the recent OS upgrade. I let the machine sit, thinking that it would eventually finish, but it sat overnight and never completed the reboot. Sat there with “PureOS” on the screen and the cryptsetup line in the corner. Ctrl-Alt-Del worked, but the
systemd-analyze output is that of the later boot.
Not sure if I should open a new topic, but my Librem 15v3 takes quite a lot time to boot, so I looked up how to analyze and after some research I ended up here:
My top services during boot are
2min 56ms systemd-udev-settle.service
systemd-udev-settle.service takes so much time. Any hints how to analyze further.
People also masked services and so on, but I’m a bit afraid that this may break something.
Thanks in advanced for some help. Up to now I just sit and wait but 3 min is quite a long time for a system with an NVMe SSD isn’t it?
Yes, I would just reinstall a new PureOS image at this point; your boot up time should be within single digit seconds.
Thanks for the quick reply, but can you elaborate a it more what is the root cause and why a re-install should solve it?
Actually I “just” reinstalled my system end of 2021. So 2 years later I should do it another time ^^.
I thought this is a Windows thing. I chose PureOS because I thought I would have a reasonably relaxed life with it, because of its rolling release characters.
I would not know. My approach to dealing with issues I do not have the time nor interest to understand is to bring the system back to a known good state. It simplifies my situation to binary:
Btw. I didn’t reinstall, in my case it was related to the USB (USB-C) docking stating or a device which is attached to it.
Without having it plugged in the system starts very quickly. So I skipped the re-install.
Okay, mark your post as a solution.
I think I cannot do this (no button visible), as the initial message/question was not written by me.