http://bugzilla.novell.com/show_bug.cgi?id=625490 http://bugzilla.novell.com/show_bug.cgi?id=625490#c Arvin Schnell changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aschnell@novell.com AssignedTo|aschnell@novell.com |fehr@novell.com -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=625490 http://bugzilla.novell.com/show_bug.cgi?id=625490#c2 --- Comment #2 from Klaus Fischer 2010-07-27 19:14:17 UTC --- Created an attachment (id=378716) --> (http://bugzilla.novell.com/attachment.cgi?id=378716) Requested files: YaST2 logs, fstab, crypttab Hi, first of all thanks for taking care of this. In the attachedment I send you the logs of YaST2, fstab and crypttab. Please note the fstab is the one that was produced by the installation procedure. The nofail option was added by the installation procedure because I did not know that it would exist or would be helpful. However, as I wrote mount fails. I of course also tried to mount with deleting noauto but this did not change anything. I am also aware of that the second none in the cr_sda7 line was specified with "noauto" by the intallation procedure. So this I did change manually. However, if I leave noauto (I of course also tried with the nofail option as just explained, no change) I am not asked for a password. The command that you told me is not really of help because when I use it then the system just tells me that cr_sda7 already exists. An explanation for all the trouble that came to my mind is that I remember that I told the installation procedure to reread mount points from /etc/fstab of the already installed system. As far as I remember the installation started to complain about sda7 after this although it seem to work ok before. Please send me message in case you need any additional information. Thank you very much for your help. Cheers, Klaus -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=625490 http://bugzilla.novell.com/show_bug.cgi?id=625490#c4 Thomas Fehr changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #4 from Thomas Fehr 2010-07-28 09:56:48 UTC --- Unfortunately I have to tell you that yast2-storage destroyed the content of your encrypted volume. This is of course a bug. I am will try to reproduce this here and will create a fix. Fortunately you write that you have a backup of your data, so at least there is no data loss. You can fix your system the following way (you must be root to be able to do this): - execute /sbin/cryptsetup status cr_sda7, this should show something like: /dev/mapper/cr_sda7 is active: cipher: aes-cbc-essiv:sha256 keysize: 128 bits device: /dev/sda7 offset: 1032 sectors size: 57222435 sectors mode: read/write - create an ext3 filesystem on the encrypted volume mkfs.ext3 /dev/mapper/cr_sda7 - mount it where it belongs mount /dev/mapper/cr_sda7 /crypto/Linux If anything goes wrong here just email me at fehr@suse.de. Afterwards you can restore your data from your backup to /crypto/Linux. The setup should also be fine after next reboot. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=625490 http://bugzilla.novell.com/show_bug.cgi?id=625490#c6 --- Comment #6 from Thomas Fehr 2010-07-29 14:08:25 UTC --- Problem is fixed in SVN Head and openSuSE-11.3 branch. NOTE: Of course the problem is still present on 11.3 installation media, so everyone using "Import fstab" feature in 11.3 having encrypted partitions still needs to be very careful. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.