Seen this for years, so no news, but good logs this time, i hope. This bug probably share roots with Bug 22059, Bug 15262, and possibly more. In short i installed Mageia 6, and during partitioning step i changed my mind, so removed and again added partitions. After reboot i got dracut Warning: Could not boot. dracut Warning: /dev/disk/by-uuid/ <long ID here> does not exist Recognising this problem, i ran the installer again, this time in the installer i simply reused all partitions, i just set the mount points (after having unlocked the encrypted LVM). I think i chosed to format the disks just to be sure, and installed less packages (no Plasma) the second time. And i did grab logs :) File from "bug" command after final step of install *both* times, and the rdsosreport.txt from the failed boot. For clarity, this is the partitioning: EFI Boot /boot, ext4 Encrypted pv for LVM, containing /, ext4 /home, ext4 swap Machine is acer Aspire 7, A717-71G, Disk is NVMe 256GB Install and boot in UEFI mode with security turned off, quirk details in ( https://bugs.mageia.org/show_bug.cgi?id=22552#c20 )
Created attachment 9988 [details] report.bug from install that fail booting with wrong disk UUID
Created attachment 9989 [details] rdsosreport.txt from the boot, disk UUID problem
Created attachment 9990 [details] report.bug from the successful reinstall reusing partitions
Installer: Mageia 6 x86_64 DVD .iso on USB stick. Adding CC from related bug 22059
Source RPM: (none) => drakx-installer-stage2CC: (none) => marja11, pterjan, thierry.vignaud
Assignee: bugsquad => mageiatools
Is this still valid in Mageia
CC: (none) => ouaurelien
Mageia 6 changed to end-of-life (EOL) status on 2019-09-30. It is no longer maintained, which means that it will not receive any further security or bug fix updates. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 6's end of life. If you are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/ Best regards, Aurélien Bugsquad Team
Status: NEW => RESOLVEDResolution: (none) => OLD
Should be tested. Myself have very little time.
Need some testing here.
Ever confirmed: 1 => 0Status: RESOLVED => UNCONFIRMEDKeywords: (none) => NEEDTESTResolution: OLD => (none)
Make bug link to Cauldron
Version: 6 => CauldronTarget Milestone: --- => Mageia 8
Setting to QA team for testing of current state, preferrably on cauldron (if still valid there, probably it is on 7 too)
Assignee: mageiatools => qa-bugs
Ask on the qa-discuss and dev mailing lists for tests. The qa-bugs list is for stable updates.
Assignee: qa-bugs => mageiatools
CC: (none) => mageia
I see "error: unable to find a GRUB drive for /dev/sda1. Check your device map." on line 78405 (which is fin as it's emty) (BTW running the installer in English could help us, ie we wouldn't have to translate back from Swedish) I see that grub.cfg contains: search… --set=root c751a66f-8fba-40d7-bec5-61fb398f0871 which is UUID for /boot, which is normal as it search /boot in order to load kernel+initrd. See: * mount_part: device=nvme0n1p2 mntpoint=/boot isMounted= real_mntpoint= device_UUID=c751a66f-8fba-40d7-bec5-61fb398f0871 root UUID is c98904d8-fef5-4b66-9f4c-2ac0aba5248c (for which I see another search command from grub, which might be the issue) Note for myself: I should log the output of pvs, vgs & lvs in report.bug Could you redo such an install, copy your /mnt/root/drakx/report.bug on a USB key just prior to click "reboot" (or just run the "bug" command at this stage) And then take a photo of the boot error message?
Source RPM: drakx-installer-stage2 => drakx-installer-stage2, grub2Keywords: (none) => NEEDINFO
@martin, I'm considering adding /lib/udev/rules.d/60-block.rules to DrakX
(In reply to Thierry Vignaud from comment #13) > @martin, I'm considering adding /lib/udev/rules.d/60-block.rules to DrakX Revisit bug 20074#c65. I never found a way to fix the resulting race.
I tried to reproduce by following Morgan's steps (starting with the partition setup shown in his first installer log) but the system booted without error. I'm fairly certain this is the same as bug 22059 and hence fixed (even if in an ugly way). Also revisit 22059#c8 for discussion of why adding 60-block.rules is a bad idea.
Thank you for testing and other input :) Closing as presumably fixed. Will open fresh if i see similar again. Will try to remember to run installer in english... Thierry, thank you too. - Will you remember to extend logging as you said ( pvs, vgs & lvs in report.bug) , or should we open an issue for that?
Status: UNCONFIRMED => RESOLVEDResolution: (none) => FIXED
I already did it 2 days ago :-) http://gitweb.mageia.org/software/drakx/commit/?id=5b1642abc6c1ff3b8c4e694893f2e3ee52f7ae42