update wiped /boot partition and grub commands

rjuarezp

Hi everyone!

The update from last Friday was a disaster on my computer. Since then, when the computer boots, the first option is to boot into the Firmware (BIOS). As I just added 0 seconds as waiting time to boot, it is very difficult to force the computer to change its default booting option to Solus Linux (one of the two kernels installed).

I wanted to change the default booting option, but I cannot find the file /etc/default/grub anymore. It is gone!!!!

I have also tried with "sudo update-grub" but this command is not existing anymore in the computer. The /boot partition is also empty (maybe not mounted???).

The last update included a new kernel and I think that the update was not performed correctly... Does anybody has the same problems? I could not find anything in the forum. This behaviour is very annoying and I was really surprised...

Can anybody help me, please?

Thanks!

Lucien_Lachance

i always set whis the boot order in bios
you can select os/kernel by pressing space a lot during bootup
i dont think solus uses grub
afaik /boot always looks empty on solus ,does here as well, i dont remember why

maybe these will help
https://getsol.us/articles/troubleshooting/boot-management/en/
https://getsol.us/articles/troubleshooting/boot-rescue/en/

particularly this bit might help:
Displaying the Solus boot menu by default on boot
The following command will set the timeout of the boot loader so that it appears by default.
sudo clr-boot-manager set-timeout 5 && sudo clr-boot-manager update

rjuarezp

Lucien_Lachance

Thanks for the help, but it does not work!

I already tried with sudo clr-boot-manager set-timeout 5 && sudo clr-boot-manager update. The code is running apparently without any problems (it replies: "New timeout value is: 5"), but when I restart the computer, the timeout is still 0 seconds and the computer is booting "Reboot into Firmware Interface" (into the UEFI BIOS). So, my computer is ignoring the order!!!! (I checked also the BIOS and my first option is to boot into the CD/DVD and the second is my SSD, so it is right!!).

It is a very annoying behaviour... It started today after making the update to the system. Does anybody have another idea?

rjuarezp

I have now tested also with sudo clr-boot-manager set-kernel com.solus-project.current.5.10.1-162 and the command is working without any problem.

As soon as I reboot again, the option "Reboot into Firmware Interface" is highlighted again!!!!! What is doing clr-boot-manager? Why is it ignoring my orders and keep highlighting the option to reboot into the BIOS?

Thanks!

rjuarezp

I found the solution!!!!!
It was given here: https://discuss.getsol.us/d/5028-reboot-into-firmware-interface-is-default-boot-option
Thanks to @abrakidabra !!!!

rjuarezp

By the way... somebody should update the page https://getsol.us/articles/troubleshooting/boot-management/en/

It seems that the command sudo clr-boot-manager set-timeout 5 && sudo clr-boot-manager update is not working anymore. You have to go to the menu and press the key d at the option you want to set as default. Only this is working now.

I also installed the lts kernel and later uninstalled it (with the Software Center) and the entry of the LTS kernel is still in the boot manager. So, it seems that some post uninstall commands are being ignored now... (maybe clr-boot-manager has a problem???).

Thanks!

Harvey

rjuarezp It seems that the command sudo clr-boot-manager set-timeout 5 && sudo clr-boot-manager update is not working anymore.

Works for me but I am using UEFI not legacy boot, maybe the problem exists there.

rjuarezp I also installed the lts kernel and later uninstalled it (with the Software Center) and the entry of the LTS kernel is still in the boot manager. So, it seems that some post uninstall commands are being ignored now...

Pretty sure this is by design. It will keep an old kernel around for awhile as an alternative boot option should you encounter issues with the latest kernel update not working on your system.

Anyway glad you found a solution to your issue. 🙂