Bug 114219

Summary: YaST2 failed to mount an existing encrypted file system
Product: [openSUSE] SUSE LINUX 10.0 Reporter: Lenz Grimmer <lgrimmer>
Component: YaST2Assignee: Thomas Fehr <fehr>
Status: RESOLVED FIXED QA Contact: Klaus Kämpf <kkaempf>
Severity: Normal    
Priority: P5 - None CC: riggwelter
Version: Beta 3   
Target Milestone: RC 1   
Hardware: Other   
OS: All   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: y2log tarball

Description Lenz Grimmer 2005-08-30 20:08:15 UTC 
Thanks for fixing BUG#104441, which now encouraged me to give this another try.
I have an encrypted home directory on LVM (/dev/system/cryptohome) that I wanted
to mount to /home using the custom partitioner during the initial installation.
Unfortunately this still does not seem to work - when YaST attempted to mount
that partition, I got a quite unhelpful error popup window that informed me that
the mount failed because of "Error -3003". After the installation, there was no
/etc/cryptotab. This is how it looks like for SUSE 9.3 (which works):

[SNIP]
/dev/loop0  /dev/system/cryptohome /home          reiserfs   twofish256
noatime,data=journal,acl,user_xattr
[SNIP]
Comment 1 Lenz Grimmer 2005-08-30 20:09:09 UTC 
Created attachment 48221 [details]
y2log tarball
Comment 2 Thomas Fehr 2005-09-01 07:39:33 UTC 
Maybe this is something similar to bug#113322.
I will look into this next week, this week I am in Prag and cannot do too much.
Comment 3 Lenz Grimmer 2005-09-02 16:21:33 UTC 
BUG#113524 is probably a duplicate of this one, too.
Comment 4 Lukas Ocilka 2005-09-05 06:44:13 UTC 
*** Bug 113524 has been marked as a duplicate of this bug. ***
Comment 5 Thomas Fehr 2005-09-05 17:09:29 UTC 
Handling of encrypted LVM LVs in instsys was broken in libstorage.
Comment 6 Thomas Fehr 2005-09-06 08:35:35 UTC 
*** Bug 114223 has been marked as a duplicate of this bug. ***