You are not logged in.
Hello,
Running `pacman -Syu` caused a problem similar to https://bbs.archlinux.org/viewtopic.php?id=217104 , then I booted from a flash-drive, chrooted into it and ran `pacman -S linux`. Then I tried to boot:
...
:: running hook [encrypt]
Waiting 10 seconds for device /dev/disk/by-uuid/65280982-f6db-45b8-906e-a376855b34dc ...
Waiting 10 seconds for device /dev/MyVolGroup/root ...
ERROR: device `/dev/MyVolGroup/root` not found. Skipping fsck.
:: mounting `/dev/MyVolGroup/root` on real root
mount /new_root: no filesystem type specified.
You are now being dropped into an emergency shell.
sh: can't access tty: job control turned off
[rootfs ]#
As a side note, the keyboard did not work in this emergency shell.
Any Ideas?
Me reinstalling stuff and more info: https://pastebin.com/DXjkhZTL
My /etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.# <file system> <dir> <type> <options> <dump> <pass>
# /dev/mapper/MyVolGroup-root
UUID=e5c0b122-cdfc-4417-8a0a-aa82b3cba9c5 / ext4 rw,relatime 0 1# /dev/sda1
UUID=D1BB-1508 /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 2# /dev/mapper/MyVolGroup-swap
UUID=d5f62749-bdb5-4e9c-9b75-44e79c1ffa4e none swap defaults 0 0
UPDATE:
The problem was (probably) that I rebooted before `pacman -Syu` finished. Booting from a stick, chrooting into it and running `pacman -Syu` fixed it.
Last edited by volker_weissmann (2021-12-12 17:57:09)
Offline
Would you happen to have the journalctl of the fail mount ?
Offline
Would you happen to have the journalctl of the fail mount ?
There is no log:
`journalctl -b -0` gives me the log of chrooting into it and `journalctl -b -1` gives me the log of the last successful boot.
This is expected, because it fails before prompting for decryption passphrase.
Last edited by volker_weissmann (2021-12-12 08:18:20)
Offline