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

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

UPDATE: The solution is in this post, i have removed the bug from the setup you can read in this post.

I have installed Linux Artix on my Lenovo ThinkPad T520. I have used a mix of 3 Tutorials:
https://www.rohlix.eu/post/artix-linux-full-disk-encryption-with-uefi/
And a few informations from there:
https://wiki.artixlinux.org/Main/InstallationWithFullDiskEncryption
https://pastebin.com/z406J0RD

Why i used a few tutorials? Because i don't want to encrypt GRUB2, too, so there is my partition table:
sda1
/boot/efi
vfat
ESP Partition
sda2
/boot
ext2
Here are my kernels
sda3
LUKS Volume
encrypted "volRoot" and "volSwap"
But when i boot, GRUB2 appears and i can choose "Linux Artix". Then, after a few seconds that error appears:
Code: [Select]
ERROR: device 'UUID=11a020f6-...' not found. Skipping fsck.
mount: /new_root:can't find UUID=11a020f6-...
You are now being dropped into an emergency shell.
sh: can't access tty: job control turned off.

Here is my "/etc/mkinitcpio.conf":
Code: [Select]
MODULES=()
BINARIES=()
FILES=()
HOOKS=(base udev block autodetect modconf encrypt keyboard keymap lvm2 resume filesystems fsck)
And my "/etc/default/grub":
Code: [Select]
GRUB_DEFAULT=0
GRUB_TIMEOUT=15
GRUB_DISTRIBUTOR="Linux Artix"
GRUB_CMDLINE_LINUX_DEFAULT="crypt_root=/dev/sda3 real_root=/dev/mapper/encryptedLinux-volRoot resume=/dev/mapper/encryptedLinux-volSwap loglevel=3 splash"
GRUB_CMDLINE_LINUX=""
GRUB_DEVICE=/dev/ram0
GRUB_PRELOAD_MODULES="part_gpt part_msdos luks lvm lvm2 cryptodisk"
GRUB_ENABLE_CRYPTODISK=y
GRUB_TIMEOUT_STYLE=menu
GRUB_TERMINAL_INPUT=console
GRUB_GFXMODE=1920x1080
GRUB_GFXPAYLOAD_LINUX=keep
GRUB_DISABLE_RECOVERY=true

The commands to install both were:
Code: [Select]
pacman -S lvm2 cryptsetup linux mkinitcpio grub
mkinitcpio -p linux
grub-install --modules="linux crypto search_fs_uuid luks lvm" --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id="Linux Artix" --recheck /dev/sda
grub-mkconfig -o /boot/grub/grub.cfg

The mkinitcpio got a weird output:
Code: [Select]
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 5.10.16-artix1-1
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [encrypt]
==> WARNING: Possibly missing firmware for module: n5pf
==> WARNING: Possibly missing firmware for module: cxgb4
==> WARNING: Possibly missing firmware for module: qat_c3xxx
==> WARNING: Possibly missing firmware for module: qat_dh895xcc
==> WARNING: Possibly missing firmware for module: qat_c62x
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [lvm2]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: 5.10.16-artix1-1
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: aic94xx
==> WARNING: Possibly missing firmware for module: isci
==> WARNING: Possibly missing firmware for module: wd719x
==> WARNING: Possibly missing firmware for module: qla1280
==> WARNING: Possibly missing firmware for module: qed
==> WARNING: Possibly missing firmware for module: cxgb3
==> WARNING: Possibly missing firmware for module: cxgb4
==> WARNING: Possibly missing firmware for module: bfa
==> WARNING: Possibly missing firmware for module: qla2xxx
==> WARNING: Possibly missing firmware for module: advansys
==> WARNING: Possibly missing firmware for module: csiostor
==> WARNING: Possibly missing firmware for module: xhci_pci
==> WARNING: Possibly missing firmware for module: ums_eneub6250
  -> Running build hook: [encrypt]
