You are not logged in.

Pages: 1

#1 2020-02-07 04:59:38

calvertdw
Member
Registered: 2020-02-07
Posts: 18

[SOLVED] ERROR: device 'UUID=xxx' not found after upgrade to linux 5.5

I had a pretty nasty error after upgrading to the new 5.5 kernel.

It looked like an error related to fstab. I was unable to use the keyboard.

Starting version 244.2-1-arch
ERROR: device 'UUID=...' not found. Skipping fsck.
mount: /new_root: can't find UUID=...
You are now being dropped into and emergency shell.
sh: can't access tty: job control turned off
[rootfs ]# _

After chrooting via live, I tried checking, altering fstab, reverting kernel, rerunning mkinitcpio and update grub, and the error prevailed.

What fixed it was selecting the fallback initramfs in grub, running mkinitcpio and updating grub in there, and rebooting.

Now 5.5.2 is working. (with Nvidia driver with no modifications on 1080 Ti)

Last edited by calvertdw (2020-03-03 04:44:20)

Offline

#2 2020-02-28 05:28:35

calvertdw
Member
Registered: 2020-02-07
Posts: 18

Re: [SOLVED] ERROR: device 'UUID=xxx' not found after upgrade to linux 5.5

This issue is back again on Linux 5.5.6-arch1-1

Except this time the workaround above does not work. fallback initrd works fine, but even after running mkinitcpio and updating grub, the issue remains.

Offline

#3 2020-02-28 08:07:59

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 25,232

Re: [SOLVED] ERROR: device 'UUID=xxx' not found after upgrade to linux 5.5

Into what kind of partition are you generating your images into? Do you have enough space on it? If it's a vfat ESP, run a fsck over it.

Offline

#4 2020-03-01 06:00:55

calvertdw
Member
Registered: 2020-02-07
Posts: 18

Re: [SOLVED] ERROR: device 'UUID=xxx' not found after upgrade to linux 5.5

It is a vfat EFI System Partition. I ran fsck from a live USB and results came back fine. I should note running on fallback I can't tell a difference from the normal mode.

# fsck /dev/sdb1
fsck from util-linux 2.35
fsck.fat 4.1 (2017-01-24)
/dev/sdb1: 3 files, 33/130812 clusters

# fsck /dev/sdb2
fsck from util-linux 2.35
e2fsck 1.45.5 (07-Jan-2020)
/dev/sdb2: clean, 1846640/61005824 files, 80872860/244009297 blocks

Here are some more details about my disk setup:

Disk /dev/sdb: 931.53 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: Samsung SSD 860 
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 31A2D78D-36E4-E34A-811C-3F1B21D57893

Device       Start        End    Sectors   Size Type
/dev/sdb1     2048    1050623    1048576   512M EFI System
/dev/sdb2  1050624 1953125000 1952074377 930.8G Linux filesystem

Model: ATA Samsung SSD 860 (scsi)
Disk /dev/sdb: 1000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size   File system  Name  Flags
 1      1049kB  538MB   537MB  fat32              boot, esp
 2      538MB   1000GB  999GB  ext4

[...]$ ls -halp /dev/disk/by-uuid/
total 0
drwxr-xr-x 2 root root 240 Feb 29 10:13 ./
drwxr-xr-x 8 root root 160 Feb 29 10:13 ../
lrwxrwxrwx 1 root root  10 Feb 29 10:48 066C02CA6C02B509 -> ../../sdc1
lrwxrwxrwx 1 root root  10 Feb 29 10:48 18E43840E4382304 -> ../../sdc2
lrwxrwxrwx 1 root root  10 Feb 29 10:48 1A9224189223F743 -> ../../sdc5
lrwxrwxrwx 1 root root  10 Feb 29 10:48 3442177742173D54 -> ../../sdd1
lrwxrwxrwx 1 root root  10 Feb 29 10:48 4A78DEE178DECB39 -> ../../sdc3
lrwxrwxrwx 1 root root   9 Feb 29 10:13 5302cb6700000000 -> ../../sr0
lrwxrwxrwx 1 root root  10 Feb 29 10:48 81E4-437F -> ../../sdb1
lrwxrwxrwx 1 root root  10 Feb 29 10:48 89d5d6d9-fda8-4d55-a165-8211ad893a47 -> ../../sdb2
lrwxrwxrwx 1 root root  10 Feb 29 10:48 A4F9-904A -> ../../sdc4
lrwxrwxrwx 1 root root  10 Feb 29 10:48 F4D4BF1CD4BEE052 -> ../../sda2

fstab:

[...]$ cat /etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.

# <device>                                      <dir>           <type>          <options>       <dump> <fsck>
# /dev/sdb1
UUID=81E4-437F                                  /efi            vfat            defaults        0      2
# /dev/sdb2
UUID=89d5d6d9-fda8-4d55-a165-8211ad893a47       /               ext4            defaults        0      1

