[trusty] Swap partition not set up correctly
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubiquity (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
I think I found a bug with the creation of the swap, here is what I did
sda1 was kept as EFI
sda2 created as ext2 mount to /boot
sda3 created as swap
sda4 created as btrfs
I selected "Encrypt my home"
Installation went fine.
After reboot and logon I asked myself if SWAP was encrypted as I only selected swap, after I found out that when I create a dmcrypt volume I could not select a random key, which I would like to have for swap.
To my satisfaction crypttab was already set up!
mfl@devore:~$ cat /etc/crypttab
cryptswap1 UUID=5300177f-
BUT: top shows, that there is no swap enabled:
top - 12:01:57 up 19 min, 5 users, load average: 0,03, 0,07, 0,06
Tasks: 212 total, 1 running, 210 sleeping, 0 stopped, 1 zombie
%Cpu(s): 1,2 us, 0,6 sy, 0,9 ni, 97,0 id, 0,2 wa, 0,0 hi, 0,0 si, 0,0 st
KiB Mem: 10120340 total, 2343864 used, 7776476 free, 1856 buffers
KiB Swap: 0 total, 0 used, 0 free. 1625312 cached Mem
weird!
mfl@devore:~$ sudo /etc/init.
[sudo] password for mfl:
* Stopping remaining crypto disks... * cryptswap1 (stopped)... [ OK ]
* Starting remaining crypto disks... * cryptswap1 (skipped, device /dev/disk/
mfl@devore:~$ ls -la /dev/disk/by-uuid/
total 0
drwxr-xr-x 2 root root 100 Apr 5 11:42 .
drwxr-xr-x 5 root root 100 Apr 5 11:42 ..
lrwxrwxrwx 1 root root 10 Apr 5 11:42 3beb9864-
lrwxrwxrwx 1 root root 10 Apr 5 11:42 45461e04-
lrwxrwxrwx 1 root root 10 Apr 5 11:42 6B91-2F53 -> ../../sda1
Okay, partition missing? Weird! Check parted...
mfl@devore:~$ sudo parted /dev/sda print all
Model: ATA TOSHIBA THNSNH25 (scsi)
Disk /dev/sda: 256GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 1049kB 512MB 511MB fat32 boot
2 512MB 1024MB 512MB ext2
3 1024MB 6024MB 5000MB
4 6024MB 256GB 250GB btrfs
sda3 happens to be there, but not found by UUID with which it was set up by the installer.
Status changed to 'Confirmed' because the bug affects multiple users.