upgrading from Debian 11 to 12 using apt installed new Kernel 6.1.0-25-amd64 and unlike in older 5.10.0-32-amd64 which works under both Deb. 11 & 12, the 6.x kernel does not work at boot of a Deb. 12 (11 is gone):
$ for i in $(locate autofs4); do ls -la $i; donecryptsetup: sd5_crypt: set up successfully
/dev/mapper/computer--vg-root: clean...
systemd[1]: Failed to look up module alias 'autofs4': function not implemented
[UNSUPP] Starting of Arbitrary Executable File Formats File System Automount Point not supported.
systemd[1]: Failed to start Load Kernel Modules
[FAILED] Failed to start Load Kernel Modules
[FAILED] Failed to start Install ZFS kernel module.
[DEPEND] Dependency failed for Import ZFS pools by cache file.
[FAILED] Failed to mount /boot/efi.
[DEPEND] Dependency failed for Local File Systems.
[FAILED] Failed to start netfilter persistent configuration.
Reached target network
...
You are in emergency mode.
$ sudo blkid|grep f...e-rw-r--r-- 1 root root 107499 Aug 10 08:09 /usr/lib/modules/5.10.0-32-amd64/kernel/fs/autofs/autofs4.ko
-rw-r--r-- 1 root root 109371 Aug 26 21:47 /usr/lib/modules/6.1.0-25-amd64/kernel/fs/autofs/autofs4.ko
my primary drive is sda, nvme* is a clone which has same UUID, I have tried to change the UUID if I remember correctly ( sudo cryptsetup luksUUID --uuid=newuuid /dev/sda5 ), but somehow it is back there after reboot, I am not 100% sure if i have really executed it and if it is correct to do it on a mounted partition 5./dev/nvme0n1p5: UUID="f...e" TYPE="crypto_LUKS" PARTUUID="***"
/dev/sda5: UUID="f...e" TYPE="crypto_LUKS" PARTUUID="***"
$ sudo dkms status└─sda5 8:5 0 111.3G 0 part
└─sdb5_crypt 253:0 0 111.3G 0 crypt
└─computer--vg-root 253:1 0 110.3G 0 lvm /
ZFS is NOT on system drive, but on external USB drive.zfs/2.1.11, 5.10.0-32-amd64, x86_64: installed
zfs/2.1.11, 6.1.0-25-amd64, x86_64: installed
inxi (pass: i )
grub.cfg boot entries and lsinitramfs .img content (zfs...)
Previously I had an issue with a cryptsetup source mismatch, where I have ran "sudo cryptsetup luksUUID --uuid=newuuid /dev/sda5 && sudo update-initramfs -u"
while the mentioned initramfs command shown only kernel 6 in its output, so I am wondering if the above mentioned boot issue may be related to the cryptsetup UUIDs, hopefully not.
Please kindly what to try/check to fix this?
Update: for some reason, next boot attempts are OK. I do not know why, some role may play new kernel *26 installation (received automatically during apt update).