Failed to boot after reboot

FTouzain

I ran:

sudo bootctl --no-pager

It told me Couldn't find EFI system partition .... So clearly solus was installed in legacy mode.

What will happen it I type:

update-grub2

sudo grub-mkconfig -o /boot/grub/grub.cfg

?
How does grub2 detect boot device please?
My boot partition is tagged as bootable in gparted and I have no broken packages, neither broken disk. So, clearly, my problem seems to come from grub2, isn't it?

brent

FTouzain So clearly solus was installed in legacy mode.

Read this 4 times and head is spinning. you have 6 drives? Distros (two? three?) are on one nvme? Then the other 5 are for storage or something? Your boot order is probably nightmarish unless you have a single boot?

Then you claim Solus boot rescue doesn't apply to grub. I've used it half a dozen times for efi..maybe you are right...

but Solus tells me exactly what I thought:
"I can't boot into Solus after installation!
There are some misunderstandings with how legacy and EFI boot work (usually implemented as UEFI). These sections cover the common misconceptions.
Legacy/BIOS installation
Legacy installations on Solus use the GRUB boot loader on an MBR disk. Only one boot loader can be used on an MBR disk, so if you haven't installed the Solus boot loader on the MBR, you will need to boot into the other OS and update GRUB prior to being able to boot Solus. This will also be required on each update of the kernel to ensure you're booting the latest release." (https://help.getsol.us/docs/user/troubleshooting/installation#legacybios-installation)

Should you run sudo grub-mkconfig -o /boot/grub/grub.cfgin the other distro? Looks like it. I've done the treacherous efi/grub mixup before. It hasn't always worked but if one distro in a grub-dealio disappears you update grub in the other distro...this worked for me a couple times...but I will swear to you...I will never install grub and systemd distros together, ever. But we don't know that either about your situation. You got nothing to lose in my POV.

You never said what your distro next to Solus was. There seems like a ton of info missing in this thread.

pomon

FTouzain It told me Couldn't find EFI system partition ....

Do you have the /boot partition mounted when executing the command sudo bootctl --no-pager?

Axios

As I say with multi booting start with one if step 2 dont work return to step 1
Instead of try to throw something into they setup if your having problems
thats why I avoided multi boot years ago.
But I do understand why people need them at times.

FTouzain

Thank you,

I have only one distro: Solus (installed on a previous linux, maybe this is why legacy was chosen: I did choose it specifically).

The four other drives are for data.

AlphaElwedritsch

FTouzain (installed on a previous linux, maybe this is why legacy was chosen

As a rule, this is not decisive. The BIOS settings are used.

brent

FTouzain I have only one distro: Solus (installed on a previous linux, maybe this is why legacy was chosen: I did choose it specifically).

Then you probably:
1) need to Chroot , mount /boot. and run that grub command
2) or get a terminal on boot (ctrl + alt -f2 or f3) and run that command.

Hell, maybe both commands.
You installed a grub Solus all alone and it worked forever and now it doesn't that would be unusual.
If you just installed Solus and worked uefi into it, then this makes sense. Couldn't tell which scenario.

FTouzain

pomon
I think I have the boot partition mounted because I already have a /boot/grub directory. Even if I didn’t mount it myself, I suppose it is done by one of the command of the recovery process I followed. Thank you. So, I will try the grub-mkconfig command.

FTouzain

Here is what sudo grub-mkconfig -o /boot/grub/grub.cfg gives me:

I backed up my original /boot/grub/grub.cfg as /boot/grub/grub.cfg.back

Generating grub configuration file ...
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
grub-probe: error: cannot find a GRUB drive for /dev/sde1.  Check your device.map.
done

So, I deduce the /boot directory is the one of my live USB ? (/dev/sde1).

What is exactly the command to mount the /boot partition of my nvme please? (and in which directory) (if it is possible).

There is strictly no difference between the new and the old /boot/grub/grub.cfg file.

FTouzain

