Description of problem: x86_64 UEFI install on system with lots of disks, installation to RAID0, volume1P3, has working M7 on Volume1P2. Apparently successful installation, install recognised the RAID. Boot failed: dracut Warning: /dev/disk/by-uuid/62dbc600-3e19-4000-0007-ff0ec9271ddf does not exist dracut warning: /dev/mapper/isw-bdjgiebedg-Volume1p1 does not exist. My comment: Volume1p1 is the EFI partition, which M7 on that machine uses happily. When, from the emergency # prompt, I look in /dev/mapper, it contains control and isw-bdjgiebedg-Volume1, but not volume1p1, volume1p2, volume1p3 as I would expect. Sorry couldn't dump the rdsosreport.txt file as I couldn't mount an inserted memory stick to dump it to; mount failed with FAT-fs (sdl1): codepage cp437 not found So, the install proceeds apparently normally, installing itself to Volume1p3 as intended (installation files are readable there from subsequent boot of the prior M7 installation on Volume1p2). The setup of /dev/mapper appears to be in error however, so boot fails Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3.
Whiteboard: (none) => m8alpha1
Thanks for the report, Tony. Quite unsure where to push this sort of bug, of which we are going to get plenty in the near future. Starting with kernel & tv; please say where might be better. I am leaving myself CC'd to find out.
Assignee: bugsquad => kernelCC: (none) => lewyssmith, thierry.vignaud
Do you have a non-RAID disk in the system. If so, you could try mounting a partition on that disk and copying the rdsosreport.txt file there. Otherwise, try a USB stick with an ext2 filesystem. Also, please attach the /root/drakx/report.bug.xz from the mga8 system, and the log file generated by lsinitrd ./initrd.img > ls-initrd.log when run (as root) in /boot of the mga8 system.
Keywords: (none) => NEEDINFOCC: (none) => mageia
Thanks for jumping on it, Martin. Removing my own CC.
CC: lewyssmith => (none)
No need for the info - I've reproduced the fault and identified the upstream change in dracut that is causing it.
Component: Installer => RPM PackagesSource RPM: (none) => dracut-050-1.mga8Priority: Normal => release_blockerKeywords: NEEDINFO => (none)Assignee: kernel => mageia
Fixed in dracut-050-2.mga8. To get your current system to boot, when dracut drops to the debug shell, enter the command kpartx -a /dev/mapper/isw-bdjgiebedg-Volume1 then exit the shell. If that works, install the updated dracut package and then run dracut -f to rebuild the initrd image. The next boot should complete without error.
Status: NEW => RESOLVEDResolution: (none) => FIXED
CC: (none) => davidwhodgins