SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I made a mistake and restarted the window manager when slackpkg upgrade-all was running.
My system has an (almost) full disk encryption setup and a volume group inside of it.
I already chrooted to the disk from other OS, but couldn't still solve the issue.
At the boot, initrd complains
LUKS device /dev/nvme0n1p2 unavailable for unlocking!
then consequent mount error:
mounting /dev/cryptvg/root on /mnt failed: no such file or directory.
At the the prompt, when running cryptsetup:
/lib64/libcrypto.so.3: version OPENSSL_3.2.0 not found (required by /usr/lib64/libcryptsetup.so.12).
Probably, it's still necessary to upgrade some packages, but slackpkg upgrade-all doesn't seem to find any to upgrade.
I've already deleted the contents of /var/log/packages.
Sounds to me like your upgrade was successful, but then you aborted the process by killing your X session. Probably the only thing you need to do is generate a working initrd.
Use that other OS to chroot into your installation and then run "geninitrd" as root. That should give you a working initrd.
And for future reference: NEVER run an OS upgrade while you are inside an X or Wayland session! Always switch to runlevel 3 (or 1) before starting your upgrade.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.