Description of problem: I used Mageia 5 kernel 4.1.8-1 mga5 on my home server. After upgrade to 4.1.12-1 mga 5, at boot, I receive the sequence : Could not find module by name='skge' Could not find module by name="forcedeth" Dracut Warning : Could not boot Dracut Warning : /dev/md0 does not exist Generating '/run/initranfs/rdsosreport.txt' You might want to save '/run/intranfs/rdsosreport.txt' to a usb stick or /boot After mounting then attach it to a bug report Reboot with 'rd.debug' added to the kernel command line Droping to debug shell dracut:/# ------- If I reboot and choose Server 4.1.8-1 mga 5 (the old kernel) the computer run fine. ------- I use /, /home and /var on Raid5 devices md0, md1 and md2 with a /boot part. What I can do to help you ? This problem is on 2 different computers. Regards Reproducible: Steps to Reproduce:
Hi, On a second server (HP Proliant) with a hardware RAID board, this problem is not present. Peharps a soft RAID problem ? Regards
The error message talks about a rdsosreport.txt error file. Could you attach it?
CC: (none) => zen25000Assignee: bugsquad => tmb
Source RPM: (none) => kernel-server
Mass-reassigning all bugs with "kernel" in the Source RPM field that are assigned to tmb, to the kernel packagers group, because tmb is currently MIA.
Assignee: tmb => kernel
I just updated mga5 on x86_64 host big31. Prior: kernel-desktop-latest-4.4.16-1.mga5-1-1.mga5 works normally. Current: kernel-desktop-latest-4.4.39-1.mga5-1-1.mga5 cannot find root device whether cmdline contains root=/dev/sda17 or root=LABEL=mga5hcs5, so drops so rescue shell, claiming /dev/disk/by-label/mga5hcs5 does not exist. In fact in rescue shell, /dev/d* does not exist. Host big31 has no storage devices except sda. Removing and reinstalling latest kernel didn't help, and neither did rebuilding initrd with hostonly="no".
CC: (none) => mrmazda
@ Yves, Thank you for having taken the needed time to report this issue! Did this bug get fixed? If so, please change its status to RESOLVED - FIXED If it didn't, then we regret that we weren't able to fix it in Mageia 5. Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/ It only continued to get important security updates since then, because we were waiting for the big Plasma5 update in Mageia 6, that fixed many of the Mageia 5 => 6 upgrade issues. If you haven't seen that this bug got fixed, then please check whether this bug still exists in Mageia 6. If it does, then please change the Version (near the top, at the left) to "6". If you know it exists in Cauldron, then change Version to Cauldron. If you see it in both Cauldron and Mageia 6, then please set Version to Cauldron and add MGA6TOO on the Whiteboard. ==> If you didn't reset your password after february 2018, then you'll need to reset it here https://identity.mageia.org/forgot_password to be able to log in and comment in this report. <==
CC: (none) => marja11
No reply, so closing as OLD since Mageia 5 is no longer maintained.
Status: NEW => RESOLVEDResolution: (none) => OLD
Hello, Admittedly, the bug is old but, passed to Mageia 6 has not changed anything and the problem is still there. you can see it at this address: https://lsdm.onlynux.org/awstats.lsdm.osdetail.html Have a good day, Yves
CC: (none) => yspecht
(In reply to Yves Specht from comment #7) > Hello, > > Admittedly, the bug is old but, passed to Mageia 6 has not changed anything > and the problem is still there. you can see it at this address: > > https://lsdm.onlynux.org/awstats.lsdm.osdetail.html > > Have a good day, > > Yves thx, reopening. I suppose our kernel maintainers understand how to read your statistics. I don't, and the http://www.awstats.org/ website is temporarily offline. How are the values & percentages related to Mageia's kernel-server not booting? GNU Linux (Unknown or unspecified distribution) 1 370 12.5 % 6 744 35.7 %
Resolution: OLD => (none)Summary: Mageia 5 Server 4.1.12-1 mga5 d'ont boot after update => Mageia 6 kernel-server doesn't boot after updateVersion: 5 => 6Status: RESOLVED => REOPENED
Sorry, but that is either a wrong pasted link or a try at a clickbait...
Status: REOPENED => RESOLVEDResolution: (none) => OLDCC: (none) => tmb