In this document, we will walk through restoring the ability to boot Solus.
The inability to boot Solus can be attributed to various issues, such as:
Multi-booting is when you have multiple operating systems on the same device. Also referred to as “dual-booting” when only having two operating systems on the same device.
The inability to access Solus in a multi-boot scenario typically applies to “legacy boot” (non-UEFI), where the other operating system owns GRUB, which is used booting itself and Solus. This can be resolved by accessing the other operating system and running
In the case that updates have not been applied correctly by the system or the updates were interrupted, it may be possible to boot rescue the Solus system. To do so, you will need:
Whether you’re using GRUB or UEFI, you will need to mount your Solus root (
/) partition as the first step of performing a boot rescue. This is typically your primary partition, formatted as the filesystem type
lsblk, determine the
/dev/sdX#partition of the Solus system. We recommend checking the size of the partition listed and if it matches the size of your Solus install, use that. It will likely be something along the lines of
mount /dev/sdX# /target
If your system uses UEFI as opposed to GRUB, you will also need to mount your EFI System Partition, otherwise referred to as ESP. If you followed our UEFI guide during installation of Solus, then in all likelihood your ESP will be about 500mb in size. If you’re unsure of the partition, run the following, replacing X with the same letter during your mounting of your root file system, minus the number:
fdisk -o Device,Size,Type -l /dev/sdX
Your output may look something similiar to:
Device Size Type /dev/sda1 512M EFI System /dev/sda2 111.3G Linux filesystem
Notice we have
/dev/sda1 as the Device with the
EFI System type and roughly 500mb in size. This is the partition we will be mounting.
With our ESP device known, let’s go ahead and mount it, replacing
sdX# in the case below with our partition.
mount /dev/sdX# /target/boot
To access your system and perform boot rescue, you will need to mount specific directories from the host system (in this case, our Live ISO), to our Solus system, and then chroot (change root) to the Solus system.
First run the following commands:
mount --bind /proc /target/proc mount --bind /dev /target/dev mount --bind /sys /target/sys
Assuming all goes well, you should now be able to chroot into your Solus system by doing
Once in the chroot, run the following command, which will generate the necessary GRUB configuration files, EFI loader files, etc.
sudo clr-boot-manager update
After this, you should exit your chroot with
exit then reboot your system. In the event you are still unable to access Solus, please contact us.