Cauldron: Format of /boot/initrd-....img not recognized

This forum is dedicated to testing early releases and cauldron : Howtos, tips, tricks and user global feedback and thoughts...

Helpful tip :
For bugs tracking we use : https://bugs.mageia.org = The Mageia Bug Tracker
In this bug tracker you'll find already reported bugs and you'll be able to report those you have found....

Cauldron: Format of /boot/initrd-....img not recognized

Postby NetAlien » Sep 11th, '24, 15:39

During Cauldron update this morning, got this twice:
Code: Select all
remove-boot-splash: Format of /boot/initrd-6.6.50-server-1.mga10.img not recognized

$ ll /boot/initrd-6.6.50-server-1.mga10.img
-rw------- 1 root root 39570464 Sep 11 09:18 /boot/initrd-6.6.50-server-1.mga10.img

$ sudo file /boot/initrd-6.6.50-server-1.mga10.img
/boot/initrd-6.6.50-server-1.mga10.img: ASCII cpio archive (SVR4 with no CRC)

$ mount /boot/initrd-6.6.50-server-1.mga10.img /mnt/img
mount: /mnt/img: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error.
       dmesg(1) may have more information after failed mount system call.

$ dmesg
[...]
[772993.777042] loop0: detected capacity change from 0 to 77286
[772993.778864] EXT4-fs (loop0): VFS: Can't find ext4 filesystem
[772993.778990] EXT4-fs (loop0): VFS: Can't find ext4 filesystem
[772993.779078] EXT2-fs (loop0): error: can't find an ext2 filesystem on dev loop0.
[772993.779564] ISOFS: Unable to identify CD-ROM format.
[772993.779733] REISERFS warning (device loop0): sh-2021 reiserfs_fill_super: can not find reiserfs on loop0
[772993.779785] FAT-fs (loop0): invalid media value (0x44)
[772993.779786] FAT-fs (loop0): Can't find a valid FAT filesystem
[772993.779803] hpfs: Bad magic ... probably not HPFS

$ cpio -tv < /boot/initrd-6.6.50-server-1.mga10.img
drwxr-xr-x   3 root     root            0 Sep 11 09:18 .
-rw-r--r--   1 root     root            2 Sep 11 09:18 early_cpio
drwxr-xr-x   3 root     root            0 Sep 11 09:18 kernel
drwxr-xr-x   3 root     root            0 Sep 11 09:18 kernel/x86
drwxr-xr-x   2 root     root            0 Sep 11 09:18 kernel/x86/microcode
-rw-r--r--   1 root     root       224256 Sep 11 09:18 kernel/x86/microcode/GenuineIntel.bin
440 blocks


I get the same error with or without '-o loop' on mount.

How dangerous is this?

added code tags ~Germ
NetAlien
 
Posts: 3
Joined: Aug 21st, '24, 15:20

Re: Cauldron: Format of /boot/initrd-....img not recognized

Postby doktor5000 » Sep 11th, '24, 17:48

There's a pretty old bug report about this: https://bugs.mageia.org/show_bug.cgi?id=19049
It can be ignored.
You could try to regenerate the initrd via dracut to see if that helps, as root:
Code: Select all
dracut -f
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 18039
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: Cauldron: Format of /boot/initrd-....img not recognized

Postby NetAlien » Sep 11th, '24, 18:19

Sorry if I'm being overly cautious; but this "error" is complaining about 6.6.50 which is next to boot vs currently running 6.6.43
Code: Select all
$ dracut -f
returned lots of "because command '...' could not be found!"
and finished with:
dracut: *** Creating image file '/boot/initrd-6.6.43-server-1.mga10.img' ***
dracut: dracut: using auto-determined compression method 'pigz'
dracut: *** Creating initramfs image file '/boot/initrd-6.6.43-server-1.mga10.img' done ***


which is the running now vs 6.6.50 which is on deck for the next reboot. initrd is critical to boot; hence my caution.
Last edited by doktor5000 on Sep 11th, '24, 18:51, edited 1 time in total.
Reason: added code tags
NetAlien
 
Posts: 3
Joined: Aug 21st, '24, 15:20

Re: Cauldron: Format of /boot/initrd-....img not recognized

Postby doktor5000 » Sep 11th, '24, 18:58

You shouldn't be running cauldron if you're overly cautious, see my signature. I don't even understand what you're so cautious about - it there's an issue, just select the previous kernel from the bootloader.
What will you do if there's an _actual_ issue and not only some informational message ?

For dracut you need to specify the initrd version if it's not matching the currently running kernel. See e.g. https://forums.mageia.org/en/viewtopic.php?f=8&t=6433 for an example.
Or use dracut --regenerate-all to regenerate all of them.
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 18039
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: Cauldron: Format of /boot/initrd-....img not recognized

Postby sturmvogel » Sep 12th, '24, 14:02

And regarding „missing modules“. That are status messages and absolute basics. Have a read here:
https://bugs.mageia.org/show_bug.cgi?id=31849#c3
sturmvogel
 
Posts: 738
Joined: Jul 30th, '12, 00:39


Return to Testing : Alpha, Beta, RC and Cauldron

Who is online

Users browsing this forum: No registered users and 1 guest

cron