[SOLVED] unable to boot after update - error: device 'UUID' not found

jack_slapped · 2022-07-01 22:52:47

loqs wrote:

What about iommu=pt which allows IOMMU for VMs but not the host?

this causes the boot to fail again with the same error.

seth · 2022-07-02 06:10:49

See whether you get away w/

swiotlb=force

(no iommu parameter)

jack_slapped · 2022-07-03 21:08:01

seth wrote:

See whether you get away w/
swiotlb=force
(no iommu parameter)

this also gets it to boot, but breaks vm's. getting the error

error starting domain: unsupported configuration: host doesnt support passthrough of host pci devices.

jack_slapped · 2023-04-08 19:56:56

seth wrote:

You "need" the main kernel if you've newer HW that lacks support in older kernels, however your premise is a fallacy.
At some point a main kernel will become the LTS kernel and if it still has that problem, because it never got addressed - and there's no guarantee that it will be - there's no easy way back (but downgrading)
If you're not short on boot partition space, I'd simply have the main and the LTS kernel installed at all times and if an update welcomes you with an unpleasent surprise, you have a fallback solution to rely on until the problem in the other kernel is resolved.

You were totally right seth... I thought I would just roll with the LTS and this problem im having would just kinda sort itself out. well now the LTS kernel is doing the same thing. I did find a few other people posting something similar in other threads like this one. I'm thinking its possibly due to how I installed grub and most likely due to the kernel updating. i cant figure out why its acting like grub isnt installed or that the UUID for the /boot partition isnt there.

1. https://bbs.archlinux.org/viewtopic.php?id=284828

2. https://bbs.archlinux.org/viewtopic.php?id=284761

3. https://bbs.archlinux.org/viewtopic.php?id=284764

here is some more information on my system

my /etc/fstab

# Static information about the filesystems.
# See fstab(5) for details.

# <file system> <dir> <type> <options> <dump> <pass>
# /dev/nvme1n1p2
UUID=28654d63-5274-4e13-8a7f-e6a1d005394b	/         	ext4      	rw,relatime	0 1

# /dev/nvme1n1p1
UUID=D853-076C     	/boot     	vfat      	rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro	0 2

i booted from the installation media to try reinstalling grub and running mkinitcpio -P. i ran these commands to reinstall grub from arch-chroot installation media.

mount /dev/nvme1n1p2 /mnt
mount /dev/nvme1n1p1 /mnt/boot
arch-chroot /mnt
grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id=GRUB
grub-mkconfig -o /boot/grub/grub.cfg

im going to reboot back into the installation media and get some output of commands like lsblk. is there any other commands i should get the output to?

seth · 2023-04-08 21:29:49

[    3.802848] vfio_pci: add [10de:1b06[ffffffff:ffffffff]] class 0x000000/00000000
[    3.819485] vfio_pci: add [10de:10ef[ffffffff:ffffffff]] class 0x000000/00000000
[    3.852867] vfio_pci: add [144d:a808[ffffffff:ffffffff]] class 0x000000/00000000

Those are the nvidia GPU (and hdmi audio) and yuor nvme(s) - what if you https://wiki.archlinux.org/title/PCI_pa … _device_ID ?

jack_slapped · 2023-04-12 03:16:28

so i actually have that already setup. i had a problem when these were not being grabbed early enough.

my vfio.conf looks like this

options vfio-pci ids=10de:1b06,10de:10ef,144d:a808

and i believe it gets loaded with mkinicpio? mine below.

# 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=(vfio vfio_iommu_type1 vfio_pci amdgpu radeon)

# 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 filesystems keyboard 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=()

here is the output of lsblk

NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
loop0         7:0    0 687.9M  1 loop 
sda           8:0    1   7.5G  0 disk 
└─sda1        8:1    1   7.5G  0 part 
nvme1n1     259:0    0 931.5G  0 disk 
├─nvme1n1p1 259:2    0   512M  0 part /boot
└─nvme1n1p2 259:3    0   931G  0 part /