[...]$ df -h
Filesystem      Size  Used Avail Use% Mounted on
dev             7.8G     0  7.8G   0% /dev
run             7.8G  1.9M  7.8G   1% /run
/dev/sdb2       916G  293G  577G  34% /
tmpfs           7.8G   41M  7.8G   1% /dev/shm
tmpfs           7.8G     0  7.8G   0% /sys/fs/cgroup
tmpfs           7.8G  2.6M  7.8G   1% /tmp
/dev/sdb1       511M  132K  511M   1% /efi
tmpfs           1.6G   24K  1.6G   1% /run/user/1000


Starting version 244.2-1-arch
ERROR: device 'UUID=89d5d6d9-fda8-4d55-a165-8211ad893a47' not found. Skipping fsck.
mount: /new_root: can't find UUID=89d5d6d9-fda8-4d55-a165-8211ad893a47.
You are now being dropped into and emergency shell.
sh: can't access tty: job control turned off
[rootfs ]# _

Last edited by calvertdw (2020-03-01 06:03:06)

Offline

#5 2020-03-01 07:37:13

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,056

Re: [SOLVED] ERROR: device 'UUID=xxx' not found after upgrade to linux 5.5

Compare lsblk -f w/ the error to check that it's looking for the proper UUID.

The initramfs build could have failed for other reasons.
Mount /dev/sdb1 to eg. /mnt/boot and check the timestamps on /mnt/boot/initramfs-linux*
If they're old, follow https://wiki.archlinux.org/index.php/Pa … an_upgrade and re-install the kernel packages (linux, linux-lts, …) and pay attention to the update process, notably errors during the initramfs generation.

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

Offline

#6 2020-03-03 04:28:50

calvertdw
Member
Registered: 2020-02-07
Posts: 18

Re: [SOLVED] ERROR: device 'UUID=xxx' not found after upgrade to linux 5.5

I checked lsblk -f and the UUID matches the error. I can also boot fine on the fallback, so I think that rules out a UUID mismatch.

I checked the timestamps of the initramfs-linux* images and they look good:

$ ls -halp /boot
total 76M
drwxr-xr-x  3 root root 4.0K Feb 26 21:31 ./
drwxr-xr-x 18 root root 4.0K Feb  6 21:28 ../
drwxr-xr-x  6 root root 4.0K Feb 27 23:27 grub/
-rw-r--r--  1 root root  44M Feb 27 23:27 initramfs-linux-fallback.img
-rw-r--r--  1 root root  23M Feb 27 23:27 initramfs-linux.img
-rw-r--r--  1 root root 3.0M Dec 11 06:32 intel-ucode.img
-rw-r--r--  1 root root 6.3M Feb 26 21:31 vmlinuz-linux

Since I can boot fine in fallback mode, I tried reinstalling the linux package from there. I do have errors during mkinitcpio:

sort: read failed: '/sys/devices/pci0000:00/0000:00:1c.4/0000:06:00.0/usb7/7-2/7-2:1.0/0003:256F:C62E.10CA/power_supply/hid-0003:256F:C62E.10CA-battery/uevent': No such device
modprobe: ERROR: missing parameters. See -h.

Full log:

$ sudo pacman -S linux
warning: linux-5.5.6.arch1-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Packages (1) linux-5.5.6.arch1-1

Total Installed Size:  74.30 MiB
Net Upgrade Size:       0.00 MiB

:: Proceed with installation? [Y/n] 
(1/1) checking keys in keyring                                                                              [################################################################] 100%
(1/1) checking package integrity                                                                            [################################################################] 100%
(1/1) loading package files                                                                                 [################################################################] 100%
(1/1) checking for file conflicts                                                                           [################################################################] 100%
(1/1) checking available disk space                                                                         [################################################################] 100%
:: Processing package changes...
(1/1) reinstalling linux                                                                                    [################################################################] 100%
:: Running post-transaction hooks...
(1/4) Arming ConditionNeedsUpdate...
(2/4) Updating module dependencies...
(3/4) Updating linux initcpios...
==> 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.5.6-arch1-1
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
sort: read failed: '/sys/devices/pci0000:00/0000:00:1c.4/0000:06:00.0/usb7/7-2/7-2:1.0/0003:256F:C62E.1052/power_supply/hid-0003:256F:C62E.1052-battery/uevent': No such device
modprobe: ERROR: missing parameters. See -h.
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [keyboard]
  -> 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.5.6-arch1-1
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: wd719x
==> WARNING: Possibly missing firmware for module: aic94xx
  -> Running build hook: [filesystems]
  -> Running build hook: [keyboard]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-fallback.img
==> Image generation successful
(4/4) Update Nvidia module in initcpio

Last edited by calvertdw (2020-03-03 04:30:17)

Offline

#7 2020-03-03 04:33:42

calvertdw
Member
Registered: 2020-02-07
Posts: 18

Re: [SOLVED] ERROR: device 'UUID=xxx' not found after upgrade to linux 5.5

I think that error comes from my Corsair Link power supply that has USB power monitoring. The AX860i.

Offline

#8 2020-03-03 04:42:54

calvertdw
Member
Registered: 2020-02-07
Posts: 18

Re: [SOLVED] ERROR: device 'UUID=xxx' not found after upgrade to linux 5.5

Sure enough, I unplugged my Corsair Link and the mkinitcpio error disappeared and I was able to boot the default image. Thanks!

Offline

Pages: 1

Board footer

Powered by FluxBB