Device Not Found on Boot

king_krab · 2022-01-15 19:10:43

On rebooting my machine I get the following error message and am dropped into an emergency shell without access to the keyboard:

Warning: /lib/modules/5.16.0-arch1-1/modules.devname not found - ignoring
Starting version 250.2-2-arch
ERROR: device 'UUID=2285e9c88-d14a-4988-bc3f-f9036dbfedab' not found. Skipping fsck.
mount: /new_root: can't find UUID=285e9c88-d14a-4988-bc3f-f9036dbfedab.
You are now being dropped into an emergency shell.
sh: can't access tty: job control turned off

From pacman -Q:

linux 5.15.5.arch1-1
linux-firmware 20211027.1d00989-1dev

From blkid for root partition:

/dev/nvme0n1p2: UUID="285e9c88-d14a-4988-bc3f-f9036dbfeda" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="a4f3dd0b-813a-024e-8d70-a1e3c0a72094"

From neofetch:

OS: Arch Linux x86_64
Host: Inspiron 16 7610
Kernel: 5.15.5-arch1-1
Uptime: 18 hours, 55 minutes
Packages: 729 (pacman)
Shell: bash 5.1.16
Resolution: 3072x1920
CPU: 11th Gen Intel i7-11800H (16) @ 4.600GHz
Memory: 445MiB / 15743MiB

Last edited by king_krab (2022-01-17 19:45:50)

seth · 2022-01-15 19:37:16

The bootloader or /etc/fstab reference a device w/ the UUID 285e9c88-d14a-4988-bc3f-f9036dbfedab which is at least not nvme0n1p2
You can boot the installation iso and inspect the bootloader (grub?) configuration and esp /etc/fstab in the installed system and compare it the the output of "lsblk -f"
The fix either the bootloader config or the fstab.

Scimmia · 2022-01-15 20:16:58

It looks like you have a mismatch between your kernel and your initramfs somehow. That first warning tells me that you're booting the 5.16.0-arch1-1 kernel, but the initramfs doesn't have modules for that kernel. Did pacman not regenerate the initramfs when you updated?

Last edited by Scimmia (2022-01-15 20:18:18)

king_krab · 2022-01-16 16:47:18

I tried booting with the fallback-initramfs. But I still got dropped into an emergency shell with no keyboard.

mount: /new-root: can't find UUID=285e9c88-d14a-4988-bc3f-f9036dbfedab.
You are now being dropped into an emergency shell.
sh: can't access tty; jon control turned off

I have also tried regenerating the initramfs using mkinitcpio and rebootint to no avail. I'm sure I'm missing something.

Last edited by king_krab (2022-01-17 19:46:08)

seth · 2022-01-16 16:49:53

seth wrote:

boot the installation iso and inspect the bootloader (grub?) configuration and esp /etc/fstab in the installed system and compare it the the output of "lsblk -f"
Then fix either the bootloader config or the fstab.

Edit: the kernel versions in you OP are all over the place, the initial error indeed suggests you're booting some 5.16 but the pacman -Q output says you've the *older* 5.15.5.arch1-1 installed (typical fuck-up is the other way round, where you installed a new kernel but keep booting the old one) and the neofetch output also claims you're running the 5.15.5-arch1-1 kernel
You might want to elaborate on that situation.

However, the device w/ the searched UUID can't be found and that's the immediate issue.

Last edited by seth (2022-01-16 16:52:32)

king_krab · 2022-01-16 17:32:28

Other than noting that both commands give the same UUID and mountpoint, I'm not sure what discrepancies to look for.

From lsblk -f

NAME           FSTYPE     FSVER      LABEL        UUID                                                      FSAVAIL     FSUSE%   MOUNTPOINTS
nvme0n1p2    ext4            1.0                              285e9c88-d14a-4988-bc3f-f9036dbfedab    867.96         2%            /

From cat /etc/fstab

# <file system>                                                <dir>     <type>   <options>    <dump> <pass>
# /dev/nvme0n1p2
UUID=28539c88-d14a-4988-bc3f-f9036dbfedab    /           ext4       rw,relatime    0           1

Last edited by king_krab (2022-01-17 19:46:34)

