You are not logged in.
Pages: 1
Greetings,
I ran my usual pacman -Syuv this morning, and my laptop froze upgrading systemd. When I reboot, the system runs fsck on my root partition, gives me a warning about the root device not being configured to be mounted read-write, and then stops after the following:
:: mounting '/dev/nvme0n1p4' on real root
:: running cleanup hook [udev]
Don't panic. I booted from USB, connected to the internet, mounted my root and boot file systems on /mnt, and arch-chroot'd into /mnt.
/var/log/pacman.log shows that I started a full upgrade this morning, and then is padded with NULs.
But when I try to run pacman (with or without parameters), I get this:
# pacman
pacman: error while loading shared libraries: /usr/lib/libcrypto.so.3: file too short
And sure enough, /usr/lib/libcrypto.so.3 is an empty file. The timestamp is April 28 at 02:40; my local timezone is US/Eastern (-0400).
I can try to re-install pacman (https://wiki.archlinux.org/title/Pacman … ing_pacman), but I'm concerned about /usr/lib/libcrypto.so.3.
How can I restore my system? What else I can tell you?
Yes, had a similar pacman failure about a month ago, and yes, I have been rebooting after pacman updates that include new kernels. :-)
Thanks,
Dan
Last edited by segment289 (2024-05-01 16:06:15)
Offline
Further poking around shows that many .so files under /usr/lib/ are empty. Looks like a lot of them are libboost files, and at least some of them are libsystemd files (I point that out because that's where my original upgrade failed).
Offline
Offline
After re-installing all the packages, I can boot, log in, and bring up my DIY X11 desktop!
Thanks, seth. You and Arch are amazing. :-)
Offline
Pages: 1