[Bug 1546714] Re: System not booting when /home is on separate LUKS-encrypted partition

[Gary Gaydos]

** Package changed: ubuntu => systemd (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1546714

Title:
  System not booting when /home is on separate LUKS-encrypted partition

Status in systemd package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Michael Roesch <ROESCH3 at de.ibm.com> - 2016-02-16 07:47:10 ==
  Kernel: 4.4.0.4

  Partition setup:

  DASD 0.0.5d30 (ECKD) - 7.4 GB IBM S390 DASD drive
  >     #1    650.0 MB    F  ext2        /boot
  >     #2      2.7 GB    F  ext4        /
  >     #3      4.0 GB    K  crypto      (dasda3_crypt)
  >            49.2 kB       unusable
  Encrypted volume (dasda3_crypt) - 4.0 GB Linux device-mapper (crypt)
  >     #1      4.0 GB    f  ext4        /home

  Using this partition setup, the system is not able to complete the
  boot process. The systems stops booting with these messages:

  ? ?0;32m  OK   ?0m? Started Load/Save Random Seed.   
  systemd-random-seed.service   
  ? ?0;32m  OK   ?0m? Started Flush Journal to Persistent Storage.   
  systemd-journal-flush.service   
  ? ?0;32m  OK   ?0m? Started LSB: Tune IDE hard disks.   
  hdparm.service   
  systemd-udev-trigger.service   
  ? ?0;32m  OK   ?0m? Started udev Coldplug all Devices.   
  ? ?0;32m  OK   ?0m? Found device /dev/disk/by-uuid/0fe87e7c-ef50-44df-af73-bd1f8
  f305aa2.   
           Starting Cryptography Setup for dasda3_crypt...   
  ? ?0;32m  OK   ?0m? Found device /dev/disk/by-uuid/dbce2efd-d3d5-409c-8e22-3bb93
  7d9dfc8.   
  ? ?0;32m  OK   ?0m? Found device /dev/hvc0.   
  ? ?0;32m  OK   ?0m? Found device /dev/ttyS0.   
  ? ?0;32m  OK   ?0m? Found device /dev/ttysclp0.   
           Starting File System Check on /dev/...d-d3d5-409c-8e22-3bb937d9dfc8... 
    
  ? ?0;32m  OK   ?0m? Started File System Check Daemon to report status.   
  systemd-fsckd.service   
  systemd-fsck at dev-disk-by\x2duuid-dbce2efd\x2dd3d5\x2d409c\x2d8e22\x2d3bb937d9dfc
  8.service   
  boot.mount   
    
  This does also happen, when you put LUKS on top of an LVM setup or if you even place the /home partition on a separate DASD. The problem is the same.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1546714/+subscriptions