Mailinglist Archive: opensuse-bugs (7467 mails)
| < Previous | Next > |
[Bug 361293] New: cannot mount encrypted partition
- From: bugzilla_noreply@xxxxxxxxxx
- Date: Tue, 12 Feb 2008 15:21:05 -0700 (MST)
- Message-id: <bug-361293-21960@xxxxxxxxxxxxxxxxxxxxxxxxx/>
https://bugzilla.novell.com/show_bug.cgi?id=361293
Summary: cannot mount encrypted partition
Product: openSUSE 10.3
Version: Final
Platform: i686
OS/Version: openSUSE 10.3
Status: NEW
Severity: Critical
Priority: P5 - None
Component: Basesystem
AssignedTo: bnc-team-screening@xxxxxxxxxxxxxxxxxxxxxx
ReportedBy: kevin.coonan@xxxxxxxxx
QAContact: qa@xxxxxxx
Found By: Customer
After the initial install of OpenSUSE 10.3 with a non-encrypted '/' partition
and an encrypted '/home/user_name partition' (created using the graphic
partitioner) the encrypted partition does not mount, even after correctly
supplying the key.
The problem is primarily in the created '/etc/fstab'.
The original fstab:
/dev/disk/by-id/scsi-SATA_HTS721010G9AT00_MPC011Y0G1PB6C-part1 /
ext3 acl,user_xattr 1 1
/dev/mapper/cr_sda5 /home/user_name acl,user_xattr,noauto
acl,user_xattr,noauto 0
/dev/disk/by-id/scsi-SATA_HTS721010G9AT00_MPC011Y0G1PB6C-part2 swap
swap defaults 0 0
proc /proc proc defaults 0 0
sysfs /sys sysfs noauto 0 0
debugfs /sys/kernel/debug debugfs noauto 0 0
usbfs /proc/bus/usb usbfs noauto 0 0
devpts /dev/pts devpts mode=0620,gid=5 0 0
Didn't seem to work so well. If I tried to mount /dev/sda5 I got a unknown
filesystem message. When I ran /etc/init.d/boot.crypto start it didn't work as
I had hoped.
/lib/udev/vol_id -u /dev/sda5 Showed a UUID which was different from the one
returned by dumpe2fs /dev/sda5. Seems that there are two UUIDs assigned, ? if
one is for the encrypted partition and the other is for the ext3 partition seen
by the OS. There also seems to be an extra space before /dev/mapper/... which
is probably throwing the parser off.
So I used the UUID from dumpe2fs to mount via the UUID (uuid=...), commented
out the /dev/mapper/cr_sda5 ... line, and when /etc/init.d/boot.crypto start
followed by mount -a things worked. There are a good deal of similar
complaints in other forums, none with answers.
I suspect I only half finished the job, but at least can read my partition
again!
--
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.
Summary: cannot mount encrypted partition
Product: openSUSE 10.3
Version: Final
Platform: i686
OS/Version: openSUSE 10.3
Status: NEW
Severity: Critical
Priority: P5 - None
Component: Basesystem
AssignedTo: bnc-team-screening@xxxxxxxxxxxxxxxxxxxxxx
ReportedBy: kevin.coonan@xxxxxxxxx
QAContact: qa@xxxxxxx
Found By: Customer
After the initial install of OpenSUSE 10.3 with a non-encrypted '/' partition
and an encrypted '/home/user_name partition' (created using the graphic
partitioner) the encrypted partition does not mount, even after correctly
supplying the key.
The problem is primarily in the created '/etc/fstab'.
The original fstab:
/dev/disk/by-id/scsi-SATA_HTS721010G9AT00_MPC011Y0G1PB6C-part1 /
ext3 acl,user_xattr 1 1
/dev/mapper/cr_sda5 /home/user_name acl,user_xattr,noauto
acl,user_xattr,noauto 0
/dev/disk/by-id/scsi-SATA_HTS721010G9AT00_MPC011Y0G1PB6C-part2 swap
swap defaults 0 0
proc /proc proc defaults 0 0
sysfs /sys sysfs noauto 0 0
debugfs /sys/kernel/debug debugfs noauto 0 0
usbfs /proc/bus/usb usbfs noauto 0 0
devpts /dev/pts devpts mode=0620,gid=5 0 0
Didn't seem to work so well. If I tried to mount /dev/sda5 I got a unknown
filesystem message. When I ran /etc/init.d/boot.crypto start it didn't work as
I had hoped.
/lib/udev/vol_id -u /dev/sda5 Showed a UUID which was different from the one
returned by dumpe2fs /dev/sda5. Seems that there are two UUIDs assigned, ? if
one is for the encrypted partition and the other is for the ext3 partition seen
by the OS. There also seems to be an extra space before /dev/mapper/... which
is probably throwing the parser off.
So I used the UUID from dumpe2fs to mount via the UUID (uuid=...), commented
out the /dev/mapper/cr_sda5 ... line, and when /etc/init.d/boot.crypto start
followed by mount -a things worked. There are a good deal of similar
complaints in other forums, none with answers.
I suspect I only half finished the job, but at least can read my partition
again!
--
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 > |