Created attachment 13443 [details]
dracut report and debug report in archive

Howdy.  First, some context:

I have 4 machines on the LAN running up-to-date 64-bit Mageia for some years with few challenges.  Latest kernel update is normal for the following three:

2-are Wyze thin clients, one runs a webserver, the other mostly displays a surveillance camera.  Some properties:

[rolf@d90d7 ~]$ uname -r
5.15.74-desktop-1.mga8
[rolf@d90d7 ~]$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-5.15.74-desktop-1.mga8 root=UUID=f8166285-e50a-4d90-a6f1-9a3c29453ce8 ro verbose noiswmd noresume audit=0
[rolf@d90d7 ~]$ cat /etc/release
Mageia release 8 (Official) for x86_64

[rolf@d90d7 ~]$ uname -r
5.15.74-desktop-1.mga8
[rolf@d90d7 ~]$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-5.15.74-desktop-1.mga8 root=UUID=f8166285-e50a-4d90-a6f1-9a3c29453ce8 ro verbose noiswmd noresume audit=0
[rolf@d90d7 ~]$ cat /etc/release
Mageia release 8 (Official) for x86_64

The third is my primary workstation, ROG STRIX X570-I GAMING, Ryzen 7 5700G, etc:

[rolf@x570i ~]$ uname -r
5.15.74-desktop-1.mga8
[rolf@x570i ~]$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-5.15.74-desktop-1.mga8 root=UUID=392cbe8f-abfc-4dd9-b7d6-c8c21b6294fd ro verbose noiswmd resume=/dev/nvme0n1p2 audit=0 cx23885.debug=8
[rolf@x570i ~]$ cat /etc/release
Mageia release 8 (Official) for x86_64

I had this problem with my former workstation, Z170I PRO GAMING, Intel Core i5-6500, etc. necessarily booted to the previous kernel, which works:

[rolf@z170i boot]$ uname -r
5.15.65-desktop-1.mga8
[rolf@z170i boot]$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-5.15.65-desktop-1.mga8 root=UUID=eabf32a7-39a6-4e78-af5d-841e55d30069 ro splash quiet noiswmd audit=0 intel_idle.max_cstate=1
[rolf@z170i boot]$ cat /etc/release
Mageia release 8 (Official) for x86_64

Deeper background on this machine is that I recently used gparted to copy the OS partitions from an m.2 card in sata enclosure plus /var on little sata card plugged directly to sata connection on the motherboard then pasted to a single sata m.2, which now holds the OS.  I edited fstab that mounted on /dev/sd[a-b] to call on /dev/nvme???.  When that failed, I stumbled on booting an MGA8 installation key rescue session and "re-installing bootloader".  That was sufficient for the previous kernel.  Installing the new kernel resulted in a dracut shell advising, for example:
"dracut could not boot, /dev/sdb4 does not exist"
and that "rdsosreport.txt" had been written under /run, that I might want to copy it somewhere.  Also, there was the option of booting with the kernel command ~ "rd.debug" for more verbosity.  I collected both,  compressed xz archive attached, the debug is 2M.

While I was there, I mounted and chrooted into the filesystem to find that /boot/EFI partition refused to mount:
"wrong fs type, bad option, bad superblock, codepage not found". The fstab entry that boots with previous kernel:
UUID=3C14-DB71 /boot/EFI vfat defaults,umask=000 0 0
Booted to the older kernel, I used the MCC "setup boot" module to remove the "resume" directive, pointed to sdb4, previous mount point for swap.  It's not in  /proc/cmdline, anymore, but still shows up in rdsosreport.txt
I tried regenerating initrd:
[root@z170i boot]# dracut --force /boot/initrd-5.15.74-desktop-1.mga8.img 5.15.74-desktop-1.mga8
I believe the several subsequent configurings with "setup boot" in MCC would have run the bootloader installer.

In summation, the flag on sdb4 is distracting but the failure to mount /boot/EFI under the new kernel seems the more important problem to me.  Again, the fstab entry, above, works with 5.15.65-desktop-1.mga8
Thanks.