For information, as I wanted to be sure I had all my drives, I did sudo mount -a yesterday (I had forgetten it).
So, my nvme1n1p2 is currently mounted at / and was already mounted when I typed sudo grub-mkconfig -o /boot/grub/grub.cfg).
So, what does the /boot directory correspond to ? (really the boot directory mounted? but why /dev/sde1, my usb key ? I don't see /dev/sde1 if I do a df command, because of the chroot ?)

I don't know well linux system mechanisms and architecture as you will guess

In addition of the drives I usually have, I have those ones:

devtmpfs                4096          0       4096   0% /dev
none                32885532          0   32885532   0% /dev/shm
efivarfs                 128         40         84  32% /sys/firmware/efi/efivars

pomon

Show:

lsblk -o NAME,FSTYPE,MOUNTPOINT
[ -d /sys/firmware/efi ] && echo "UEFI" || echo "BIOS"
efibootmgr
grub-install --version

FTouzain

lsblk -o NAME,FSTYPE,MOUNTPOINT
gives:

NAME        FSTYPE MOUNTPOINT
loop0              
loop1              
sda                
└─sda1             /media/dd_photos1
sdb                
└─sdb1             /media/dd_photos2
sdc                
└─sdc1             /media/ssd_travail
sdd                
└─sdd1             /media/dd_travail
sde                
├─sde1             
└─sde2             
zram0              [SWAP]
nvme1n1            
├─nvme1n1p1        
└─nvme1n1p2        /
nvme0n1            
└─nvme0n1p1        /media/data

[ -d /sys/firmware/efi ] && echo "UEFI" || echo "BIOS"
gives:

UEFI

efibootmgr
gives:

bash: efibootmgr : commande introuvable

translation: command not found

grub-install --version
gives:

grub-install (GRUB) 2.12

pomon

A bit strange that it doesn’t show FSTYPE. Try:

sudo fdisk -l | grep -i efi
or
sudo blkid | awk '{print $1, $3, $4}'

I want to locate which partition is /boot so it can be mounted and its contents checked.

Install sudo eopkg it efibootmgr

FTouzain

sudo fdisk -l | grep -i efi
gives

/dev/sde2               136  409735   409600   200M ef EFI (FAT-12/16/32)

sudo blkid | awk '{print $1, $3, $4}'
gives

/dev/nvme0n1p1: UUID="9638b75b-4bb0-43fb-ac7e-61a105d68a4f" BLOCK_SIZE="4096"
/dev/nvme1n1p1: TYPE="swap" PARTUUID="875fad34-01"
/dev/sda1: BLOCK_SIZE="4096" TYPE="ext4"
/dev/loop1: BLOCK_SIZE="4096" TYPE="ext4"
/dev/sdd1: UUID="a361777e-56f5-400e-bb3d-12184e91d498" BLOCK_SIZE="4096"
/dev/sdb1: BLOCK_SIZE="4096" TYPE="ext4"
/dev/loop0: TYPE="squashfs" 
/dev/sde2: LABEL_FATBOOT="SOLUSESP" LABEL="SOLUSESP"
/dev/sde1: UUID="2025-01-25-00-21-18-00" LABEL="SolusLiveBudgie"
/dev/sdc1: UUID="63caab14-bfbc-4140-9d7d-6353e4ab87bc" BLOCK_SIZE="4096"
/dev/nvme1n1p2: BLOCK_SIZE="4096" TYPE="ext4"
/dev/zram0: UUID="918780e5-97a4-416d-94d4-5ff158c1ba83" TYPE="swap"

/dev/nvme0n1p1 is supposed to be ext4, I don't know why it is not displayed.

/dev/nvme1n1p2 is supposed to be my Solus partition.

FTouzain

sudo eopkg it efibootmgr:

Taille totale du/des paquets(s) : 24.00 KB
Téléchargement 1 / 1
Paquet efibootmgr trouvé dans le dépôt Solus
efibootmgr-18-3-1-x86_64.eopkg (24.0 KB)100%      0.00 --/- [--:--:--] [fini]
Installation 1 / 1
efibootmgr-18-3-1-x86_64.eopkg [en cache]
Installation de efibootmgr, version 18, millésime 3
Extraction des fichiers de efibootmgr
efibootmgr installé
 [✓] Syncing filesystems                                                success
 [ ] Updating clr-boot-manager                                          skipped
 [ ] Updating clr-boot-manager                                          skipped
 [ ] Reloading systemd configuration                                    skipped
 [✓] Updating manpages database                                         success
 [ ] Reloading udev rules                                               skipped
 [ ] Reloading udev rules                                               skipped

pomon

FTouzain
Check if anything is mounted under /boot with findmnt /boot. If not, run sudo mount /dev/sde2 /boot and check the contents with ls /boot.
Since you have already installed it, show the output of efibootmgr.

It’s a bit strange that /dev/nvme1n1p2 is marked as boot. This means it might contain boot files. Show ls /target.

stocc

I think your system may be using MBR, but I don't know which disk has the MBR installed on it. fdisk -l should show the boot flag I believe, but how you actually resolve the issue, I can't help I'm afraid.

FTouzain

stocc

fdisk -l show the booting flag for:

/dev/sde1
/dev/nvme1n1p2

Thank you for your troubleshooting attempt.

FTouzain

Nothing mounted in /boot (no output).

findmnt /boot
sudo mount /dev/sde2 /boot
ls /boot

Last command gives:

EFI  initrd  kernel  loader  solus-enroll-me.cer

efibootmgr gives:

No BootOrder is set; firmware will attempt recovery

There is no /target directory because I am in chroot.
When doing in a terminal not in chroot ls /target, I get:

bin   dev   lib    lost+found  node_modules_20  root  snap  tmp  vmlinuz
boot  etc   lib32  media       opt              run   srv   usr
data  home  lib64  mnt         proc             sbin  sys   var

All the commands you asked me before was supposed to be in the chroot terminal? Isn't it?

Thank you.

stocc

FTouzain /dev/sde is your live USB, correct?
It seems to me that perhaps /dev/nvme1n1 should contain the MBR and point to nvme1n1p2 as the bootable partition but perhaps it has become corrupted? There are commands to re-create the MBR, but that destroys any existing partitions and I wouldn't want to be responsible for destroying any data you already have installed on that disk. As I mentioned earlier, it may be best to run rescatux to see what that shows.
Worst case, you may have to re-install...

« Previous Page Next Page »