Description of problem: The kernel goes into panic on boot Version-Release number of selected component (if applicable): Mageia 5 RC kernel 3.19 How reproducible: Every boot. Steps to Reproduce: 1. Boot 2. 3. Pls. Note: On almost every other previous release the panic problem has been present - maybe it is NOT a kernel issue but an init issue ... Reproducible: Steps to Reproduce:
Please attach a screenshot of the kernel panic
Keywords: (none) => NEEDINFOCC: (none) => thierry.vignaudSource RPM: Mageia 5 RC => kernel, dracut
(In reply to Thierry Vignaud from comment #1) > Please attach a screenshot of the kernel panic How on earth do I do that the machine doesn't even boot ???
(In reply to René Lagoni Neukirch from comment #2) > (In reply to Thierry Vignaud from comment #1) > > Please attach a screenshot of the kernel panic > > How on earth do I do that the machine doesn't even boot ??? The panic is something like - VFS: Unable to mount root FS on unknown block (0,0)
(In reply to René Lagoni Neukirch from comment #3) > (In reply to René Lagoni Neukirch from comment #2) > > (In reply to Thierry Vignaud from comment #1) > > > Please attach a screenshot of the kernel panic > > > > How on earth do I do that the machine doesn't even boot ??? > > The panic is something like - VFS: Unable to mount root FS on unknown block > (0,0) FWIW: I did an upgrade from Mageia 4 til Mageia 5, i.e not a full installation from scratch.
(In reply to René Lagoni Neukirch from comment #2) > (In reply to Thierry Vignaud from comment #1) > > Please attach a screenshot of the kernel panic > > How on earth do I do that the machine doesn't even boot ??? Well, most people figure they can use a camera for that :)
Created attachment 6580 [details] "Screendump" Picture as requested ....
Probably a bogus bootloader config. What is your boot loader? lilo? grub? grub2?
Summary: Kernel Panic => Kernel Panic (VFS: unable to mount root fs on unknown-block(0,0)
(In reply to Thierry Vignaud from comment #7) > Probably a bogus bootloader config. > What is your boot loader? lilo? grub? grub2? Tried to reply to the mail, but it bounced ... GRUB2 FWIW - Tried on my other (and newer) platform - no problems whatsoever.
Can you use "e" in grub2 to look at kernel options?
Created attachment 6597 [details] The boot according to the e option. I did an upgrade twice from M4 to M5RC - one on my oldest platform and one on my youngest. The latter succeeded the first DID NOT. Both 64 bit, both with Grub2, both with kernel 3.19. The old platform still works with mga4 boot images.
(In reply to René Lagoni Neukirch from comment #10) > Created attachment 6597 [details] > The boot according to the e option. > > I did an upgrade twice from M4 to M5RC - one on my oldest platform and one > on my youngest. The latter succeeded the first DID NOT. > Both 64 bit, both with Grub2, both with kernel 3.19. > The old platform still works with mga4 boot images. I just did an update (from the mga5 medias ofcourse) among these a lot of drak... tools. Now even my older platform works fine.
Closing then. I think that could be a side effect of bug #15984 *** This bug has been marked as a duplicate of bug 15984 ***
Status: NEW => RESOLVEDResolution: (none) => DUPLICATE
I tried to boot my system from the final/released LiveCD Mageia-5-LiveCD-KDE4-en-i586-CD.iso and right at boot the kernel panic happenned with this message: "Kernel Panic (VFS: unable to mount root fs on unknown-block(0,0) " I have never had this problem with the live CDs of Mageia 3 and 4 on the same system. This means that this bug was not fixed for all the released ISOs.
CC: (none) => gamiro97
Reopening as per comment 13, and re-closing bug 15984.
Status: RESOLVED => REOPENEDResolution: DUPLICATE => (none)
Changing release version to 5, as per comment 13. Is there a plan to re-release the affected ISO(s)?
Version: Cauldron => 5
That's a different issue (first was a bogus bootloader configuration in _installed_ system whereas you're talking about booting live ISO) Please open a new bug report.
Status: REOPENED => RESOLVEDResolution: (none) => FIXED
Proper status *** This bug has been marked as a duplicate of bug 15984 ***
Resolution: FIXED => DUPLICATE