Bug 30353 - keep getting message: Format of /boot/initrd-x.y.z-desktop-n.mga8.img not recognized when installing new kernel
Summary: keep getting message: Format of /boot/initrd-x.y.z-desktop-n.mga8.img not rec...
Status: RESOLVED DUPLICATE of bug 19049
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 8
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Kernel and Drivers maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-04-30 06:23 CEST by w unruh
Modified: 2022-04-30 22:07 CEST (History)
3 users (show)

See Also:
Source RPM: bootsplash
CVE:
Status comment:


Attachments

Description w unruh 2022-04-30 06:23:05 CEST
Description of problem:
I upgrade the system including installing a new kernel. dracut is run on the new kernel, and I consistantly get the error message
Format of /boot/initrd-5.15.35-desktop-2.mga8.img not recognized
(where the kernel version changes from one time to the next. )
Everything seems to proceed as usual, and dracut seems to create a new initrd for the kernels. This error message is worrying, but does not seem to mean anything, or am I being lulled into indifference?

This has been going on for a number of years now. If it is an inconsequential error message, perhaps it should not be generated.
Comment 1 Lewis Smith 2022-04-30 08:53:07 CEST
Thank you for this report.

Only tmb can comment on it, so assigning appropriately.

Summary: keep getting message: Format of /boot/initrd-5.15.35-desktop-2.mga8.img not recognized when installing new kernel => keep getting message: Format of /boot/initrd-x.y.z-desktop-n.mga8.img not recognized when installing new kernel
Assignee: bugsquad => kernel

Comment 2 Lewis Smith 2022-04-30 20:43:16 CEST
New bug 30355 is grossly similar, with the suggestion that this could be a Grub2 issue. The two bugs might be duplicates.

Bill, can you confirm whether you use Grub2?

CC: (none) => lewyssmith

Comment 3 Thomas Backlund 2022-04-30 20:56:39 CEST
it's the bootsplash script that complains... 
I guess we could atleast silence it

Source RPM: kernel xxx => bootsplash

Comment 4 w unruh 2022-04-30 21:01:54 CEST
Yes, I do use grub2.
grub2-2.06-1.1.mga8
It has been this way for a while now. I do not remember exactly when as I usually
simply ignored it, and it did not seem to do anything bad, but on the latest 
update I finally decided it was worth reporting it. Must have been something in 
the global air for the two of us to report within 4 hrs of each other!
GG HH 2022-04-30 21:03:26 CEST

CC: (none) => boulshet

Comment 5 w unruh 2022-04-30 21:10:08 CEST
Also as I recall I have gotten this on a number of different machines, so it would seem to be a generic software problem. 
Next time I update the kernel I will try to grab the message itself.
Comment 6 w unruh 2022-04-30 21:37:33 CEST
Here is the message on one machine I just installed.
Creating: target|kernel|dracut args|basicmodules 
/etc/dracut.conf.d/51-mageia-resume.conf:add_device+="/dev/nvme0n1p5"
remove-boot-splash: Format of /boot/initrd-5.15.35-desktop-2.mga8.img not recognized

Also another message

/etc/dracut.conf.d/51-mageia-resume.conf:add_device+="/dev/nvme0n1p5"

dracut: WARNING: <key>+=" <values> ": <values> should have surrounding white spaces!
dracut: WARNING: This will lead to unwanted side effects! Please fix the configuration file.

Maybe this is the problem in /etc/dracut.conf.d/51-mageia-resume.conf

I assume this file is automatically generated, and whatever is generating it is buggy. 
(I do not have any idea what the "unwanted side effects" are )
But this does seem to be a valid "Format unrecognized" type of error
Comment 7 GG HH 2022-04-30 21:50:53 CEST
on my side, i do have spaces
$ cat /etc/dracut.conf.d/51-mageia-resume.conf 
add_device+=" UUID=854bbb02-4a9a-4076-9bb1-abbd69817e34 "
Comment 8 w unruh 2022-04-30 21:55:57 CEST
The only place I find it is
>grep -r 51-mageia-resume.conf /lib*
/lib/libDrakX/any.pm:       output("$::prefix/etc/dracut.conf.d/51-mageia-resume.conf", qq(add_device+=" $biggest_swap_dev "\n));

but the whitespace seems to be there, unless perl stips it out.
Comment 9 GG HH 2022-04-30 22:03:17 CEST
It was probably introduced in your config file before drakxtools-backend was fixed in 18.40-1.mga8 (january 2021)
https://bugs.mageia.org/show_bug.cgi?id=28055
Comment 10 Marja Van Waes 2022-04-30 22:07:36 CEST
Duplicate

*** This bug has been marked as a duplicate of bug 19049 ***

Status: NEW => RESOLVED
Resolution: (none) => DUPLICATE
CC: (none) => marja11


Note You need to log in before you can comment on or make changes to this bug.