You are not logged in.
.
Last edited by Arciere (2025-04-30 08:30:29)
Offline
Do you not even get to GRUB? if you double check from the ISO with efibootmgr, does the generated entry for GRUB exist/stick? Which mainboard is this? If anything MSI, see the green tip box in https://wiki.archlinux.org/index.php/GR … allation_2
Offline
.
Last edited by Arciere (2025-04-30 08:30:11)
Offline
Check this post of mine: https://bbs.archlinux.org/viewtopic.php?id=259748
Maybe you should install the system into /dev/nvme0 instead of /dev/nvme0n1 ?
Also new here myself, don't have much experience, but your fdisk output is so close to the one from my Mac's diskutil the time I got the installation wrong...
Offline
@Arciere depends, if you look into /boot without having mounted the ESP I'd expect it to be empty if you mounted the ESP to /boot like you did during installation there should be files/kernels and grub config/files there. As for efibootmgr check/post the output of
efibootmgr -v@Richardn No /dev/nvme0n1 is the correct level at which to allocate partitions that shouldn't be the issue here.
Offline
.
Last edited by Arciere (2025-04-30 08:30:03)
Offline
All would be best, use a pastebin for posting terminal outputs.
Offline
All would be best, use a pastebin for posting terminal outputs.
And please post the output of
efibootmgr -v -uSo it's easier to read.
Last edited by schard (2020-10-13 10:10:22)
Inofficial first vice president of the Rust Evangelism Strike Force
Offline
.
Last edited by Arciere (2025-04-30 08:29:54)
Offline
So, Grub is registered by the EFI as an available loader.
Please post the output of
$ lsblk -o +fstype,parttypename,uuid,ptuuid
$ mount
$ cat /etc/fstabLast edited by schard (2020-10-13 10:31:02)
Inofficial first vice president of the Rust Evangelism Strike Force
Offline
.
Last edited by Arciere (2025-04-30 08:29:46)
Offline
Sorry, a quick info. I gave this command found on the Wiki to load the previous output:
efibootmgr -v -u |& curl -F 'f:1=<-' ix.ioBut if I gives it back, I upload the new output to the exact same link (I think). What should I change in this command to change the link and thus be able to keep both outputs online?
This might be due to the ix.io server comparing the input by hashes. This way the server can prevent storing duplicate (identical) data.
So most likely the output of efibootmgr has not changed and thusly the server does not generate a new entry.
Last edited by schard (2020-10-13 10:41:37)
Inofficial first vice president of the Rust Evangelism Strike Force
Offline
.
Last edited by Arciere (2025-04-30 08:29:39)
Offline
Hm. That looks mostly good.
With the exception that the GRUB entry's UUID does not exist on your system.
I'd try to just re-install grub again.
# efibootmgr -b 0000 -B
# grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id=GRUB
# grub-mkconfig -o /boot/grub/grub.cfgInofficial first vice president of the Rust Evangelism Strike Force
Offline
.
Last edited by Arciere (2025-04-30 08:29:30)
Offline
You can try a different boot manager, like systemd-boot.
Inofficial first vice president of the Rust Evangelism Strike Force
Offline
.
Last edited by Arciere (2025-04-30 08:29:21)
Offline
That's not going to help, it's not going to retain systemd-boot entries either. If your UEFI is indeed not retaining the entries, follow the tip box I've mentioned regardless to install it into the fallback location, that one should boot when you select to boot off of the drive.
In any case, what you also can do is go through the UEFI firmware and check whether you find an option to manually add entries to the boot menu.
Offline
.
Last edited by Arciere (2025-04-30 08:29:13)
Offline
.
Last edited by Arciere (2025-04-30 08:29:06)
Offline
That's not going to help, it's not going to retain systemd-boot entries either.
Possibly. My goal was to rule out a problem with Grub, though.
Also, it's not clear to me that the EFI does actually not retain the loader entries.
In the output from the chrooted system, it's clearly there.
@Arciere:
Is the grub entry gone from
efibootmgr -v -uafter you rebootet the live system?
Last edited by schard (2020-10-13 16:07:21)
Inofficial first vice president of the Rust Evangelism Strike Force
Offline
@Arciere that's what I meant yes.
@schard I see the sentiment, however even if GRUB was bugged to hell and back one needs an entry in the corresponding UEFI loader. Right now the EFI doesn't show anything at all, that's currently not really related to any software that should or would potentially run, and if the EFI signature of GRUB was broken then no one would be able to use it and we'd see reports here.
Offline
.
Last edited by Arciere (2025-04-30 08:28:33)
Offline
.
Last edited by Arciere (2025-04-30 08:28:26)
Offline
.
Last edited by Arciere (2025-04-30 08:28:19)
Offline