[Uefi-X86_Ubuntu 22.04.3 ] Impossible to update Grub, stalled into minimal grub stage
Description
Environment
None
Attachments
3
Checklist
hideActivity
Show:
SoSie October 11, 2023 at 8:34 AM
It seems grub efi can not handle nvme, I converged to grub-pc with target i386-pc and then grub-install did the correct job at least!
This is the screenshot of my attempt to have side by side
armbian aarch64 and armbian x86 on the same disk
I have installed succesfully armbian bananapi on /dev/sda1 (armbi_root)
I created a 256Mo fat32 on /dev/sda2 and a third ext4 with uefi-x86, i synchronized
with the iso like this:
#loop0 7:0 0 9,9G 0 loop
#├─loop0p1 259:0 0 4M 0 part
#├─loop0p2 259:1 0 256M 0 part
#└─loop0p3 259:2 0 9,6G 0 part
all was done on a 2’5 sata hardrive
. I boot on it using ventoy combined with super-grub2 disk, avoiding this sort of nightmare like in the script that is not sufficient sometimes !
Everthing is fine to boot and I set a paswword as usual the frst installation,
. I struggle with the keyboard because it is not english so I have to
as Nautilus does not provide the ability to open a term here, I swaped it to nemo
and bored, change the desktop to cinnamon
Now as I am not satisfied, I want this on a ssd, I tried with a sata ssd, after
fighting a bit, grubs starts annoying to restore the boot but I succeed to make it boot per default only un grub mode./ MBR only
Now I want this on nvme. I do quite the same steps. This time I am so tired not managing to rectify the boot I use ‘boot-recovery’ shiipped with the swiss-knife toolset medicat, the king of Boot-Repair-Disk 64bit - sized of 22gb reducing script to..(after switching back base-files package to old one <12 to be able to install grub-efi-amd64-signed)
Notice that there is not more annoyances stuff like:
”nvram locked” solved with --no-nvram .
“warning: EFI variables cannot be set on this system.”
solved with mount -t efivarfs none /sys/firmware/efi/efivars
The THING is on my side it said you have not secureboot enabled
bur as the same time the system acts if it prevents to update grub !
This stuff allows me to go further but at the end on start I fall in Minimal Grub 2.06 mode having to type (or using ventoy+super grub2 disk)
The grub install produced no errors, using a secure boot signed with shim-signed on
a non secureboot system.. Is grub 2.06 buggy with nvme or do I missed something TO AVOID TO BE STUCK IN THE MINIMAL BASH GRUB making uefi X86 inaccessible for common users.. ?