==> WARNING: Possibly missing firmware for module: n5pf
==> WARNING: Possibly missing firmware for module: qat_c3xxx
==> WARNING: Possibly missing firmware for module: qat_dh895xcc
==> WARNING: Possibly missing firmware for module: qat_c62x
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [lvm2]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-fallback.img
==> Image generation successful

And i also install and add a lot of stuff into the rc-loader:
Code: [Select]
rc-update add device-mapper boot
rc-update add lvm boot
rc-update add dmcrypt boot
rc-update add dbus default
rc-update add elogind boot
rc-update add ntpd default
rc-update add acpid default
rc-update add syslog-ng default

An "ls -lha1 /boot/" (the /dev/sda2 partition) shows my kernel:
Code: [Select]
drwxr-xr-x  6 root root 4.0K Feb 15 23:05 .
drwxr-xr-x 17 root root 4.0K Feb 15 22:07 ..
drwxr-xr-x  4 root root  16K Jan  1  1970 efi
drwxr-xr-x  7 root root 4.0K Feb 17 12:24 grub
drwx------  2 root root  16K Feb 15 18:31 lost+found
drwxr-xr-x  2 root root 4.0K Nov 30 01:28 memtest86+
-rw-------  1 root root  37M Feb 16 22:09 initramfs-linux-fallback.img
-rw-------  1 root root  19M Feb 16 22:08 initramfs-linux.img
-rw-r--r--  1 root root 9.0M Feb 15 22:36 vmlinuz-linux

And there is the "/boot/grub/grub.cfg":
Code: [Select]
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub

### BEGIN /etc/grub.d/00_header ###
insmod part_gpt
insmod part_msdos
insmod luks
insmod lvm
insmod lvm2
insmod cryptodisk
if [ -s $prefix/grubenv ]; then
  load_env
fi
if [ "${next_entry}" ] ; then
   set default="${next_entry}"
   set next_entry=
   save_env next_entry
   set boot_once=true
else
   set default="0"
fi

if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
fi

export menuentry_id_option

if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
    saved_entry="${chosen}"
    save_env saved_entry
  fi
}

function load_video {
  if [ x$feature_all_video_module = xy ]; then
    insmod all_video
  else
    insmod efi_gop
    insmod efi_uga
    insmod ieee1275_fb
    insmod vbe
    insmod vga
    insmod video_bochs
    insmod video_cirrus
  fi
}

if [ x$feature_default_font_path = xy ] ; then
   font=unicode
else
insmod part_gpt
insmod cryptodisk
insmod luks
insmod gcry_serpent
insmod gcry_serpent
insmod gcry_whirlpool
insmod lvm
insmod ext2
cryptomount -u 28197c4717804978bbce8c1223978774
set root='lvmid/T3omzk-9K1K-viYI-gqg8-cAjN-9koc-S7eLz3/iD8bRT-ERfH-XeuE-kmXv-5uxq-62tu-6cx0ea'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint='lvmid/T3omzk-9K1K-viYI-gqg8-cAjN-9koc-S7eLz3/iD8bRT-ERfH-XeuE-kmXv-5uxq-62tu-6cx0ea'  11a020f6-9765-478f-818d-904fa82e918f
else
  search --no-floppy --fs-uuid --set=root 11a020f6-9765-478f-818d-904fa82e918f
fi
    font="/usr/share/grub/unicode.pf2"
fi

if loadfont $font ; then
  set gfxmode=1920x1080
  load_video
  insmod gfxterm
fi
terminal_input console
terminal_output gfxterm
if [ x$feature_timeout_style = xy ] ; then
  set timeout_style=menu
  set timeout=15
# Fallback normal timeout code in case the timeout_style feature is
# unavailable.
else
  set timeout=15
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/10_linux ###
menuentry 'Linux Artix Linux' --class linux --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-/dev/ram0' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod ext2
set root='hd0,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-ieee1275='ieee1275//disk@0,gpt2' --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2  560bb75e-3b5e-4bc7-a5e2-61ceee78d570
else
  search --no-floppy --fs-uuid --set=root 560bb75e-3b5e-4bc7-a5e2-61ceee78d570
