Arch Linux

ben-arch

Member

Registered: 2005-12-17

Posts: 120

Re: [Solved] Can't boot from nvme (dd from ssd)

Am sharing, it's a given.

As I've said, "- re-formatted the partition (fat32)".  Which means, I've lost also the linux files.
(as Head said, but for different reason).

So -
- booted the arch install media.
- mounted al partitions on their repective /mnt mounting points.
- arch-chroot /mnt
- pacman -S linux.  (-Syu if your system is not up to date)
- exit
- reboot

SO, I want to thank all who helped -
@Scimmia
@d.ALT
@Head_on_a_Stick

pasteyourpayloadhere

Member

Registered: 2024-11-03

Posts: 2

Re: [Solved] Can't boot from nvme (dd from ssd)

Hi ben-arch,

I've encountered the same problem, however, I am not following the solution you've used. Could you please create a post with a more detailed solution?

In the mean time, I'll continue looking around at other threads etc. Mods: Should I create a new thread if none of the others in the end help me fix this same issue? I'll post all the photos and explanations as much as possible.

Thank you.

pasteyourpayloadhere

Member

Registered: 2024-11-03

Posts: 2

Re: [Solved] Can't boot from nvme (dd from ssd)

tldr; run `sync` after the `sudo efibootmgr --create --disk /dev/nvme0n1 --part 1 --label "Archlinux" --loader "\EFI\GRUB\grubx64.efi"` command.

Okay, I've found the solution, using the same Pro Z790-P WiFi motherboard.
I did over promise in my previous message regarding the photos, hope you'll forgive me. If you really want them, I'll provide them. However, my solution is as follows:

Problem: UEFI not loading into GRUB after installing Archlinux (manually in this case).

When running efibootmgr -v the entry wasn't there for the ESP.
After creating it, and after rebooting, it wasn't there either; which meant it wasn't being written on NVRAM.

Solution:
`sync` forces it to be written (I'll read what the command does soon, haven't just yet, I just know that it forces sync therefore forces it to write to NVRAM from what I understand).

Hardware: Pro Z790-P WiFi motherboard with a m.v2 drive on the first controller (0).

I was able to boot into Archlinux using EFI shell, and loading the grubx64.efi file manually that way.

This is provided all outputs are correct for the following (i.e., you've followed the Archlinux Installation Guide etc correctly).

`fdisk -l | grep EFI` should have the last column as EFI System.
`gdisk -l /dev/nvme0n1` should say GPT is present, your boot partition as code EF00 for the last column and Number 1 for the first column.
`ls -l /sys/firmware/efi/efivars | grep Boot` should have all entries as rw for root (current user).
`mount | grep efivars` should list the entry as rw (basically same as above I think).
And before the `sync` command was issued:
`efibootmgr -v` wasn't listing the boot partition.

Regarding `sync`:
Looks like sync works because it forces the memory cache / buffer to be written. From what I gather, it's written on either 5 second or 30 second cycles?
So apparently, according to that, I was rebooting before it was being written too.
Apparently the process is this:

efibootmgr --create [...]
     ↓
writes to /sys/firmware/efi/efivars/
     ↓
UEFI firmware interface
     ↓
Physical NVRAM hardware
(I used AI to generate that process -- might be incorrect?).

Feel free to correct me if any of this sync information is incorrect .

Kind regards.

Last edited by pasteyourpayloadhere (2024-11-03 09:23:23)