seth · 2022-01-16 18:05:11

Ah, the different blkid was simply a typo
Try passing waitroot or rootdelay, https://unix.stackexchange.com/question … -rootdelay

Edit: and elaborate on the kernel situation - did you try a downgrade?

Last edited by seth (2022-01-16 18:06:29)

king_krab · 2022-01-16 22:13:32

Here are my kernel params on GRUB boot

setparams 'Arch Linux'

    load_video
    set gfxpayload=keep
    insmodn gzio
    insmod fat
    search --no-floppy --fs-uuid --set=root E384-C786
    echo        'Loading Linux linux ...'
    linux        /vmlinuz-linux root=UUID=285e9c88-d14a-4988-bc3f-f9036dbfedab rw  loglevel=3 quiet
    echo        'Loading initial ramdisk ...'
    initrd          /initramfs-linux.img

I tried adding rootdelay=15 to the end of this list, but the problem persisted. Oddly though, it didn't seem to wait for 15 seconds.

From ls boot after mounting nvme0n1p2 on /mnt and chroot-ing into /mnt:

initramfs-linux-fallback.img    initramfs-linux.img    vmlinuz-linux

I will try a downgrade next..

Last edited by king_krab (2022-01-17 19:47:10)

Head_on_a_Stick · 2022-01-17 17:24:26

king_krab wrote:

From ls boot after mounting nvme0n1p2 on /mnt and chroot-ing into /mnt:
initramfs-linux-fallback.img    initramfs-linux.img    vmlinuz-linux

What does the 'file' command say about vmlinuz-linux? It should show the version.

king_krab · 2022-01-17 17:51:25

From file vmlinuz-linux:

vmlinuz-linux: Linux kernel x86 boot execuatble bzImage, version 5.15.13-arch1-1 (linux@archlinux) #1 SMP PREEMPT Wed, 05 Jan 2022 16:20:59 +0000, R0-rootFS, swap_dev, Normal VGA

Last edited by king_krab (2022-01-17 19:48:17)

Scimmia · 2022-01-17 18:01:16

So how are you booting the 5.16.0 kernel?

king_krab · 2022-01-17 18:49:20

I'm really not sure. Everytime I run `pacman -Syu` it updates linux and linux-headers to 5.16, and then I have to fix it. So some discrepancy probably exists because of that. I thought the 5.15 kernel was supposed to be an LTS version. So I guess I'm a bit surprised pacman would update the kernel packages on the execution of such a routine command.

Another thing I just noticed is that `/boot/grub/grub.cfg` does not exist, which is a bit alarming since I had been running Arch fairly smoothly for over a week when I first encountered this boot problem.

Scimmia · 2022-01-17 19:19:10

And through all of this, you haven't once mentioned updating to 5.16 or fixing it. What, exactly, are you doing?

Head_on_a_Stick · 2022-01-17 19:21:56

Please edit your posts to use code tags instead of quote tags for terminal output.

king_krab wrote:

I thought the 5.15 kernel was supposed to be an LTS version

If you want to run an LTS kernel then install the linux-lts package.

king_krab wrote:

I just noticed is that `/boot/grub/grub.cfg` does not exist

Can we see

# parted --list

And also check the output of the 'set' command from the GRUB command line — that will list all the variables, which should include the root device and the configfile location.

king_krab · 2022-01-17 19:23:44

I'm just trying to get Arch to boot. One day I rebooted it, and I ran into this problem. I don't remember exactly, but I figure I must have run a bad update that messed with the kernel. It did not occur to me that `pacman -Syu` would do this. I guess I just presumed it would only update userspace programs.

Head_on_a_Stick · 2022-01-17 19:36:57

The parted command can be run from the live environment. See https://wiki.archlinux.org/title/List_o … ted_client for a way to share it from a console.

You can take a picture of the GRUB screen after running the set command. Share it via a hosting site and remember the 250x250px image size limit.

king_krab · 2022-01-17 19:45:03

From `parted --list`

Model: KXG60ZNV1T02 NVMe KIOXIA 1024GB (nvme)
Disk /dev/nvme0n1: 1024GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number    Start         End        Size        File system    Name    Flags
1                1049kB   630MB   629MB        fat32                  boot, esp
2                630MB    1024GB 1024GB        ext4