fi
echo 'Loading Linux linux ...'
linux /vmlinuz-linux root=UUID=11a020f6-9765-478f-818d-904fa82e918f rw  crypt_root=/dev/sda3 real_root=/dev/mapper/encryptedLinux-volRoot resume=/dev/mapper/encryptedLinux-volSwap loglevel=3 quiet splash
echo 'Loading initial ramdisk ...'
initrd /initramfs-linux.img
}
submenu 'Advanced options for Linux Artix Linux' $menuentry_id_option 'gnulinux-advanced-/dev/ram0' {
menuentry 'Linux Artix Linux, with Linux linux' --class linux --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-advanced-/dev/ram0' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod ext2
set root='hd0,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-ieee1275='ieee1275//disk@0,gpt2' --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2  560bb75e-3b5e-4bc7-a5e2-61ceee78d570
else
  search --no-floppy --fs-uuid --set=root 560bb75e-3b5e-4bc7-a5e2-61ceee78d570
fi
echo 'Loading Linux linux ...'
linux /vmlinuz-linux root=UUID=11a020f6-9765-478f-818d-904fa82e918f rw  crypt_root=/dev/sda3 real_root=/dev/mapper/encryptedLinux-volRoot resume=/dev/mapper/encryptedLinux-volSwap loglevel=3 quiet splash
echo 'Loading initial ramdisk ...'
initrd /initramfs-linux.img
}
menuentry 'Linux Artix Linux, with Linux linux (fallback initramfs)' --class linux --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-fallback-/dev/ram0' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod ext2
set root='hd0,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-ieee1275='ieee1275//disk@0,gpt2' --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2  560bb75e-3b5e-4bc7-a5e2-61ceee78d570
else
  search --no-floppy --fs-uuid --set=root 560bb75e-3b5e-4bc7-a5e2-61ceee78d570
fi
echo 'Loading Linux linux ...'
linux /vmlinuz-linux root=UUID=11a020f6-9765-478f-818d-904fa82e918f rw  crypt_root=/dev/sda3 real_root=/dev/mapper/encryptedLinux-volRoot resume=/dev/mapper/encryptedLinux-volSwap loglevel=3 quiet splash
echo 'Loading initial ramdisk ...'
initrd /initramfs-linux-fallback.img
}
}

### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###

### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries.  Simply type the
# menu entries you want to add after this comment.  Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###

### BEGIN /etc/grub.d/41_custom ###
if [ -f  ${config_directory}/custom.cfg ]; then
  source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f  $prefix/custom.cfg ]; then
  source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###



]I am out of ideas . I have searched a lot, the most was errors because of systemd ... haha. Anyone got an idea or maybe can give me a hint?

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

Reply #1
What does your grub.cfg look like, one that actually shows linux to boot, the above grub is only a config but not boot selection and such. If there is no /boot/grub/grub.cfg then you didn't do the  grub-mkconfig step.

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

Reply #2
I have edited my first post, the information about /boot/grub/grub.cfg is now there.
And i have installed grub, it's the fourth code- box in the first post.

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

Reply #3
Okay, there are a few Bugs in my f...king setup. At the first, i am pretty sure you are here because of that:
The solution is here:
https://itectec.com/superuser/unable-to-find-root-device-on-a-fresh-archlinux-install/
You have in the "/etc/mkinitcpio.conf" something like that:
Code: [Select]
HOOKS="base udev autodetect block modconf filesystems keyboard fsck"
And THATS the reason why this can't work. BLOCK has to be before AUTODETECT:
Code: [Select]
HOOKS="base udev block autodetect modconf filesystems keyboard fsck"
The treason why that works is in the link, currently we have midnight here and my brain didn't work correctly.