output of blkid

/dev/nvme0n1p1: LABEL="Recovery" BLOCK_SIZE="512" UUID="EC70C11470C0E684" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="251a5a8f-3e45-49eb-b860-388b32617ac1"
/dev/nvme0n1p4: BLOCK_SIZE="512" UUID="6C38CB7A38CB41B6" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="4ae33389-fb39-4fef-9b0a-049950721039"
/dev/nvme0n1p2: UUID="32C1-79AA" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="7b1b5962-dbc0-4513-8a31-ec55ec72429c"
/dev/nvme1n1p2: UUID="28654d63-5274-4e13-8a7f-e6a1d005394b" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="arch" PARTUUID="f9f39234-1ee0-4d09-8c0a-dd1e1dfdd8d2"
/dev/nvme1n1p1: UUID="D853-076C" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="boot" PARTUUID="a8b481bd-dc57-4b76-801e-17897d3da7ce"
/dev/loop0: TYPE="squashfs"
/dev/sda1: LABEL="ARCH_202304" UUID="E820-7669" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="Main Data Partition" PARTUUID="0a071c02-9142-4408-99a9-228f15cf7847"
/dev/nvme0n1p3: PARTLABEL="Microsoft reserved partition" PARTUUID="8e62a249-ca2e-47f4-b521-a655221f4a4b"

Last edited by jack_slapped (2023-04-12 03:17:41)

jack_slapped · 2023-04-12 03:24:15

I'm wondering if it has something to do with the mounting of /boot or the grub installation. I saw one thread where someone had grub installed in some other directory which would not get updated, updates would update a different grub or boot directory but on reboot it would still load the directory with the old files. I wonder if I did something wrong with my grub install where its not actually updating for some reason or is in the wrong directory, or maybe grub is sourcing the wrong directory? i also wondered if maybe udev isnt coming up early enough and so maybe the boot process doesnt see the uuid's of the nvme drives bc they tech hadnt been assigned uuids. i had that problem with my graphics cards since they boot so fast with an nvme drive.

seth · 2023-04-12 12:04:51

Why are you passing through the nvme?

jack_slapped · 2023-04-13 00:10:09

so i have a second nvme thats my old windows install. i passed it through for gaming in linux. i thought that would give better performance for the windows vm, but im not really sure tbh. let me post the entire lsblk output just in case its relevant. pretty sure nvme0n1 is the windows nvme.

NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
loop0         7:0    0 687.9M  1 loop 
sda           8:0    1   7.5G  0 disk 
└─sda1        8:1    1   7.5G  0 part 
nvme1n1     259:0    0 931.5G  0 disk 
├─nvme1n1p1 259:2    0   512M  0 part /boot
└─nvme1n1p2 259:3    0   931G  0 part /
nvme0n1     259:1    0 931.5G  0 disk 
├─nvme0n1p1 259:4    0   529M  0 part 
├─nvme0n1p2 259:5    0   100M  0 part 
├─nvme0n1p3 259:6    0    16M  0 part 
└─nvme0n1p4 259:7    0 930.9G  0 part

seth · 2023-04-13 06:02:08

Did you try the behavior when not passing it through but only the GPU?

jack_slapped · 2023-04-13 19:40:15

not yet. once i get home ill give that a shot.

seth · 2023-04-13 19:50:45

Ifyou want a spoiler, take a close look at #18

jack_slapped · 2023-04-14 03:11:30

you were totally right seth. when i removed the nvme drive 144d:a808 from my vfio.conf, it fixed it.

options vfio-pci ids=10de:1b06,10de:10ef

i also updated the system, ran grub-mkconfig -o /boot/grub/grub.cfg, then ran mkinitcpio -P just in case. but as soon as i added 144d:a808 back in wouldnt boot with the same error. i went ahead and updated my default/grub as well and removed amd_iommu. doesnt look like its really needed anymore from what i read. new grub looks like this.

