Description of problem: after successful install of mageia 3 beta 1 without any issue on a pair of new 500 Gio disks with soft RAID it was impossible to boot the system. Version-Release number of selected component (if applicable): Mageia 3 beta 1 How reproducible: Install proposed to activate soft RAID. Answered Yes. On boot from RAID disk the system aborts with dracut Warning : Cancelling resume operation device not found dracut Warning : Could not boot dracut Warning : /dev/mapper/isw-bbigficcd-Volume0p1 does not exist Dropping to debug shell However I could checked that all necessary RAID devices had been actually created : mapper/isw-bbigficcd-Volume0p1 is 12 Gio (2%) mapper/isw-bbigficcd-Volume0p5 swap is 3.8 Gio mapper/isw-bbigficcd-Volume0p6 is 449 Gio (96%) I suspect there is a bug in proper device route for booting ? Regards from Bernard f6bvp
CC: (none) => mageia, thierry.vignaud
Are you sure the files are actually *exactly* what's expected? Bug #6180 is about the mapper devices being created without the 'p' near the end.
CC: (none) => dan
I tried a new install using Mageia 3 beta3 version, selecting again soft RAID option and rebuilding default partitions. However, boot aborts after a while, with same dracut Warnings. Warning message is : dracut Warning : Cancelling resume operation. Device not found dracut Warning : Could not boot dracut Warning : /dev/mapper/isw-bbigficcd-Volume0p1 does not exist dracut Warning : /dev/mapper/isw-bbigficcd-Volume0p1 does not exist dracut Warning : /dev/mapper/isw-bbigficcd-Volume0p5 does not exist looking into /dev/mapper/ I see nothing exept an entry named control Booting rescue option from DVD I mounted disks partions on /mnt and could look at etc/fstab where are the following entries: /dev/mapper/isw-bbigficcd-Volume0p1 / ext4 acl, relatime 1 1 /dev/mapper/isw-bbigficcd-Volume0p6 /home ext4 acl, relatime 1 2 /dev/mapper/isw-bbigficcd-Volume0p5 swap swap default 0 0 Sorry that I did not found how to mount USB memory stick and write onto it the complete report written with kernel option rd.debug Any suggestion to help me go further and help debugging this soft RAID boot failure.
I am glad I found how to mount USB stick and saved file report.bug.xz that I will attach here. Notice that I probably misspelled above file names transcripted manually : '-' signs were actually '_' characters.
Created attachment 3629 [details] This is bug report file for RAID boot failure
Changing version, it will be great to test if mga4 state is better (and add back to cauldron if it's still valid).
Version: Cauldron => 3
Actually Mageia4 beta1 or upcoming beta2 should handle raid much better
Mageia 3 changed to end-of-life (EOL) status 4 months ago. http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => OLD