Description of problem: I have tried to re-use existing luks partion and/or create new luks partition during the install, I get a "cryptsetup failed" popup. The console message isn't more explicative. Version-Release number of selected component (if applicable): Last iso Mageia Cauldron dvd 64 bit How reproducible: Install and try to create and use a luks
after the install, i can access the existing luks partition after the install cryptosetup. So it's not an unsupported format ;)
Hi, thanks for reporting this bug. maybe duplicate/related to bug 3482 Assigned to the packages maintainers. (Please set the status to 'assigned' if you are working on it)
Keywords: (none) => TriagedCC: (none) => thierry.vignaudAssignee: bugsquad => pterjanSource RPM: (none) => drakx-installer-stage2
Can you attach your /root/drakx/report.gz please?
Keywords: (none) => NEEDINFO
I can confirm this one as well. It isn't fixed in Mageia 2 alpha 2 either.
CC: (none) => uberscubajim
Oh, hang on. It isn't fixed if you install from the live CD but the network install seems to work OK.....
*** Bug 3513 has been marked as a duplicate of this bug. ***
Can users experiencing this problem who used drakx-installer (not LiveCD), please attach /root/drakx/report.gz as asked for in comment 3 (In reply to comment #5) > Oh, hang on. It isn't fixed if you install from the live CD but the network > install seems to work OK..... @ Blino Is this supposed to work when installing from the liveCD, too? If it is, maybe Jim's bug 3513 can be reopened and used
CC: (none) => mageia, marja11
It can't work with LiveCD because cryptsetup is not in the <LiveCD Name>.lst file.
CC: (none) => dvgevers
please if it's another issue, open another bug.
@ Yves Please attach the file Thierry asked for in comment 3, or, when trying to reproduce this problem, plug in a usb stick and switch to console 2 (by pressing 'Ctrl-Alt-F2') during installation, and type: 'bug' then press Enter. It will put report.bug on the key.
For the record, it works for me
Status from beta1 pre release test: Creating a new encrypted partition at install time results in the described "cryptsetup failed" popup. Using existing encrypted partitions does work.
CC: (none) => oliver.bgr
I can confirm Oliver's comment. This was when installing from the Mageia-2-beta1-i586-DVD.iso image.
CC: (none) => fri
This was caused by a change implemented at my request in bug 3092. The xts kernel module is not available in the installer's kernel. During a normal usage of an xts encrypted filesystem, I also see the cryptd module. Both modules should be added to the kernel in the installer.
CC: (none) => davidwhodgins
Fixed. boot.iso is being regenerated
Status: NEW => RESOLVEDResolution: (none) => FIXED
I'm able to test as soon as the new boot.iso is available.
OK, I've tried it with the boot.iso dated 24-Feb-2012 with the SHA1 value that starts bc17b44 and I still get the "cryptsetup failed" error message. Any ideas?
(In reply to comment #15) > Fixed. > boot.iso is being regenerated Wouldn't it be the drakx-installer-stage2 that needs to have the kernel modules added in the mdkinst.sqfs file?
(In reply to comment #18) > (In reply to comment #15) > > Fixed. > > boot.iso is being regenerated > > Wouldn't it be the drakx-installer-stage2 that needs to have > the kernel modules added in the mdkinst.sqfs file? reopening and changing assignee to Thierry, since he was working on this bug. there is a new drakx-installer-stage2 too, that got pushed later (16 hrs ago) although I only read about "include more HID drivers (mga#4129)"
Status: RESOLVED => REOPENEDResolution: FIXED => (none)Assignee: pterjan => thierry.vignaud
Stage2 has already been rebuild: -rwxr-xr-x 1 root root 47968256 Feb 24 16:43 mdkinst.sqfs* You need to retest
Created attachment 1639 [details] Patch for /usr/lib/libDrakX/fs/dmcrypt.pm This is strange. It fails until I manually run "modprobe xts". I've been using xts mode for years, and didn't even know that xts mode used a separate kernel module. I've never had to modprobe it before. Anywahy here's a patch to add xts to the list of modules loaded for rpmdrake when encrypting a filesystem.
Applied
drakxtools-backend needs to be pushed, and then drakx-installer-stage2 rebuilt so we can finish testing.
installer is already up to date
Closing
Status: REOPENED => RESOLVEDResolution: (none) => FIXED
Sorry, I need to reopen because it is not fixed. I have the same problem with Mageia 2 Beta 3. You can find the detailed log for ALT+F3 output here : https://bugs.mageia.org/show_bug.cgi?id=5661
Status: RESOLVED => REOPENEDCC: (none) => ylenyResolution: FIXED => (none)
Severity: normal => critical
why have you reopen this bug if you have make another one ? the apposite question is also true
Hello Manuel >why have you reopen this bug if you have make another one ? Because I don't know if the mageia developpers want to work with this ticket or the new one that I have opened. Ok, I will close this ticket and stay tuned with the other ticket.
Status: REOPENED => RESOLVEDResolution: (none) => OLD
This one was fixed.
Status: RESOLVED => VERIFIEDResolution: OLD => FIXED
Thank you :) Confirming it now works to open up and use an encrypted LVM. However, there is a somewhat confusing delay, bug 5886.
Status: VERIFIED => RESOLVED