The "draklive-install" program crashed. Drakbug-15.19 caught it. -suite création LVM crypté, il est sans doute pas possible de choisir d'installer GRUB sur cette LVM!? Il y aurait eu un message me l'interdisant je n'en serais là ;-) INTERNAL ERROR: unknown device /dev/vg-boot/root MDK::Common::Various::internal_error() called from /usr/lib/libDrakX/bootloader.pm:1641 bootloader::device_string2grub() called from /usr/lib/libDrakX/bootloader.pm:1916 bootloader::write_grub() called from /usr/lib/libDrakX/bootloader.pm:1983 bootloader::install_grub() called from /usr/lib/libDrakX/bootloader.pm:2024 bootloader::action() called from /usr/lib/libDrakX/bootloader.pm:2035 bootloader::install() called from /usr/lib/libDrakX/any.pm:262 (eval)() called from /usr/lib/libDrakX/any.pm:260 any::installBootloader() called from /usr/lib/libDrakX/any.pm:239 any::setupBootloaderUntilInstalled() called from /usr/sbin/draklive-install:326 main::setup_bootloader() called from /usr/sbin/draklive-install:70 main::install_live() called from /usr/sbin/draklive-install:42 ...propagated at /usr/lib/libDrakX/any.pm line 267. Perl's trace: standalone::bug_handler() called from /usr/lib/libDrakX/any.pm:267 any::installBootloader() called from /usr/lib/libDrakX/any.pm:239 any::setupBootloaderUntilInstalled() called from /usr/sbin/draklive-install:326 main::setup_bootloader() called from /usr/sbin/draklive-install:70 main::install_live() called from /usr/sbin/draklive-install:42 Theme name: oxygen-gtk Kernel version = 3.8.0-desktop-0.rc4.1.mga3 Distribution=Mageia release 3 (Cauldron) for x86_64 CPU=Intel(R) Core(TM) i5-2450M CPU @ 2.50GHz
Priority: Normal => release_blockerCC: (none) => pterjan, thierry.vignaud, tmbSummary: draklive-install crashed => draklive-install crashed (grub over lvm)
Thanks for the bug report. Do you know if it's still valid on the Beta 3?
CC: (none) => pierre-malo.denielou
no answer for 2 months now. Decreasing priority. Feel free to change it if you have any input
Priority: release_blocker => HighCC: (none) => ennael1
CC: (none) => bequimao.de
I could reproduce the bug on my system with the traditional installer. No encryption envolved. It does not matter, if I install to the logical partition of LVM or to another partition. Just the presence of my LVM only leads to the permanent loop. Version is Mageia 4 alpha 2 (KDE, amd64) The message begins with: Prepairing initial startup programs ... and then Internal Error: Unknow device sdb10 MDK::Common::Various::Internal_Error called from /usr/lib/libDrakX/devices.pm:186 There is no sdb10 in my system. When I accept the button OK, than it starts again: Prepairing initial startup programs ... see also: https://forums.mageia.org/en/viewtopic.php?f=7&t=4962&p=40155#p40155 Best regard, Bequimão
Created attachment 4369 [details] bug.txt from the test above
(In reply to Ulrich Beckmann from comment #4) > Created attachment 4369 [details] > bug.txt from the test above cc'ing coling, because he said before FrOSCon he was willing to help (when he read on dev ml that we'd meet Ulrich with this problem)
CC: (none) => mageia, marja11Source RPM: draklive-install-1.37-2.mga3 => draklive-install-1.37-2.mga3 drakx-installer-stage2
Stéphane and Ulrich, can you confirm whether this issue affects the released Mageia 4, and Mageia 5 alpha1? (Note that Mageia 5 alpha1 should be released within a week).
CC: (none) => remi
The issue is still there. Now tested with Mageia-5-alpha1-x86_64-DVD. Ulrich
Whiteboard: (none) => 5alpha1
While i have not got exactly this, i frequently experience problems using lvm especially when also encryption is used. I have noticed that if I make a lvm, partitions inside it, set their mount points and then create other partiitons (more exactly another encrypted lvm this evening, fresh network install) - it forgets the mount points. It seems like that happened for you So a tip: do it again and as last step before exiting from partitioning, click every partition including them in lvm and check if all mount points are OK.
CC: (none) => fri
Hi Morgan, Not interested in workarounds and guesses here. The issue is tested and confirmed on my old notebook repeatedly in various Mageia versions. The new one has UEFI and GPT, and thus no tests with Mageia so far. I conclude that a developer could only debug the error on this particular machine. Otherwise the cost would by high, and the test probably would not lead to the error but to a sucessfull installation. So I request to close this bug report. Best regards, Ulrich Beckmann
You are not alone, diskdrake problems are confirmed many times... I have filed various bugs about installer/diskdrake partitioning with lvm with and without encryption. Unfortunately we are a bit short of developers. Result of a workaround by guessing can lead to know more about the bug. Installer stubbornly use to screw up partition use for me. But I am stubborn too, and use diskdrake with encrypted lvms it until it works. I can not remember it have fouled up if i just assign mount points on existing partitions. So two passes use to do it: first partition it, restart and next round just set mount points and proceed install. If it is like that for you too then we know diskdrake partitions correctly and also set mount points correctly, if done separately but not in same pass. That could help developer pinpoint the problem, was my thought.
Summary: draklive-install crashed (grub over lvm) => draklive-install crashed (grub over crypted lvm) (unknown device /dev/vg-boot/root)
Is this still valid in 5rc?
There's been fixes regarding such issue in pre-final Mga5. But we might still have a race here between drakx trying to access devices and udevd trying to create devices. We probably miss a 'udevadm settle' call
CC: (none) => mageia
I have now finished a sucessfull installation of Mageia 5 on the same machine. The infinite loop didn't occur. The bug cannot be reproduced here any longer. Ulrich
So responding to comment #13 closing report.
Status: NEW => RESOLVEDCC: (none) => nicResolution: (none) => FIXED