Another Monday... Did the updates from the weekend and now can't boot. Getting
"Failed to open encryption mapping: The device UUID=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX is not a LUKS volume and the crypto= parameter was not specified"
Trying to manually mount the partitions at the emergency shell results in:
cryptsetup: error while loading shared libraries: libjson-c.so.3
I can mount the partitions just fine from Artix Live USB but I'm out of my depth and don't know how to recover from this one.
Nothing else was done except run the updates from this weekend using pacman instead of pamac like I usually do.
Any suggestions?
Ok update on this. Not sure if it's due to libjson or not. Steps I followed to get my machine to boot back up.
1) Boot into Artix Live USB
2) (was lazy and used partitionmanager) to "decrypt" the drives (/ and swap)
3) mkdir /mnt/HD
4) mount /dev/mapper/luks-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX (luks partition for /)
5) mount /dev/sda1 /mnt/HD/boot/efi
6) artools-chroot /mnt/HD /bin/bash
7) downgrade json by running pacman -U /var/cache/pacman/pkg/json-c-0.13-1.x86_64.pkg.tar.gz
8 ) mkinitcpio -p linux-lts
At this point I'm not 100% sure if it was the json downgrade or re-running mkinitcpio that fixed it. I'd back out the json change to test but silly me uses this system as my production system and already lost an hour and 38 minutes fixing it so I can't test right now but if anyone else runs into the same issue they can report it here.
It is the json-c update. Apologies, we have a bug in our buildtree script that is gonna be fixed.
Essentially, json-c went too early in the repos.
Thanks artoo. I probably should be testing updates in a VM first anyway until we're stable. Appreciate the update.
json-c should not have gone in core repo.
I added cryptsetup and syslog-ng rebuilds, so it should be working again with new json-c version.
Looks like we're good man. Built a new VM with similar setup to the host (minus Nvidia, etc) and processed all updates and it comes up fine.