From grub> set:

?=0
chosen=gnulinux-advanced-285e9c88-d14a-4988-bc3f-f9036dbfedab
cmdpath=(hd1,gpt1)/EFI/GRUB
color_highlight=black/light-gray
color_normal=light_gray/black
feature_200_final=y
feature_all_video_module=y
feature_chainloader_bpb=y
feature_default_font_path=y
feature_menuentry_id=y
feture_menuentry_options=y
feature_nativedisk_cmd=y
feature_ntldr=y
feature_platform_search_hint=y
feature_timeout_style=y
grub_cpu=x86_64
grub_platform=efi
...
locale_dir=(hd1,gpt1)/grub/locale
menuentry_id_options=--id
...
prefix=(hd1,gpt1)/grub
root=hd1,gpt1
secondary_locale_dir=

Last edited by king_krab (2022-01-17 20:05:28)

seth · 2022-01-17 20:22:41

From cat /etc/fstab

Not "from" - post the entire fstab and the output of "mount" as well as the complete "lsblk -f" and grub set. "From" means you're filtering information and since you've no idea what's relevant, that's not helpful.

Your later revelations strongly suggest you're not installing the kernel on the boot partition and I guess everything else is just an outfall of you trying to "fix" that.

king_krab · 2022-01-17 20:38:26

/etc/fstab
http://ix.io/3MBD

mount
http://ix.io/3MBE

lsblk -f
http://ix.io/3MBF

Head_on_a_Stick · 2022-01-17 20:44:18

So grub.cfg is being read from /dev/nvme0n1p1 and I suspect you will find another vmlinuz-linux there as well, the version of which will not match /usr/lib/modules/ (on /dev/nvme0n1p2), hence the error in the OP.

No idea why /dev/nvme0n1p1 isn't being mounted under /boot though.

What happens if you run

# mount /boot

king_krab · 2022-01-17 21:03:56

While chroot-ed: mount -v /boot

mount: /dev/nvme0n1p1 mounted on /boot

Head_on_a_Stick · 2022-01-17 21:12:34

Ah, I see, this was all run after chrooting from the live image. You really should explain exactly what you're doing. We're not psychic and the surveillance cameras appear to be down at the moment...

So now you should update the kernel with /boot mounted correctly (ie, under /dev/nvme0n1p1).

If you ever have to "fix" things again make sure /dev/nvme0n1p1 is mounted correctly before doing anything with the kernel.

Arch Linux

#1 2022-01-15 19:10:43

Device Not Found on Boot

#2 2022-01-15 19:37:16

Re: Device Not Found on Boot

#3 2022-01-15 20:16:58

Re: Device Not Found on Boot

#4 2022-01-16 16:47:18

Re: Device Not Found on Boot

#5 2022-01-16 16:49:53

Re: Device Not Found on Boot

#6 2022-01-16 17:32:28

Re: Device Not Found on Boot

#7 2022-01-16 18:05:11

Re: Device Not Found on Boot

#8 2022-01-16 22:13:32

Re: Device Not Found on Boot

#9 2022-01-17 17:24:26

Re: Device Not Found on Boot

#10 2022-01-17 17:51:25

Re: Device Not Found on Boot

#11 2022-01-17 18:01:16

Re: Device Not Found on Boot

#12 2022-01-17 18:49:20

Re: Device Not Found on Boot

#13 2022-01-17 19:19:10

Re: Device Not Found on Boot

#14 2022-01-17 19:21:56

Re: Device Not Found on Boot

#15 2022-01-17 19:23:44

Re: Device Not Found on Boot

#16 2022-01-17 19:36:57

Re: Device Not Found on Boot

#17 2022-01-17 19:45:03

Re: Device Not Found on Boot

#18 2022-01-17 20:22:41

Re: Device Not Found on Boot

#19 2022-01-17 20:38:26

Re: Device Not Found on Boot

#20 2022-01-17 20:44:18

Re: Device Not Found on Boot

#21 2022-01-17 21:03:56

Re: Device Not Found on Boot

#22 2022-01-17 21:12:34

Re: Device Not Found on Boot

Board footer