Bugzilla – Bug 435244
new partitioner unable to configure ciphered disk created by 11.0
Last modified: 2009-01-03 18:34:03 UTC
Created attachment 245452 [details] yast logs I created ciphered disk using 11.0 (i386). I install new 11.1 Beta1 and try to configure (mount) this device. Partitioner showed that this device is ciphered (c symbol) and allow me to set mount point. After click to apply it faild with message "mount faild unknown filesystem ...." Logs will follow
Seems to work for me. Please test again with Beta 3.
Created attachment 251810 [details] screen shot of the error popup
Created attachment 251812 [details] yast2 logs from openSUSE 11.1 beta4 Still issue in Beta4
Steps to reproduce 1. Install 11.0 2. Create some ciphered disk somewhere (not /home or / or whatever) 3. Install 11.1 - new installation 4. In new system (11.1) go to YaST 5. Use Paritioner and select ciphered device 6. Set mount point, do not format 7. You should see same picture as I did.
Should be fixed.
*** Bug 441107 has been marked as a duplicate of this bug. ***
*** Bug 446020 has been marked as a duplicate of this bug. ***
*** Bug 446651 has been marked as a duplicate of this bug. ***
Negative. I just tried RC1 with an encrypted /home . It wasn't shown as encrypted drive (no "C") in the first view. I couldn't mount it as /home - filesystem not known (oh, encrypted ;) ). Then it showed "CF" !! . I reverted this and the "C" was now there. If I select the "encrypt partition" beneath the format options and "just mount", then it worked. Thats pretty confusing!
Please provide YaST2 logs. Or check the output of blkid for the device with the encrypted home: Does blkid report TYPE="crypt_LUKS" or some filesystem?
It might also be interesting to see what /lib/udev/vol_id reports for the partition. I see the problem as following: The partition contained some filesystem before creating the encrypted partition. cryptsetup does not wipe out existing signatures (see bug #410418 comment #3). So the partition contains several signatures now and blkid simply reports the wrong. vol_id seems to make a better job in this case. But changing YaST to use vol_id instead of blkid is far to risky at this time. Also, this is not a regression to 11.0. And affect only some encrypted partitions. Thus changing priority.
It reported TYPE="crypt_LUKS". For y2logs I need more time.
Closing after receiving no response within four weeks. Feel free to reopen when requested information is provided.