stuck at boot after upgrade to 24.4 noble numbat lts

[Fred-VIE]

After the update it wont boot anymore. The Kubuntu sign shows and that is it. Not even the repair mode works, it just stops after detecting some USB device.

What options do I have now?

[skyfishgoo]

you should be able to get to the grub menu still, correct?

hit "E" to edit the kernel call command and remove the word "splash" from the sting inside the quotes.

they hit F10 to try booting with that

if it works you will need to update right away or modify your grub file to remove it and update grub.

[Fred-VIE]

No luck. Boot stopped saying:

/sbin/init: error while loading shared libraries: libcrypto.so.3: cannot open shared object file: no such file or directory. Kernel panic - not synced. Attempted to kill init! Exitcode = 0x00007F0. CPU 2 pid: 1comm: init tainted P OE 5.15.0-131-generic #141-ubuntu

[Fred-VIE]

Is there no way to repair it from an USB-IMAGE or install the latest kernel again from that 24.04 image to the installation on the drive?

edit:

I have found following: booting from USB stick, bind-mounting and running an apt dist-upgrade in chroot fixed the install

Maybe anyone can tell me what to do to fix it like that? I have a boot-stick but I dont know what bind-mounting and chroot is or howto use it properly.

I have investigated further and wonder if it could be as as simple as

mount -B sdc5
sudo chroot $HOME –userspec=USER:GROUP (I know the user but I am not sure about the group. Is it the PC name that is shown in Kubuntu?)
sudo do-release-upgrade

? I am not sure what the root is to make updates to. This is probably too simple but from what I read one usually creates a special chroot environment in the home folder. Since I want no special environment but rather my Kubuntu installation instead this could be it. But since Linux is usually much more complicated than that some confirmation would be useful.
end of last edit

It seems like I have installed a developer version because I relied on the konsole update command from a website while searching "kubuntu kernel update konsole command" after it failed to update with the app that popped on every system start. I do not know why a normal guide to update to the latest kernel would suggest a dev-version but it seems thats where I am at this point. I was just using it because the command was just a push of a key button away to try it again, after it failed before.

I searched the command again and If I remember correctly the konsole command was

sudo do-release-upgrade -d

and I did not know what the -d stands for (I never knew with any console command what those letters after the minus meant tbh.) Someone told me that it supposedly stands for developer version and that is why I am having problems.

I have found the libcrypto.so.3 file in several paths:

/usr/lib/i386-linux-gnu/
/var/lib/flatpak/runtime/org.freedesktop.Platform.Compat.i386/x86_64/23.08/268dba3d13a468fea0102b162915784536df0877a6ebca2667 bf440aa0a7bea1/files/
/var/lib/flatpak/runtime/org.gnome.Platform/x86_64/46/188683dc86d530dd1547f14ee37dec1ac6e091c8455d6fbc3a 166f600fe6bea4/files/lib/x86_64-linux-gnu/
/var/lib/flatpak/runtime/org.freedesktop.Platform/x86_64/23.08/f35d1c6a3c62675d2c546601f48d65c8936b3f12ff84396e9b 6b21d0d749694d/files/lib/x86_64-linux-gnu/
/var/lib/flatpak/runtime/org.gnome.Platform/x86_64/47/400c051d7bdf97ecb22db051f1a0eddde33bd145bae97c2489 cc4dcf801d1ed3/files/lib/x86_64-linux-gnu/
home/accountname/.local/share/flatpak/runtime/org.freedesktop.Platform/x86_64/24.08/50874f35da7c9371a5f8e53384b2ae4fb0ab1ae2a461f5e964 639dbc81f3aa01/files/lib/x86_64-linux-gnu/
/home/accountname/.local/share/flatpak/runtime/org.gnome.Platform/x86_64/47/400c051d7bdf97ecb22db051f1a0eddde33bd145bae97c2489 cc4dcf801d1ed3/files/lib/x86_64-linux-gnu
/home/accountname/.local/share/flatpak/runtime/org.gnome.Platform/x86_64/46/188683dc86d530dd1547f14ee37dec1ac6e091c8455d6fbc3a 166f600fe6bea4/files/lib/x86_64-linux-gnu/

I cannot enter the console with ctrl+alt+f-buttons (tried all of them) when the boot stops.
I cannot enter any recovery console from the boot menu because boot stops while/after loading some usb-device.

[Qqmike]

I'm not sure about all the specific details of your case (e.g., dev version vs ?, etc.).

Just a couple things to help:

did not know what the -d stands for

Run the "manual" command, man:
man <name of the command you are using>
Ex.:
man do-release-upgrade
(then press Enter, of course)

bind-mounting and chroot

There are how-to's on it, including my how-to (here at Kubuntu KFN How-To section).
However ... sometimes it is better, faster to just use (the expert program) Boot-Repair (which does all that stuff for you):

https://help.ubuntu.com/community/Boot-Repair

[Fred-VIE]

I found several howto's but none really for my case. Thats the thing. so much info, and half of it is harmful and outdated.

Boot repair output: https://paste.ubuntu.com/p/c3Tqp7StKN/

I did not try to repair anything because it seems just to repair the boot manager which I do not have problems with and it could break my setup:
-Win drive
- Kubuntu drive
- Manjaro drive
- 2 NVMe's one with Linux format, one NTFS

Atm. I cannot try the man command because I do not get into Kubuntu, except for the boot-stick.

What I have mentioned though, that it still showed Kubuntu 22.04 when I started from the boot repair-stick and checked all the options where you get to choose the main boot OS Kubuntu was not mentioned as 24.04. The boot repair output confirms that.

Searching for my problem I found this. Could this work even though it was used on xubuntu?

Boot live cd and configure network
mount / folder on live cd (root disk)
On root disk, cd “root disk”
rm dev/null
cp /etc/resolv.cnf etc/resolv.cnf
sudo chroot . /bin/bash -c “apt --fix-broken install”

After all updates are done, reboot shall work.

Log in and execute:

sudo apt update
sudo apt dist-upgrade

Because this does not mention to mount the OS-installation-disk it sounds weird to me. I wonder how the chroot command can fix a broken install without knowing the target drive?