You are not logged in.
Hi everyone,
Arch won't boot after an update gone wrong: when loading, I get "timed out" for:
- /dev/zram0
- /dev/disk-by-uuid/<a string>
- /dev/disk-by-uuid/<another-string>
I am then prompted to insert my root password for maintenance.
I am totally utterly clueless as what to do.
I tried to run "journal -xb", but it prints indefinitely!
Last edited by masca (2024-06-24 09:45:52)
Offline
check your fstab against lsblk if the uuids still match
Offline
https://wiki.archlinux.org/title/Pacman … an_upgrade
LC_ALL=C pacman -Qkk --root=/mnt | grep -v ', 0 altered files'
from the iso w/ the system partition mounted into /boot will tell you what's broken - given that zram is unavailable, you can add the kernel to that list.
Every package that shows up w/ broken or missing mtree needs to be installed with "--dbonly" first, then again without that flag or you'll run into file conflicts.
NEVER! use "-x" with journalctl, it's just spam.
Offline
So, if I do
lsblk --output uuid
I get:
UUID
64c8db56-b9aa-487a-8259-a2806810426f
which is the same thing I see doing
cat /etc/fstab
for /, /home, /var/log, /var/cache/pacman/pkg, /.snapshots. There's a different UUID for /boot, which does not show in lsblk:
# <file system> <dir> <type> <options> <dump> <pass>
# /dev/mapper/ainstsds2
UUID=64c8db56-b9aa-487a-8259-a2806810426f / btrfs rw,relatime,ssd,space_cache=v2,subvolid=256,subvol=/@ 0 0
# /dev/mapper/ainstsds2
UUID=64c8db56-b9aa-487a-8259-a2806810426f /home btrfs rw,relatime,ssd,space_cache=v2,subvolid=257,subvol=/@home 0 0
# /dev/mapper/ainstsds2
UUID=64c8db56-b9aa-487a-8259-a2806810426f /var/log btrfs rw,relatime,ssd,space_cache=v2,subvolid=258,subvol=/@log 0 0
# /dev/mapper/ainstsds2
UUID=64c8db56-b9aa-487a-8259-a2806810426f /var/cache/pacman/pkg btrfs rw,relatime,ssd,space_cache=v2,subvolid=259,subvol=/@pkg 0 0
# /dev/mapper/ainstsds2
UUID=64c8db56-b9aa-487a-8259-a2806810426f /. snapshots btrfs rw,relatime,ssd,space_cache=v2,subvolid=260,subvol=/@snapshots 0 0
# /dev/sda1
UUID=FCFE-9B1E /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
Last edited by masca (2024-06-24 06:51:43)
Offline
so you use BtrFS - can't help here
the "missing" id is the ESP - which not show up as it's not a uuid
Offline
Please don't paraphrase, https://bbs.archlinux.org/viewtopic.php?id=57855
Als please use [code][/code] tags, not markdown. Edit your post in this regard.
Have you check the installation integrity?
Can you provide a system journal?
https://wiki.archlinux.org/title/System … al_to_view and see the 1st link below on how to post that from the console.
Offline
So, I have managed (I think!) to chroot by doing:
cryptsetup luksOpen /dev/sda2 encrypted_partition
mount /dev/mapper/encrypted_partition /mnt
mount -o subvol=@ /dev/mapper/encrypted_partition /mnt
mount -o subvol=@home /dev/mapper/encrypted_partition /mnt/home
mount -o subvol=@pkg /dev/mapper/encrypted_partition /mnt/var/cache/pacman/log
mount -o subvol=@log /dev/mapper/encrypted_partition /mnt/var/log
Then,
mount -o subvol=@snapshots /dev/mapper/encrypted_partition /mnt/.snapshots
gives
mount: /mnt/. snapshots: fsconfig system call failed: No such file or directory. dmesg(1) may have more information after failed mount system call
I do
arch-chroot /mnt
anyway...
Then,
1. Running
LC_ALL=C pacman -Qkk --root=/mnt | grep -v ', 0 altered files'
yields
error: failed to initialize alpm library: (root: /mnt, dblayh: /mnt/var/lib/pacman/)
could not find or read directory
2. The same goes for
journalctl -D /mnt/var/log/journal -e
.
I get:
Failed to open/mnt/var/log/journal: No such file or directory
---
I have given up and reinstalled. It's certainly a malpractice but I have a looming deadline and didn't know what else to do
Last edited by masca (2024-06-24 09:44:17)
Offline
arch-chroot /mnt … LC_ALL=C pacman -Qkk --root=/mnt | grep -v ', 0 altered files'
It makes no sense to point towards another root when chrooted into that root - the command is meant to use the pacman version of the install iso in anticipation that the one on the installed system is not going to be useable.
Offline