Arch Linux

harryGoldsonXWNF

Member

Registered: 2023-04-01

Posts: 3

[SOLVED] ERROR: device 'UUID' not found. Skipping fsck.

After booting up possibly after an update (issue happened yesterday), I was greeted with:     

ERROR: device 'c2046a53-17e7-4b18-92ab-ffe883b1d330' not found. Skipping fsck.
mount: /new_root: can't find UUID=c2046a53-17e7-4b18-92ab-ffe883b1d330.
You are now being dropped into an emergency shell.
sh: can't access tty: job control turned off
[rootfs ]#

However, I booted into the fallback initramfs kernel option, and the system boots without any issues. So, I am making this forum post booted from the same disk that I'm having the boot issue on.

# lsblk -o +uuid     

NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS                   UUID
sda           8:0    0   7.3T  0 disk
└─sda1        8:1    0   7.3T  0 part                               7b37ed5c-4db4-45b5-9bf2-265dca9b2857
sdb           8:16   0   5.5T  0 disk
└─sdb1        8:17   0   5.5T  0 part                               A4E1-9495
sdc           8:32   0   5.5T  0 disk
└─sdc1        8:33   0   5.5T  0 part                               D892-4418
zram0       254:0    0     4G  0 disk [SWAP]
nvme0n1     259:0    0 953.9G  0 disk
├─nvme0n1p1 259:1    0   511M  0 part /boot                         9330-939E
├─nvme0n1p2 259:2    0  58.7G  0 part /                             c2046a53-17e7-4b18-92ab-ffe883b1d330
└─nvme0n1p3 259:3    0 894.6G  0 part /home                         6ffd98b7-6480-44c8-a69b-3b810e01d000
nvme1n1     259:4    0 931.5G  0 disk
└─nvme1n1p1 259:5    0 931.5G  0 part /run/media/jimbo/extraStorage bc560d79-c0d4-41d2-8da7-a51d23a7769a

# cat /proc/cmdline

BOOT_IMAGE=/vmlinuz-linux-zen root=UUID=c2046a53-17e7-4b18-92ab-ffe883b1d330 rw rootfstype=ext4 loglevel=3 quiet nvidia-drm.modeset=1

sda, sdb, and sdc are external usb disks, btw.

I have never encountered this issue before, and have less than 3 months of experience using arch.  I have only arch linux installed, so this is not an issue concerning windows or any other os's on one system. My drive is unencrypted.

Currently using this fallback kernel option, how should I proceed?

Last edited by harryGoldsonXWNF (2023-04-02 11:37:13)

seth

Member

From: Don't DM me only for attention

Registered: 2012-09-03

Posts: 74,331

Re: [SOLVED] ERROR: device 'UUID' not found. Skipping fsck.

sudo lsinitcpio /boot/initramfs-linux.img| grep -i nvme

If the module is there, this might also be a race condition.
Try "rootwait" or "rootdelay=10" (the latter waits only 10 seconds for the root device)

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

harryGoldsonXWNF

Member

Registered: 2023-04-01

Posts: 3

Re: [SOLVED] ERROR: device 'UUID' not found. Skipping fsck.

# cd /boot

amd-ucode.img  EFI  grub  initramfs-linux-zen-fallback.img  initramfs-linux-zen.img  vmlinuz-linux-zen

# sudo lsinitcpio /boot/initramfs-linux-zen.img| grep -i nvme

(no output)

so, it appears that something is not there?

although, the fallback img . . .

# sudo lsinitcpio /boot/initramfs-linux-zen-fallback.img| grep -i nvme

usr/lib/modules/6.2.8-zen1-1-zen/kernel/drivers/nvme/
usr/lib/modules/6.2.8-zen1-1-zen/kernel/drivers/nvme/common/
usr/lib/modules/6.2.8-zen1-1-zen/kernel/drivers/nvme/common/nvme-common.ko
usr/lib/modules/6.2.8-zen1-1-zen/kernel/drivers/nvme/host/
usr/lib/modules/6.2.8-zen1-1-zen/kernel/drivers/nvme/host/nvme-core.ko
usr/lib/modules/6.2.8-zen1-1-zen/kernel/drivers/nvme/host/nvme-fabrics.ko
usr/lib/modules/6.2.8-zen1-1-zen/kernel/drivers/nvme/host/nvme-fc.ko
usr/lib/modules/6.2.8-zen1-1-zen/kernel/drivers/nvme/host/nvme.ko
usr/lib/modules/6.2.8-zen1-1-zen/kernel/drivers/nvme/host/nvme-rdma.ko
usr/lib/modules/6.2.8-zen1-1-zen/kernel/drivers/nvme/host/nvme-tcp.ko
usr/lib/modules/6.2.8-zen1-1-zen/kernel/drivers/nvme/target/
usr/lib/modules/6.2.8-zen1-1-zen/kernel/drivers/nvme/target/nvme-fcloop.ko
usr/lib/modules/6.2.8-zen1-1-zen/kernel/drivers/nvme/target/nvme-loop.ko
usr/lib/modules/6.2.8-zen1-1-zen/kernel/drivers/nvme/target/nvmet-fc.ko
usr/lib/modules/6.2.8-zen1-1-zen/kernel/drivers/nvme/target/nvmet.ko
usr/lib/modules/6.2.8-zen1-1-zen/kernel/drivers/nvme/target/nvmet-rdma.ko
usr/lib/modules/6.2.8-zen1-1-zen/kernel/drivers/nvme/target/nvmet-tcp.ko

can I just copy what's in the fallback img to the standard img?

seth

Member

From: Don't DM me only for attention

Registered: 2012-09-03

Posts: 74,331

Re: [SOLVED] ERROR: device 'UUID' not found. Skipping fsck.

https://wiki.archlinux.org/title/Mkinitcpio#MODULES
But please also post your mkinitcpio

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

harryGoldsonXWNF

Member

Registered: 2023-04-01

Posts: 3

Re: [SOLVED] ERROR: device 'UUID' not found. Skipping fsck.

# sudo mkinitcpio -P

==> Building image from preset: /etc/mkinitcpio.d/linux-zen.preset: 'default'
  -> -k /boot/vmlinuz-linux-zen -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-zen.img
==> Starting build: '6.2.8-zen1-1-zen'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [keyboard]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keymap]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux-zen.img'
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux-zen.preset: 'fallback'
  -> -k /boot/vmlinuz-linux-zen -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-zen-fallback.img -S autodetect
==> Starting build: '6.2.8-zen1-1-zen'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [keyboard]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keymap]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'aic94xx'
==> WARNING: Possibly missing firmware for module: 'bfa'
==> WARNING: Possibly missing firmware for module: 'qla1280'
==> WARNING: Possibly missing firmware for module: 'wd719x'
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux-zen-fallback.img'
==> Image generation successful

That was the solution! I will remember to re-process this in the event of future problems. 
I guess the problem was that kernel modules were not being loaded, which stopped fsck from being ran?

in any case, thank you for your help!