+++ This bug was initially created as a clone of Bug #5661 +++ Using comment from Glen for the main description: filesystem layout on one of the test systems is a little unusual, but that's the point, since I am testing the unusual: One test I have been testing with, is: 2 x 4GB disks, each with 1 partition on them, (/dev/vda1 and /dev/vda2), both of type: 8e (lvm). Both partitions are added to a volume group. in the volume group, I have the following LVs. boot (368MB), xfs filesystem ntfs (688MB), ntfs filesystem opt (160MB), reiserFS root (5.65GB), encrypted XFS. swap (492m) In the installer, when I first open up the VG and click on the encrypted partition, it shows an encrypted, and the file system type as brtfs (which it is not).. When I click the use button, it asks me for the passphrase. After entering it, the tab is not refreshed and goes blank, however, if I switch to a disk tab, then switch back to the volume group tab, it shows up correctly, and I can click on the encrypted xfs partition and click view, to view the files. It is configured with grub2. The above test system won't actually boot up, because it didn't cope with the encrypted root file system, so it ends up in drakcut, complaining about not being able to find /dev/mapper/crypt_vg_mga_root, however, that's not what this bug is about.
Downgrading severity.
Priority: release_blocker => High
CC: makowski.mageia => (none)
Whiteboard: (none) => 4RC
As M4 will not change, pls ge so kind to either 'whiteboard' it to 5beta1 if still valid, or to close it as old if not. Thanks.
diskdrake/installer have always had various problems with encryption and lvm in different combinations, bad refresh is the milder forms. I have posted serveral issues thrugh the mageia life about diskdrake/installer crashing, impossible to achieve expected result, etc. I always set up systems to use lvm, and often encrypted. Also these days, when installing mga5 beta the installer disk partition step exited two times and i found myself back at the step the installer asks for how the disk should be used, but to my luck the result in the end happened to be OK. (i had MSW7 and another ntfs on the disk, and a boot partition and a couple lvm vg paritions all made with Gparted using another live disk (by experience this works best) And then told the installer to make an encrypted LVM containing various partitions. No I will not post another bug on it unless someone really have the time to mess with it, them i wil happily provide feedback on overhauled versions - i understand diskdrake need a severe overhaul, and it is so easy to trig various misbehaviours it is much more efficient the asignee do tests himself wihtout spending time with correspondence until he thinks it is time for review. Regarding this bug here, the installer for me actually did "refresh" by exiting back to the previous install step so it could be run again... so... well it "works for me kind of..."
There was no action in this report since 2014-11-15 Is this bug still valid with Mga5 or (preferably) cauldron / mga6dev1 ?
Keywords: (none) => NEEDINFO
Will probably try again with mga6 around beta
(In reply to Morgan Leijström from comment #5) > Will probably try again with mga6 around beta Thx :-) Please be aware that the betas are now called development snapshots, so we'll have something like "Mageia6-dev1" instead of "Mageia6-beta1" isos
(In reply to Morgan Leijström from comment #5) > Will probably try again with mga6 around beta And?
The bugreporting share of my life is currently exhausted... ;) (not only mageia.. gotta work) Thanks for the ping though.
(In reply to Morgan Leijström from comment #8) > The bugreporting share of my life is currently exhausted... ;) > (not only mageia.. gotta work) No problem, thx for replying. I'll close this report as OLD, since the issue wasn't reproduced since 2014. Feel free to reopen, if needed.
Status: NEW => RESOLVEDResolution: (none) => OLD