The next one, it's yust an optical setup:
if you have an error or issues with grub, disable the following option in "/etc/default/grub":
Code: [Select]
GRUB_CMDLINE_LINUX_DEFAULT="quiet"
If you remove the parameter "quiet" GRUB2 will tell you a few more informations.

And still ONE Question: who can UPDATE the wiki:
https://wiki.artixlinux.org/Main/InstallationWithFullDiskEncryption
The UUID bug is still there.

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

Reply #4
The UUID error mean your / parition has not been mount at the time the mkinitcpio hooks run fsck.
It also mean that the kernel has boot ! So the problem is in your kernel parameter or your initramfs. Not in the grub install.
The Mkinitcpio is quite normal, it is normal to see a few "missing firmware" message.

Your mkinitcpio Hooks seems correct too but you might want to put the keyboard and keymap hooks before the encrypt one in order to input your password.
My hooks for my system (which is a bit similar) look like that :
Code: [Select]
HOOKS=(base udev autodetect keyboard keymap consolefont modconf block encrypt lvm2 filesystems fsck)
I followed the arch wiki page about encrypting an entire file system, which is quite good.

I think the error is in GRUB_CMDLINE_LINUX_DEFAULT="..."
It is a bad idea to specify disks and partition by their /dev/sdX terminology on static config !
Try something like :
Code: [Select]
GRUB_CMDLINE_LINUX_DEFAULT="cryptdevice=UUID=11111111-1111-1111-1111:crypt_root root=/dev/mapper/encryptedLinux-volRoot resume=/dev/mapper/encryptedLinux-volSwap loglevel=3 splash"
Where 11111111-1111-1111-1111 is the uuid of the sda3 luks volume.
You can find this information by typing "lsblk --fs"

You might want to post the output of this "lsblk --fs" command. It might be useful

Key fingerprint = 912B 29BE EDBE 8E73 8E3F  8758 869E 9A75 3DCA 4320

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

Reply #5
I've installed an artix partition with plasma on my Lenovo ideapod 3.

I tried following the instructions here:
https://forum.artixlinux.org/index.php/topic,2289.msg15645.html#post_msg15370
Namely, change the order of HOOKS in /etc/mkinitcpio.conf to

HOOKS="base udev block autodetect modconf filesystems keyboard fsck"

then running

mkinitcpio -p linux

but it didn't help.

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

Reply #6
Code: [Select]
$ lsblk -o NAME,FSTYPE,SIZE,UUID,PARTUUID
Then make sure you copied and pasted the correct UUID. UUID and PARTUUID are two different things.

If there is no UUID listed next to your partition, go with PARTUUID (PARTUUID=some-hexa-decimally-coded-partuuid)

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

Reply #7
Yes, the UUID's agree.

I tried changing (/mnt)/etc/fstab to use PARTUUID's anyway.

then typing

Code: [Select]
grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=grub
grub-mkconfig -o /boot/grub/grub.cfg

as well as

Code: [Select]
grub-mkconfig -o /boot/efi/EFI/grub/grub.cfg

since the plasma installed insisted I mount the boot partition at /boot/efi/

However, I still get the same error, which mentions the UUID rather than the PARTUUID, which suggests I need to run some other command to get into the changes I made to /etc/fstab into the bootloader.

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

Reply #8
since the plasma installed insisted I mount the boot partition at /boot/efi/
https://wiki.archlinux.org/title/EFI_system_partition#Typical_mount_points

plasma shouldn't "insist" on EFI partition path, it has nothing to do with it. Most common is to have ESP in /boot. You should post your GRUB configuration file from /etc/default/grub, /etc/mkinitcpio.conf (use paste.artixlinux.org) and /etc/fstab. And maybe the output of the lsblk command I listed in my previous post.

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

Reply #9
plasma shouldn't "insist" on EFI partition path, it has nothing to do with it.

Well the installer that came in artix-plasma-runit-20210426-x86_64.iso wouldn't recognize the partition as a boot partition unless it was mounted at /boot/efi/

