Can't boot in 5.3.18-2-pve image

I've got exactly the same problem. Kernel 5.3.18-1-pve (and older) works perfectly fine. Switching into 5.3.18-2-pve causes Kernel panic. Rebuilding initrd doesn't help.
 
can you please analyze the initrd-image the way the OP did - and also run the strings command and debsums?
 
Hi. All sums are correct. The command:
Code: 
# debsums pve-kernel-5.3.18-2-pve | grep -v OK
#
gives no output.

Code: 
# strings etc/ld.so.cache
ld.so-1.7.0
glibc-ld.so.cache1.1&
libzstd.so.1
/lib/x86_64-linux-gnu/libzstd.so.1
libzpool.so.2
/lib/libzpool.so.2
libzfs_core.so.1
/lib/libzfs_core.so.1
libzfs.so.2
/lib/libzfs.so.2
libz.so.1
/lib/x86_64-linux-gnu/libz.so.1
libuutil.so.1
/lib/libuutil.so.1
libuuid.so.1
/lib/x86_64-linux-gnu/libuuid.so.1
libudev.so.1
/lib/x86_64-linux-gnu/libudev.so.1
libtinfo.so.6
/lib/x86_64-linux-gnu/libtinfo.so.6
libsystemd.so.0
/lib/x86_64-linux-gnu/libsystemd.so.0
libstdc++.so.6
/lib/x86_64-linux-gnu/libstdc++.so.6
libssl.so.1.1
/lib/x86_64-linux-gnu/libssl.so.1.1
libselinux.so.1
/lib/x86_64-linux-gnu/libselinux.so.1
librt.so.1
/lib/x86_64-linux-gnu/librt.so.1
libresolv.so.2
/lib/x86_64-linux-gnu/libresolv.so.2
libreadline.so.5
/lib/x86_64-linux-gnu/libreadline.so.5
libpthread.so.0
/lib/x86_64-linux-gnu/libpthread.so.0
libpcre.so.3
/lib/x86_64-linux-gnu/libpcre.so.3
libnvpair.so.1
/lib/libnvpair.so.1
libm.so.6
/lib/x86_64-linux-gnu/libm.so.6
liblz4.so.1
/lib/x86_64-linux-gnu/liblz4.so.1
liblzo2.so.2
/lib/x86_64-linux-gnu/liblzo2.so.2
liblzma.so.5
/lib/x86_64-linux-gnu/liblzma.so.5
libkmod.so.2
/lib/x86_64-linux-gnu/libkmod.so.2
libgpg-error.so.0
/lib/x86_64-linux-gnu/libgpg-error.so.0
libgcrypt.so.20
/lib/x86_64-linux-gnu/libgcrypt.so.20
libgcc_s.so.1
/lib/x86_64-linux-gnu/libgcc_s.so.1
libexpat.so.1
/lib/x86_64-linux-gnu/libexpat.so.1
libdl.so.2
/lib/x86_64-linux-gnu/libdl.so.2
libdevmapper.so.1.02.1
/lib/x86_64-linux-gnu/libdevmapper.so.1.02.1
libdevmapper-event.so.1.02.1
/lib/x86_64-linux-gnu/libdevmapper-event.so.1.02.1
libcrypto.so.1.1
/lib/x86_64-linux-gnu/libcrypto.so.1.1
libc.so.6
/lib/x86_64-linux-gnu/libc.so.6
libblkid.so.1
/lib/x86_64-linux-gnu/libblkid.so.1
libattr.so.1
/lib/x86_64-linux-gnu/libattr.so.1
libaio.so.1
/lib/x86_64-linux-gnu/libaio.so.1
libacl.so.1
/lib/x86_64-linux-gnu/libacl.so.1
ld-linux-x86-64.so.2
/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2

The sum of ld.so.cache from initrd:
Code: 
# md5sum etc/ld.so.cache
2a3551da270b60b53703a0266372291a  etc/ld.so.cache
Which seems to be the same as in https://forum.proxmox.com/threads/cant-boot-in-5-3-18-2-pve-image.65997/post-297495.
 
hmm - just on a hunch - try booting with 'init=/bin/sh' on the kernel commandline (you need to edit it in the bootloader)
if you get a working shell - try executing '/init' and see whether the source of the issue becomes more clear
 
This is my production server and I can't reboot it and play with kernel parameters, sorry. So I'd rather stay with 5.3.18-1-pve kernel.
 
Hi, I have exactly the same problem.
I updated from 5.3.18-1 to 5.3.18-2 and I now get pve-group not found.
I can still boot to 5.3.18-1.
 
You must log in or register to reply here.
Top Bottom