You are not logged in.
Howdy,
After upgrading this morning, when I try to boot up I get an error:
starting version 239
ERROR: device 'UUID=f46a03aa-b1db-4ee2-9c74-d71150abc71a' not found. Skipping fsck.
mount: /new_root: can't find UUID=f46a03aa-b1db-4ee2-9c74-d71150abc71a
You are now being dropped into an emergency shell.I CAN boot using the fallback initramfs image. I'm not sure how to debug this since I can't find any devices named /dev/sd*.
Any ideas?
Last edited by sgillespie (2018-10-09 14:17:50)
Offline
Please provide your "/etc/mkinitcpio.conf" and the output of "mkinitcpio -P" and "lsblk -o +UUID".
Also do not truncate the disk's UUID that cannot be found. It may very well be essential to the issue.
Last edited by schard (2018-10-09 13:04:16)
Inofficial first vice president of the Rust Evangelism Strike Force
Offline
Also do not truncate the disk's UUID that cannot be found. It may very well be essential to the issue.
Added to my original post
Please provide your "/etc/mkinitcpio.conf" and the output of "mkinitcpio -P" and "lsblk -o +UUID".
Here's my mkinitcpio.conf (I've removed the comments for clarity)
MODULES=()
BINARIES=()
FILES=()
HOOKS=(base udev autodetect modconf block filesystems keyboard fsck)The output of "lsblk -o +UUID"
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT UUID
sda 8:0 0 238.5G 0 disk
├─sda1 8:1 0 500M 0 part 0CD7-29EC
├─sda2 8:2 0 128M 0 part
└─sda3 8:3 0 237.9G 0 part 6A7CDA3A7CDA012D
sdb 8:16 0 232.9G 0 disk
├─sdb1 8:17 0 1024M 0 part /boot E0E0-CD52
├─sdb2 8:18 0 2G 0 part [SWAP] c3a9b591-a7eb-4514-82aa-fe4d3034cefa
└─sdb3 8:19 0 229.9G 0 part / f46a03aa-b1db-4ee2-9c74-d71150abc71aand finally, "mkinitcpio -P"
==> 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: 4.18.12-arch1-1-ARCH
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> 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: 4.18.12-arch1-1-ARCH
-> 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.imgLast edited by sgillespie (2018-10-09 13:54:56)
Offline
Maybe you are affected by this bug?
Offline
Maybe you are affected by this bug?
That looks correct. I am indeed booting from an external harddrive
EDIT: The workaround listed in the bug fixes it for me. In summary, add "usb_storage" and "uas" to MODULES array, then rerun "mkinitcpio -P".
Last edited by sgillespie (2018-10-09 14:19:58)
Offline