In any case here are the files:

/etc/default/grub,

Code: [Select]
GRUB_DEFAULT="0"
GRUB_TIMEOUT="3"
GRUB_DISTRIBUTOR="Artix"
GRUB_CMDLINE_LINUX_DEFAULT="quiet"
GRUB_CMDLINE_LINUX="net.ifnames=0"

# Preload both GPT and MBR modules so that they are not missed
GRUB_PRELOAD_MODULES="part_gpt part_msdos"

# Uncomment to enable Hidden Menu, and optionally hide the timeout count
#GRUB_HIDDEN_TIMEOUT="5"
#GRUB_HIDDEN_TIMEOUT_QUIET="true"

# Uncomment to use basic console
GRUB_TERMINAL_INPUT="console"

# Uncomment to disable graphical terminal
#GRUB_TERMINAL_OUTPUT="console"

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE="1680x1050x8"
GRUB_GFXMODE="1024x768,800x600"

# Uncomment to allow the kernel use the same resolution used by grub
GRUB_GFXPAYLOAD_LINUX="keep"

# Uncomment if you want GRUB to pass to the Linux kernel the old parameter
# format "root=/dev/xxx" instead of "root=/dev/disk/by-uuid/xxx"
#GRUB_DISABLE_LINUX_UUID="true"

# Uncomment to disable generation of recovery mode menu entries
GRUB_DISABLE_RECOVERY="true"

# Uncomment and set to the desired menu colors.  Used by normal and wallpaper
# modes only.  Entries specified as foreground/background.
export GRUB_COLOR_NORMAL="light-blue/black"
export GRUB_COLOR_HIGHLIGHT="light-cyan/blue"

# Uncomment one of them for the gfx desired, a image background or a gfxtheme
#GRUB_BACKGROUND="/path/to/wallpaper"
GRUB_THEME="/usr/share/grub/themes/artix/theme.txt"

# Uncomment to get a beep at GRUB start
#GRUB_INIT_TUNE="480 440 1"

GRUB_SAVEDEFAULT="true"

GRUB_DISABLE_LINUX_RECOVERY="true"

/etc/mkinitcpio.conf

Code: [Select]
# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run.  Advanced users may wish to specify all system modules
# in this array.  For instance:
#     MODULES=(piix ide_disk reiserfs)
MODULES=""

# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image.  This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=()

# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way.  This is useful for config files.
FILES=""

# HOOKS
# This is the most important setting in this file.  The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added.  Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
##   This setup specifies all modules in the MODULES setting above.
##   No raid, lvm2, or encrypted root is needed.
#    HOOKS=(base)
#
##   This setup will autodetect all modules for your system and should
##   work as a sane default
#    HOOKS=(base udev autodetect block filesystems)
#
##   This setup will generate a 'full' image which supports most systems.
##   No autodetection is done.
#    HOOKS=(base udev block filesystems)
#
##   This setup assembles a pata mdadm array with an encrypted root FS.
##   Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
#    HOOKS=(base udev block mdadm encrypt filesystems)
#
##   This setup loads an lvm2 volume group on a usb device.
#    HOOKS=(base udev block lvm2 filesystems)
#
##   NOTE: If you have /usr on a separate partition, you MUST include the
#    usr, fsck and shutdown hooks.
HOOKS="base udev block autodetect modconf keyboard keymap filesystems fsck"

# COMPRESSION
# Use this to compress the initramfs image. By default, zstd compression
# is used. Use 'cat' to create an uncompressed image.
#COMPRESSION="zstd"
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
#COMPRESSION="lz4"

# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=()

/etc/fstab.

