Update caused collapse

Elli88

Hi!
Today's, June 25, mandatory security update caused collapse of my otherwise very stable system (Solus Budgie) on HP Pavillion (core i5, 8 gb ram, 240 SSD). After update the screen went grey, nothing brought the pc back except turned off. On restart, my dual boot system failed to load Solus, from UEFI boot menu.
I tried trouble shooting and boot repair instruction on Solus website, nothing worked.
I don't know if others has similar issues.
regards

CorvusRuber

Elli88 mandatory security update

Question: did you update fully (each and every update offered by Software Center/ sudo eopkg up in terminal) or did you select only some packgages to update ?

Elli88

CorvusRuber
Yes! I completed every thing ... it said 1st few updates didn't complete .. then it completed properly by itself

DASK

I have seen this bug on 2 laptops now. It did this on my uncles laptop when I did a full update via command line and the screen went blank at some stage during the update. Also did the same today on my laptop, blank screen that would not wake during the update process. I just left both for sometime to make sure all disk activity had stopped as it seemed the update was still proccessing in the background. Then like you I had to do an hard reset and hope for the best.

If you rebooted when the screen went off and it was still updating, it could have a damaged update maybe ?

WetGeek

If you have your power settings such that your screen turns off after so-many minutes of inactivity from the mouse and the keyboard, it could be very normal. With the system busy with the upgrades, might it not be responding immediately to the keyboard or the mouse? I'd suggest you try turning off the screen-blanking in the power settings, and see if you still need to power down the machine to get things moving again.

Elli88

WetGeek
I actually suspected that and it was problematic first, the system lags when waking up.
Then I found the answer posted by a guy call himself "thesolless38"
I'll post that in a separate reply down

Elli88

I used grub rescue 1st but the problem recur ... then I found this excellent solution that targets the real cause, which is not the update rather than an issue of installation of boot entry
Here is the correct solution from "thesolless38"
”In some cases, systemd-boot which Solus uses thinks it creates a boot entry and doesn't.
• Boot up your live CD, connect to the internet, do the following:
• Install efibootmgr:
sudo eopkg it efibootmgr
• Run efibootmgr with no arguments.
You should see an entry for Linux Boot Manager, which for some reason doesn't show up in your actual boot menu but does here (even if multi system, they will all show).
• There's a number listed for that entry. Delete it with: THIS STEP MAY NOT FOUND, in this case skip this step
sudo efibootmgr -b [num] -B
• Now you can recreate it.
If your EFI (FAT 32) partition is /dev/sda2 then do this:
sudo efibootmgr -c -d /dev/sda -p 2 -l "\EFI\systemd\systemd-bootx64.efi" -L "Linux Boot Manager"
................................
Thanks to you all