[SOLVED] Cannot start archlinux after update - Error: can't find UUID

Lifka · 2017-07-09 23:58:28

I updated archlinux with "pacman -Syu" and then when I've restart, the system can't start. This is the report:

Warning: /lib/modules/4.11.9-1-ARCH/modules.devname not found - ignoring
version 232
Error: device 'UUID=b5a9a977-e9a7-4d3d-96a9-dcf9c3a9010d' not found. Skipping fsck.
Error: can't find UUID=b5a9a977-e9a7-4d3d-96a9-dcf9c3a9010d 
You are now being dropped into a emergency shell.
Can't access tty: job control turned off

In that shell my keyboard doesn't work.

I'm trying with a livecd of archlinux: mounting the partitions and using chroot.
I check the uuid of the root partition in "/etc/fstab". It's my fstab:

# /dev/sda2
UUID=b5a9a977-e9a7-4d3d-96a9-dcf8c3a9010d   /           ext4        rw,relatime,data=ordered    0 1
 
# /dev/sda1
UUID=FBA9-977B          /boot       vfat        rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro    0 2
 
# /dev/sda4
UUID=a43b8426-c93a-4f32-99c8-9dd5cf645373   /home       ext4        rw,relatime,data=ordered    0 2
 
# /dev/sda3
UUID=9eec735e-3157-4e0e-a5c6-ef3a7c674201   none        swap        defaults    0

And it's the result of "lsblk -f"

NAME   FSTYPE   LABEL       UUID                                 MOUNTPOINT
loop0  squashfs                                                  /run/archiso/sfs/airootfs
sda                                                              
├─sda1 vfat                 FBA9-977B                            
├─sda2 ext4                 b5a9a977-e9a7-4d3d-96a9-dcf8c3a9010d /mnt
├─sda3 swap                 9eec735e-3157-4e0e-a5c6-ef3a7c674201 
└─sda4 ext4                 a43b8426-c93a-4f32-99c8-9dd5cf645373 /mnt/home

I've updated the system again with "pacman -Syu" and I tried to make "mkinitcpio -p linux", but it haven't solved the problem (in spite of the result of the command it's ok). This is the report:

==> 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.11.9-1-ARCH
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [block]
  -> Running build hook: [block]
WARNING: Possubly missing firmware for module: aic94xx
WARNING: Possubly missing firmware for module: wd719x
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> 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.11.9-1-ARCH
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [block]
WARNING: Possubly missing firmware for module: aic94xx
WARNING: Possubly missing firmware for module: wd719x
  -> Running build hook: [modconf]
  -> 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

I tried to change the order of HOOKS in "/etc/mkinitcpio.conf". But it doesn't work. This is the current order:

base udev block autodetect modconf filesystems keyboard fsck

"uname -r" returns:

4.11.7-1-ARCH

"pacman -Q linux" returns:

linux 4.11.9-1

The file of warrning "/lib/modules/4.11.9-1-ARCH/modules.devnam" exists.

I tried to install and use "linux-lts" but the result it's the same.
I use grub and I tried to reconfigure it too.

What can I do?
Thank you so much.

Last edited by Lifka (2017-07-10 02:00:55)

jasonwryan · 2017-07-10 00:51:06

/boot wasn't mounted when you ran the upgrade; hence the missing modules. Chroot in, make sure everything is correctly mounted and re-run the update.

Lifka · 2017-07-10 02:00:20

That's the problem... I can't undertand how I did not realize.
Thank you so much, jasonwryan.

Last edited by Lifka (2017-07-10 02:04:40)

martvefun · 2017-07-10 11:59:43

Thank you for the post, I got the exact same problem today.

This is what I did:

# cryptsetup luksOpen /dev/sda2 secretmount  # sda1 is boot and sda2 is the system
Enter passphrase for /dev/sda2:
# mount /dev/mapper/secretmount /mnt/mysystem
# mount /dev/sda2 /mnt/mysystem/boot
# arch-chroot /mnt/mysystem
# pacman -Syu
...
# mkinitcpio -p linux
...
# exit
# umount /mnt/mysystem/boot
# umount /mnt/mysystem
# cryptsetup luksClose /dev/mapper/secretmount

But now, when I boot, I got this screen

BootDevice Not Found

Please install an operating system on your hard disk.

Hard Disk - (3F0)

F2 System Diagnostic

What I am missing? (I am wondering if I did not messed up the bios)

Last edited by martvefun (2017-07-10 12:23:03)

Trilby · 2017-07-10 12:54:19

It's not clear to me that this problem was at all related. But even if it was it certainly isn't now; something luks related has gone wrong in your attempted fix leaving you with problems that are now completely unrelated to this thread. So rather than hijacking a solved thread, create your own thread. Feel free to link to this thread to explain the background of what led you to run the commands you did.

Closed.

Arch Linux

#1 2017-07-09 23:58:28

[SOLVED] Cannot start archlinux after update - Error: can't find UUID

#2 2017-07-10 00:51:06

Re: [SOLVED] Cannot start archlinux after update - Error: can't find UUID

#3 2017-07-10 02:00:20

Re: [SOLVED] Cannot start archlinux after update - Error: can't find UUID

#4 2017-07-10 11:59:43

Re: [SOLVED] Cannot start archlinux after update - Error: can't find UUID

#5 2017-07-10 12:54:19

Re: [SOLVED] Cannot start archlinux after update - Error: can't find UUID

Board footer