Code: [Select]
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
#UUID=a26f05dc-39bb-47f0-87bc-1e3211e7cbef /              ext4    defaults,noatime 0 1
PARTUUID=293123a0-c715-d349-b142-91dd19d0169a /              ext4    defaults,noatime 0 1
#UUID=E396-8A03                            /boot/efi      vfat    umask=0077 0 2
PARTUUID=bd80e68a-3102-3347-9d43-773f14643b34 /boot/efi      vfat    umask=0077 0 2
#UUID=00b06fff-7ece-4c5a-b127-5fa34558e7ed /home          ext4    defaults,noatime 0 2
PARTUUID=53b2ef46-a215-4e47-9894-06eb1ab8ba1a /home          ext4    defaults,noatime 0 2

And maybe the output of the lsblk command I listed in my previous post.

Code: [Select]
artix-live:[root]:/home/artix# lsblk -o NAME,FSTYPE,SIZE,UUID,PARTUUID
NAME        FSTYPE     SIZE UUID                                 PARTUUID
loop0       squashfs  57.1M                                     
loop1       squashfs   1.2G                                     
sda         iso9660  115.4G 2021-04-26-01-53-54-00              
├─sda1      iso9660    1.4G 2021-04-26-01-53-54-00              
└─sda2      vfat         4M B92A-A588                           
nvme0n1              476.9G                                     
├─nvme0n1p1 vfat       260M 86AB-E73F                            679cf965-98b8-41fa-9ad5-781c0c90dc94
├─nvme0n1p2             16M                                      567e5c30-5ba1-4c89-aff2-d604c1a75685
├─nvme0n1p3 ntfs     237.8G E6A0AC77A0AC503B                     a111e5c0-acaa-489e-999a-b6daa89ce7dd
├─nvme0n1p4 ntfs      1000M 246AAD126AACE1B2                     065c7b96-124c-494e-a6fe-88f879a8916f
├─nvme0n1p5 vfat         1G E396-8A03                            bd80e68a-3102-3347-9d43-773f14643b34
├─nvme0n1p6 ext4        30G a26f05dc-39bb-47f0-87bc-1e3211e7cbef 293123a0-c715-d349-b142-91dd19d0169a
└─nvme0n1p7 ext4     206.8G 00b06fff-7ece-4c5a-b127-5fa34558e7ed 53b2ef46-a215-4e47-9894-06eb1ab8ba1a

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

Reply #10
So, you are using an SSD. You might need to add additional parameters to your kernel command line.

For example (found by web search):
https://ubuntuforums.org/archive/index.php/t-2408864.html
Quote
3) Go to the "linux" line and, after
quiet splash, add the words
nvme_core.default_ps_max_latency_us=200 (see also https://askubuntu.com/questions/1099048/18-04-and-18-10-fail-to-boot-nvme0-failed-to-set-apst-feature-19). Then press Ctrl+X to boot with these new option included.

Also, check that your ESP has "boot" and "esp" flags. (parted -l /dev/nvme0n1 should list ESP as fat16 with boot,esp flags, and fdisk -l /dev/nvme0n1 should list its type as "EFI System".)
Well the installer that came in artix-plasma-runit-20210426-x86_64.iso wouldn't recognize the partition as a boot partition unless it was mounted at /boot/efi/
The GUI installer's name is calamares, and it is the same for all flavors of Artix. The only thing which differs among them is the initial package selection. So this problem definitely isn't related to Plasma.

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

Reply #11
Ok, what command do I run to get the changes into the bootloader?

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

Reply #12
Ok, but what command do I type to get changes to the various configuration files incorporated into the bootloader?

Also the calamares Artix Linux Installer doesn't have ESP in the list of flags.

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

Reply #13
First, don't double post. There is the "Modify" menu item under "More..." button in the bottom right of posts, use that instead.

Next, you can set the flags manually using any partition software (man parted, man fdisk). When setting flags from Calamares, some people reported "boot" flag working as well:

Three year old issue closed last year:
https://github.com/calamares/calamares/issues/891

Two year old issue closed last year:
https://github.com/calamares/calamares/issues/1192

Don't forget to also set up swap partition.

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

Reply #14
Ok, but what command do I run to get the changes I made to /etc/fstab into the bootloader, or wherever they need to be to take effect?