GRUB_CMDLINE_LINUX_DEFAULT="loglevel=3 hugepages=2048"

Thank you so much for the help! Everything is working again. Including my windows VM. Would you by chance be able to explain what was happening/how that fixed it?

Last edited by jack_slapped (2023-04-14 03:14:32)

seth · 2023-04-14 05:42:37

Devices you pass through are not available to the OS.
You've two nvme's
What's the product and vendor ID of the one you didn't want to pass through?

Edit: I assume you only ever effectively altered the kernel commandline to pass through those devices w/ the update implicitly running grub-mkconfig, but that's a guess.

Last edited by seth (2023-04-14 05:43:54)

jack_slapped · 2023-04-14 14:29:40

i was able to find some of the drive information using the nvme command. here's the output. is that the information you were looking for ? They should be the same exact drive just about. I bought 2 of them to do a gpu passthrough setup. I do remember reading something about a glitch involving identical nvme drives and the os not being able to distinguish between the two, but i cant remember where i read it or if it was even applicable to my setup.

/dev/nvme1n1          /dev/ng1n1            S59ANJ0N314586P      Samsung SSD 970 EVO Plus 1TB             0x1        828.36  GB /   1.00  TB    512   B +  0 B   2B2QEXM7
/dev/nvme0n1          /dev/ng0n1            S59ANJ0N315057J      Samsung SSD 970 EVO Plus 1TB             0x1        844.16  GB /   1.00  TB    512   B +  0 B   2B2QEXM7

seth · 2023-04-14 14:48:24

You're missing the point.
You're passing through a PCI device by its ID.
But both nvme's have the same vendor and model ID, so they both meet the condition and you're hiding the one you wanted to keep from the OS by accidentally passing it through (as well)

jack_slapped · 2023-04-14 15:21:01

Ahhhh I see now. That makes sense. It doesn't even look like passing the nvme drive is even necessary, but good to know about identical drives being assigned the same ID. Thanks again for helping figure this out and taking the time to explain!

Arch Linux

#26 2022-07-01 22:52:47

Re: [SOLVED] unable to boot after update - error: device 'UUID' not found

#27 2022-07-02 06:10:49

Re: [SOLVED] unable to boot after update - error: device 'UUID' not found

#28 2022-07-03 21:08:01

Re: [SOLVED] unable to boot after update - error: device 'UUID' not found

#29 2023-04-08 19:56:56

Re: [SOLVED] unable to boot after update - error: device 'UUID' not found

#30 2023-04-08 21:29:49

Re: [SOLVED] unable to boot after update - error: device 'UUID' not found

#31 2023-04-12 03:16:28

Re: [SOLVED] unable to boot after update - error: device 'UUID' not found

#32 2023-04-12 03:24:15

Re: [SOLVED] unable to boot after update - error: device 'UUID' not found

#33 2023-04-12 12:04:51

Re: [SOLVED] unable to boot after update - error: device 'UUID' not found

#34 2023-04-13 00:10:09

Re: [SOLVED] unable to boot after update - error: device 'UUID' not found

#35 2023-04-13 06:02:08

Re: [SOLVED] unable to boot after update - error: device 'UUID' not found

#36 2023-04-13 19:40:15

Re: [SOLVED] unable to boot after update - error: device 'UUID' not found

#37 2023-04-13 19:50:45

Re: [SOLVED] unable to boot after update - error: device 'UUID' not found

#38 2023-04-14 03:11:30

Re: [SOLVED] unable to boot after update - error: device 'UUID' not found

#39 2023-04-14 05:42:37

Re: [SOLVED] unable to boot after update - error: device 'UUID' not found

#40 2023-04-14 14:29:40

Re: [SOLVED] unable to boot after update - error: device 'UUID' not found

#41 2023-04-14 14:48:24

Re: [SOLVED] unable to boot after update - error: device 'UUID' not found

#42 2023-04-14 15:21:01

Re: [SOLVED] unable to boot after update - error: device 'UUID' not found

Board footer