eleusis
Posts: 18
Joined: Sun Jan 21, 2018 3:01 pm

Boot into GRUB rescue after fresh install

Mon Feb 19, 2018 8:40 am

I installed an encrypted Solus to my nvme drive, but I get a GRUB rescue screen at boot.

Using the Boot Rescue guide I get the following result:

Code: Select all

live@solus ~ $ sudo su
root@solus /home/live # mkdir /target
root@solus /home/live # lsblk
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
loop1         7:1    0     5G  1 loop 
├─live-base 253:1    0     5G  1 dm   
└─live-rw   253:0    0     5G  0 dm   /
loop2         7:2    0    32G  0 loop 
└─live-rw   253:0    0     5G  0 dm   /
loop0         7:0    0   1.1G  1 loop 
sda           8:0    1    59G  0 disk 
├─sda2        8:2    1    30M  0 part 
└─sda1        8:1    1   1.2G  0 part /run/initramfs/live
nvme0n1     259:0    0 238.5G  0 disk 
├─nvme0n1p1 259:1    0 286.1M  0 part 
└─nvme0n1p2 259:2    0 238.2G  0 part 
root@solus /home/live # cryptsetup luksOpen /dev/nvme0n1p2 solus
Enter passphrase for /dev/nvme0n1p2: 
root@solus /home/live # lvmdiskscan
  /dev/ram0             [      64.00 MiB] 
  /dev/nvme0n1          [     238.47 GiB] 
  /dev/loop0            [       1.09 GiB] 
  /dev/mapper/live-rw   [       5.00 GiB] 
  /dev/ram1             [      64.00 MiB] 
  /dev/nvme0n1p1        [     286.10 MiB] 
  /dev/loop1            [       5.00 GiB] 
  /dev/sda1             [       1.15 GiB] 
  /dev/mapper/live-base [       5.00 GiB] 
  /dev/ram2             [      64.00 MiB] 
  /dev/nvme0n1p2        [     238.19 GiB] 
  /dev/loop2            [      32.00 GiB] 
  /dev/sda2             [      30.00 MiB] 
  /dev/mapper/solus     [     238.19 GiB] LVM physical volume
  /dev/ram3             [      64.00 MiB] 
  /dev/SolusSystem/Swap [       3.73 GiB] 
  /dev/ram4             [      64.00 MiB] 
  /dev/SolusSystem/Root [     234.46 GiB] 
  /dev/ram5             [      64.00 MiB] 
  /dev/ram6             [      64.00 MiB] 
  /dev/ram7             [      64.00 MiB] 
  /dev/ram8             [      64.00 MiB] 
  /dev/ram9             [      64.00 MiB] 
  /dev/ram10            [      64.00 MiB] 
  /dev/ram11            [      64.00 MiB] 
  /dev/ram12            [      64.00 MiB] 
  /dev/ram13            [      64.00 MiB] 
  /dev/ram14            [      64.00 MiB] 
  /dev/ram15            [      64.00 MiB] 
  4 disks
  24 partitions
  1 LVM physical volume whole disk
  0 LVM physical volumes
root@solus /home/live # mount /dev/SolusSystem/Root /target
root@solus /home/live # mount --bind /proc /target/proc
root@solus /home/live # mount --bind /dev /target/dev
root@solus /home/live # mount --bind /sys /target/sys
root@solus /home/live # chroot /target
root@solus / # sudo clr-boot-manager update
Generating grub configuration file ...
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
done
What do I need to do next?
Last edited by eleusis on Mon Feb 19, 2018 10:35 am, edited 1 time in total.

eleusis
Posts: 18
Joined: Sun Jan 21, 2018 3:01 pm

Re: Boot into GRUB rescue after fresh install

Mon Feb 19, 2018 10:33 am

So I saw elsewhere in the forum to mount a disk at boot, which I assume for me is "/dev/nvme0n1p1", as it has some grub files in it. I also saw usage of "mount --bind /run /target/run" which is not in the boot rescue guide.

Now the last part of what I do is:

Code: Select all

root@solus /home/live # mount /dev/SolusSystem/Root /target
root@solus /home/live # mount /dev/nvme0n1p1 /target/boot
root@solus /home/live # mount --bind /proc /target/proc
root@solus /home/live # mount --bind /dev /target/dev
root@solus /home/live # mount --bind /sys /target/sys
root@solus /home/live # mount --bind /run /target/run
root@solus /home/live # chroot /target
root@solus / # sudo clr-boot-manager update
Generating grub configuration file ...
done
It seems like it worked, but after a reboot I still get to the GRUB rescue screen...

sunnyflunk
Development Team
Posts: 2977
Joined: Sun Mar 13, 2016 11:35 pm

Re: Boot into GRUB rescue after fresh install

Wed Feb 21, 2018 11:01 am

It appears as if it hasn't been installed with EFI (which will happen if the live USB isn't booted in EFI mode). On the live ISO, make sure the directory /sys/firmware/efi/ exists (if it does, it booted with EFI). Grub in Solus doesn't support NVMe drives, as it's for legacy installations.

Common reason for it not booting in EFI mode is writing the USB via an unsupported method, see https://solus-project.com/articles/inst ... nstall/en/ for the supported methods and settings to use.

eleusis
Posts: 18
Joined: Sun Jan 21, 2018 3:01 pm

Re: Boot into GRUB rescue after fresh install

Wed Feb 21, 2018 7:18 pm

It's a BIOS-only motherboard: Asus P6T-Deluxe from 2009. I use a controller for the nvme drive. Other distro's run, but I haven't managed to boot Solus on it.

I've been using Solus on my EFI laptop and prefer it over anything else I've tried.

Is the reason it cannot boot because it expects EFI evenhough I haven't run it in EFI-mode during install?

eleusis
Posts: 18
Joined: Sun Jan 21, 2018 3:01 pm

Re: Boot into GRUB rescue after fresh install

Thu Feb 22, 2018 9:37 am

Was tired last night and didn't read "Grub in Solus doesn't support NVMe drives, as it's for legacy installations."

fswalker
Posts: 1
Joined: Thu Mar 29, 2018 11:21 pm

Re: Boot into GRUB rescue after fresh install

Fri Mar 30, 2018 5:52 pm

Does it mean that Grub won't work in Solus in MBR at all for NVMe drives?
I found that Ubuntu installed Grub and it works, but I would prefer the "booting mechanism" to be owned by Solus, not Ubuntu :/
Any ideas?

Return to “Installation”