I have run drakdisk to format a LVM partition, and after clicking to format it appears this error: INTERNAL ERROR: unknown device LM/swap MDK::Common::Various::internal_error() called from /usr/lib/libDrakX/devices.pm:186 devices::entry() called from /usr/lib/libDrakX/devices.pm:201 devices::make() called from /usr/lib/libDrakX/fs/format.pm:185 fs::format::part_raw() called from /usr/lib/libDrakX/fs/format.pm:115 fs::format::part() called from /usr/lib/libDrakX/diskdrake/interactive.pm:1298 diskdrake::interactive::format_() called from /usr/lib/libDrakX/diskdrake/interactive.pm:926 diskdrake::interactive::Format() called from /usr/lib/libDrakX/diskdrake/hd_gtk.pm:131 (eval)() called from /usr/lib/libDrakX/diskdrake/hd_gtk.pm:131 diskdrake::hd_gtk::try_() called from /usr/lib/libDrakX/diskdrake/hd_gtk.pm:126 diskdrake::hd_gtk::try() called from /usr/lib/libDrakX/diskdrake/hd_gtk.pm:227 diskdrake::hd_gtk::__ANON__() called from /usr/lib/libDrakX/mygtk2.pm:1424 (eval)() called from /usr/lib/libDrakX/mygtk2.pm:1424 mygtk2::main() called from /usr/lib/libDrakX/ugtk2.pm:767 ugtk2::main() called from /usr/lib/libDrakX/diskdrake/hd_gtk.pm:120 diskdrake::hd_gtk::main() called from /usr/sbin/drakdisk:93
I'm experiencing the same issue trying to install Mageia 3 alpha 1 using the DVD (arch x86_64) or the boot.iso (then cauldron) on VirtualBox virtual machine. If I remove the partitions/lv and I try to recreate the partition scheme (using always lvm), I experience the already reported bug 7412
CC: (none) => matteo.pasotti
CC: (none) => pterjan, thierry.vignaudSource RPM: (none) => drakxtools
*** This bug has been marked as a duplicate of bug 3238 ***
Status: NEW => RESOLVEDResolution: (none) => DUPLICATE
That's neither the same crash not the same context (installation vs standalone tool)
Status: RESOLVED => REOPENEDResolution: DUPLICATE => (none)Summary: drakdisk crashes when formating an existent LVM => drakdisk crashes when formating an existent LVM (INTERNAL ERROR: unknown device LM/swap)
Thierry, it was not intentional. I read the first lines of the log and they were the same. Next time I'll pay more attention.
There have been changes to this before mga4 release I have not tried fedora, but a period during mga4 beta, installer and diskdrake had problems with encrypted lwm set up by mga2, that later got fixed. Probably this is fixed in your scenario too now. Anyhow, this bugreport is old. Feel free to reopen if there is still problem.
Status: REOPENED => RESOLVEDCC: (none) => friResolution: (none) => OLD