Mailinglist Archive: opensuse-bugs (19869 mails)

< Previous Next >
[Bug 395621] New: adding existing encrypted partitions for mounting during installation has no effect
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Thu, 29 May 2008 15:54:19 -0600 (MDT)
  • Message-id: <bug-395621-21960@xxxxxxxxxxxxxxxxxxxxxxxxx/>
https://bugzilla.novell.com/show_bug.cgi?id=395621


Summary: adding existing encrypted partitions for mounting during
installation has no effect
Product: openSUSE 11.0
Version: RC 1
Platform: HP
OS/Version: openSUSE 11.0
Status: NEW
Severity: Normal
Priority: P5 - None
Component: YaST2
AssignedTo: bnc-team-screening@xxxxxxxxxxxxxxxxxxxxxx
ReportedBy: ah@xxxxxxxx
QAContact: jsrain@xxxxxxxxxx
Found By: Beta-Customer


I have two encrypted partitions
one old style (since suse 10.0) setup on /dev/md1 (sda3 and sdb2)
(and that one is v. important to me)
and one test one - created in 10.2 as crypto_LUKS

I have used the manual partitioning method - added them to be mounted (and do
not format) entered passwords for both of them without problem
(although the legacy partition took much longer to be processed by yast than
the newer one)
the install process went smoothly - now I have rebooted twice
.. and still cannot find my encrypted partitions mounted


It even did not ask me for a password during reboots for neither of them.

linux-spch:~ # df -HT
Filesystem Type Size Used Avail Use% Mounted on
/dev/sdb5 ext3 253G 2.1G 238G 1% /
udev tmpfs 1.1G 127k 1.1G 1% /dev
/dev/sda5 ext3 231G 5.9G 216G 3% /zdjecia
/dev/md0 ext3 63G 38G 22G 64% /suse103

linux-spch:~ # cat /etc/crypttab
cr_sda6 /dev/disk/by-id/scsi-SATA_SAMSUNG_HD400LJS0H2J1WL822696-part6
none none

linux-spch:~ # cat /etc/cryptotab
/dev/loop0 /dev/md1 /oldhome ext3 twofish256 defaults

I am attaching yast logs

Is there anything else I should post?

p.s. 11.0 is great job! - this is actually the first time I managed to see the
new kde4 looks - and I love it!


--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >