Skip to main content ↑ ↓
Topic: GRUB: ERROR: device UUID= not found. Skipping fsck. & /new_root: can't find UUID (Read 7376 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Re: GRUB: ERROR: device UUID= not found. Skipping fsck. & /new_root: can't find UUID

Reply #15 –
Can you install Artix using the information I gave above? For an SSD, you might need to supply an argument on the kernel command line in GRUB.

/etc/fstab is read by automounting service at boot automatically. However, for that your disk needs to be accessible to initrd at boot time, meaning the nvme driver needs to be initialized with correct parameters (supplied to GRUB manually at first, then through /etc/default/grub when the system is installed).

Re: GRUB: ERROR: device UUID= not found. Skipping fsck. & /new_root: can't find UUID

Reply #16 –
Quote
However, for that your disk needs to be accessible to initrd at boot time, meaning the nvme driver needs to be initialized with correct parameters (supplied to GRUB manually at first, then through /etc/default/grub when the system is installed).

What command do I use to do that?

Re: GRUB: ERROR: device UUID= not found. Skipping fsck. & /new_root: can't find UUID

Reply #18 –
Quote
/etc/fstab is read by automounting service at boot automatically. However, for that your disk needs to be accessible to initrd at boot time, meaning the nvme driver needs to be initialized with correct parameters (supplied to GRUB manually at first, then through /etc/default/grub when the system is installed).

/etc/ is on the root partition.  How is the root partition read before it is mounted?  How does the boot up know what to mount as the root partition if the instructions are on the root partition?

I assume something needs to be put on the boot partition, but there's not much there.  Just some .efi files.

Re: GRUB: ERROR: device UUID= not found. Skipping fsck. & /new_root: can't find UUID

Reply #19 –
Because the root partition is supplied to the kernel by the boot manager through the kernel command line. If you are more interested in the boot process, there is extensive documentation available online.

Just read the two articles I linked above, all that you need to do is described there.