Description of problem: Hello. I couldn't boot with initrd generated with the ltest kernel update. The initrd image is nearly 20% smaller than before. Version-Release number of selected component (if applicable): 015-2.mga2 How reproducible: not sure Additional info: I have 2 harddrives with software raid (mdadm). It might be related ...
I tried to install the mkinitrd package and generate the initrd with mkinitrd-mkinitrd ... the result was surprising ... maybe it doesn't like the xz compression? # mkinitrd-mkinitrd -f /boot/initrd-3.2.6-desktop-2.mga2.img 3.2.6-desktop-2.mga2 /usr/bin/strip:/lib/modules/3.2.6-desktop-2.mga2/kernel/drivers/ata/ahci.ko.xz: File format not recognized /usr/bin/strip:/lib/modules/3.2.6-desktop-2.mga2/kernel/drivers/ata/ata_piix.ko.xz: File format not recognized /usr/bin/strip:/lib/modules/3.2.6-desktop-2.mga2/kernel/lib/crc-t10dif.ko.xz: File format not recognized /usr/bin/strip:/lib/modules/3.2.6-desktop-2.mga2/kernel/lib/crc16.ko.xz: File format not recognized /usr/bin/strip:/lib/modules/3.2.6-desktop-2.mga2/kernel/drivers/usb/host/ehci-hcd.ko.xz: File format not recognized /usr/bin/strip:/lib/modules/3.2.6-desktop-2.mga2/kernel/fs/ext4/ext4.ko.xz: File format not recognized /usr/bin/strip:/lib/modules/3.2.6-desktop-2.mga2/kernel/drivers/hid/hid.ko.xz: File format not recognized /usr/bin/strip:/lib/modules/3.2.6-desktop-2.mga2/kernel/fs/jbd2/jbd2.ko.xz: File format not recognized /usr/bin/strip:/lib/modules/3.2.6-desktop-2.mga2/kernel/drivers/ata/libahci.ko.xz: File format not recognized /usr/bin/strip:/lib/modules/3.2.6-desktop-2.mga2/kernel/drivers/ata/libata.ko.xz: File format not recognized /usr/bin/strip:/lib/modules/3.2.6-desktop-2.mga2/kernel/drivers/usb/host/ohci-hcd.ko.xz: File format not recognized /usr/bin/strip:/lib/modules/3.2.6-desktop-2.mga2/kernel/drivers/ata/pata_jmicron.ko.xz: File format not recognized /usr/bin/strip:/lib/modules/3.2.6-desktop-2.mga2/kernel/drivers/md/raid1.ko.xz: File format not recognized /usr/bin/strip:/lib/modules/3.2.6-desktop-2.mga2/kernel/drivers/scsi/scsi_mod.ko.xz: File format not recognized /usr/bin/strip:/lib/modules/3.2.6-desktop-2.mga2/kernel/drivers/scsi/sd_mod.ko.xz: File format not recognized /usr/bin/strip:/lib/modules/3.2.6-desktop-2.mga2/kernel/drivers/usb/host/uhci-hcd.ko.xz: File format not recognized /usr/bin/strip:/lib/modules/3.2.6-desktop-2.mga2/kernel/drivers/usb/usb-common.ko.xz: File format not recognized /usr/bin/strip:/lib/modules/3.2.6-desktop-2.mga2/kernel/drivers/usb/core/usbcore.ko.xz: File format not recognized /usr/bin/strip:/lib/modules/3.2.6-desktop-2.mga2/kernel/drivers/hid/usbhid/usbhid.ko.xz: File format not recognized /usr/bin/strip:/lib/modules/3.2.6-desktop-2.mga2/kernel/drivers/acpi/button.ko.xz: File format not recognized /usr/bin/strip:/lib/modules/3.2.6-desktop-2.mga2/kernel/drivers/gpu/drm/drm.ko.xz: File format not recognized /usr/bin/strip:/lib/modules/3.2.6-desktop-2.mga2/kernel/drivers/gpu/drm/drm_kms_helper.ko.xz: File format not recognized /usr/bin/strip:/lib/modules/3.2.6-desktop-2.mga2/kernel/drivers/i2c/algos/i2c-algo-bit.ko.xz: File format not recognized /usr/bin/strip:/lib/modules/3.2.6-desktop-2.mga2/kernel/drivers/i2c/i2c-core.ko.xz: File format not recognized /usr/bin/strip:/lib/modules/3.2.6-desktop-2.mga2/kernel/drivers/platform/x86/mxm-wmi.ko.xz: File format not recognized /usr/bin/strip:/lib/modules/3.2.6-desktop-2.mga2/kernel/drivers/gpu/drm/nouveau/nouveau.ko.xz: File format not recognized /usr/bin/strip:/lib/modules/3.2.6-desktop-2.mga2/kernel/drivers/gpu/drm/ttm/ttm.ko.xz: File format not recognized /usr/bin/strip:/lib/modules/3.2.6-desktop-2.mga2/kernel/drivers/acpi/video.ko.xz: File format not recognized /usr/bin/strip:/lib/modules/3.2.6-desktop-2.mga2/kernel/drivers/platform/x86/wmi.ko.xz: File format not recognized
(there is also a bug in the mageia-dev ml) Assigned to the package maintainer. (Please set the status to 'assigned' if you are working on it)
Keywords: (none) => TriagedCC: (none) => tmbBlocks: (none) => 4298Assignee: bugsquad => mageia
Yes, mkinitrd needs to be fixed for xz modules. does dracut work ?
Can you try with dracut-015-3.mga2? I think the lvm/dm stuff was not properly detected, but hopefully now it will be.
Status: NEW => ASSIGNED
I get the same with dracut-016-1. when rebuilding the init with dracut I get many errors like: E: FATAL:Could not load /lib/modules/3.2.6-desktop-2.mga2/modules.dep: no such file or directory followed by find: `/lib/modules/3.2.6-desktop-2.mga2/': no such file or directory Hope that helps.
CC: (none) => malo
Looks like the same problem as #4541, but everyone there seems to have been able to regenerate the initrd OK. Have you definitely regenerated the initrd with 016 installed?
Created attachment 1580 [details] dracut-issue screenshot Hello Colin. In my case the problem persists even with dracut 016 ... and YES, I have regenerated the mkinitrd with dracut 016 (using the force option). The file is still nearly 20% smaller and the attached screenshot demonstrates the issue ... Regards, Jaromir.
OK, that's kinda reassuring as I couldn't really see any fix for this issue in the commit log. I guess now the problem is going to be narrowing down exactly what is happening. I can only really see two fundamental paths for the fault. Either 1. The files are copied and then subsequently removed again. 2. The files are never copied in the first place. As you seem to be able to reliably reproduce the issue, are you able to do some bisecting with git to determine where the problem crept in? Either that or are you able to provide me with (temporary) SSH access to your machine so I can do the tests? If you do bisect, use the following git repository and branch: http://colin.guthr.ie/git/dracut/log/?h=mga-016 But it's also worth trying with "master" too just in case it's one of my own patches that is to blame. To generate an initrd from git just do: sudo ./dracut -f foo.img -l -c /etc/dracut.conf --confdir /etc/dracut.conf.d Then you can inspect foo.img with 'lsinitrd foo.img | grep " bin/"' to see if the same problem is present... this should provide a whole lot more than just plymouth.... Also feel free to grab me on IRC on freenode in #magiea-dev.
Also even if you do not do this git stuff, can you attach a log of an initrd generated with the --debug option? It'll produce a LOT of output :)
Ok ... I'll do that in the evening.
Here is the --debug output for me. http://www.doc.ic.ac.uk/~malo/dracut.log
(In reply to comment #11) > Here is the --debug output for me. Thanks for that. It appears to show copying of the required binaries quite happily which is very confusing. I presume you can confirm that e.g. "umount" is not in your initrd? Are you able to use git to bisect the issue and/or provide SSH access temporarily so I can debug the issue? If so, please let me know on IRC (coling in #mageia-dev on freenode)
The core issue with this bug is the same as the one reported in another bug (newer than this one but it has more comments so I'll do the marking this way round). I'm pretty sure I've seen this bug once in the wild personally, but it does only seem to happen during kernel install, never when running dracut manually. It's likely some race condition relating to the bootsplash initrd regeneration. It's arguably something we should factor out as at kernel install time it's totally wasteful and redundant. *** This bug has been marked as a duplicate of bug 4541 ***
Status: ASSIGNED => RESOLVEDResolution: (none) => DUPLICATE
Hello Colin. Since dracut-017 I don't experience the 'missing mdadm' issue anymore. I just forgot to tell you ... Sorry. Jaromir.