no swap created when selecting both dm-crypt and ecryptfs

Bug #1320702 reported by Nobuto Murata
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Expired
High
Unassigned

Bug Description

When selecting both "Ecrypted LVM"(dm-crypt) and "Encrypt home directory"(ecryptfs). No swap will be created.

May 18 21:17:07 ubuntu ubiquity: INFO: Setting up swap: [/dev/dm-2]
May 18 21:17:07 ubuntu ubiquity: INFO: Successfully setup encrypted swap!
May 18 21:18:56 ubuntu ubiquity: * Starting crypto disk...
May 18 21:18:56 ubuntu ubiquity: * cryptswap1 (skipped, device /dev/disk/by-uuid/1f4a2305-4a67-49dd-972c-612fb4ba3818 does not exist)...
May 18 21:18:56 ubuntu ubiquity: ...fail!

$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 111.8G 0 disk
├─sda1 8:1 0 512M 0 part
├─sda2 8:2 0 244M 0 part
└─sda3 8:3 0 111.1G 0 part
  └─sda3_crypt (dm-0) 252:0 0 111.1G 0 crypt
    ├─ubuntu--vg-root (dm-1) 252:1 0 99.2G 0 lvm
    └─ubuntu--vg-swap_1 (dm-2) 252:2 0 11.9G 0 lvm
sdb 8:16 0 14.9G 0 disk
sdc 8:32 1 14.5G 0 disk
└─sdc1 8:33 1 14.4G 0 part /cdrom
loop0 7:0 0 933.9M 1 loop /rofs

$ blkid
/dev/sda1: UUID="320D-6F34" TYPE="vfat"
/dev/sda2: UUID="e75d9d7c-d976-463f-897b-53f10bb31fa5" TYPE="ext2"
/dev/sda3: UUID="79c9d6cb-146e-433b-9cbb-acb3f087446d" TYPE="crypto_LUKS"
/dev/loop0: TYPE="squashfs"
/dev/sdc1: UUID="F2B2-8FBF" TYPE="vfat"
/dev/mapper/sda3_crypt: UUID="2sfzzF-gENJ-bvN6-2QNW-tBPI-Zro6-FSjCei" TYPE="LVM2_member"
/dev/mapper/ubuntu--vg-root: UUID="e40e6d27-4deb-473d-900b-01324e2b1616" TYPE="ext4"

$ cat /target/etc/crypttab
sda3_crypt UUID=79c9d6cb-146e-433b-9cbb-acb3f087446d none luks,discard
cryptswap1 UUID=1f4a2305-4a67-49dd-972c-612fb4ba3818 /dev/urandom swap,cipher=aes-cbc-essiv:sha256

$ tail -n +7 /target/etc/fstab
# <file system> <mount point> <type> <options> <dump> <pass>
/dev/mapper/ubuntu--vg-root / ext4 errors=remount-ro 0 1
# /boot was on /dev/sda2 during installation
UUID=e75d9d7c-d976-463f-897b-53f10bb31fa5 /boot ext2 defaults 0 2
# /boot/efi was on /dev/sda1 during installation
UUID=320D-6F34 /boot/efi vfat defaults 0 1
/dev/mapper/ubuntu--vg-swap_1 none swap sw 0 0
/dev/mapper/cryptswap1 none swap sw 0 0

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: ubiquity 2.18.8
ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.2-0ubuntu4
Architecture: amd64
CasperVersion: 1.340
CurrentDesktop: Unity
Date: Mon May 19 06:22:55 2014
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed boot=casper quiet splash --
LiveMediaBuild: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140518)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Nobuto Murata (nobuto) wrote :
Revision history for this message
Nobuto Murata (nobuto) wrote :

After reboot, no swap mounted.

$ free -h
             total used free shared buffers cached
Mem: 11G 1.2G 10G 207M 27M 603M
-/+ buffers/cache: 636M 10G
Swap: 0B 0B 0B

$ sudo swapon -a
swapon: /dev/mapper/ubuntu--vg-swap_1: read swap header failed: Invalid argument
swapon: /dev/mapper/cryptswap1: stat failed: No such file or directory

tags: added: trusty
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ubiquity (Ubuntu):
status: New → Confirmed
Revision history for this message
sverker wahlin (sverker-wahlin) wrote :

this looks like my problem as well. I managed to get a swap partition going using mkswap, but it isn't mapped to the cryptsetup, and, I assume, it's not encrypted...

Changed in ubiquity (Ubuntu):
importance: Undecided → High
Revision history for this message
Marcus Tomlinson (marcustomlinson) wrote :

This release of Ubuntu is no longer receiving maintenance updates. If this is still an issue on a maintained version of Ubuntu please let us know.

Changed in ubiquity (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]

Changed in ubiquity (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.