boot hangs for no way to enter password for encrypted LVM

[bugproxy]

Problem Description
=======================
VNC booting Ubuntu hangs after:
[ 0.774027] /build/buildd/linux-3.16.0/drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
due to no way to enter the password for an encrypted device. It occurs for an installation with the device encryption selected. Without encryption, the warning message still appears, but the booting can continue till login prompt.

Work Around: If selecting Recovery Mode quickly to boot, then there is the chance to enter a password and bring up the system.

However, at the booting menu, if your hand is too slow, then the terminal mode will be toggled to somewhat unknown. Then the <Enter> key will not work, nor do the upper case letters. You have to type Ctrl+M (alternative of <Enter> with normal TERM setting) to get in "Advanced options for Ubuntu", but still end up unable to provide the correct password if it contains any upper case letters.

*** Selections in Ubuntu installation ***
Install
Language - English
Country - United States
Detect keyboard - No
Country for the keyboard - English (US)
Keyboard layout - English (US)
Hostname - UbuntuCrypt
Full name - ...
Username - .....
Password - *******
Encrypt directory - No
Time zone - Central
Partitioning method - Guided - use entire disk and set up encrypted LVM
Select disk - Virtual disk 1 (vda) - 53.7 GB Virtio Block Device
Write the changes to disks and configure LVM - Yes
Encryption passphrase - *******
Amount of volume group to use - 53.4 GB - Continue
Write the changes to disks - Yes
manage upgrades - Install security updates automatically
System clocks set to UTC - No
Installation complete - Continue

*** Machine/software info ***
[root@lep8b /]# uname -a
Linux lep8b.austin.ibm.com 3.10.42-2007.pkvm2_1_1.16.ppc64 #1 SMP Fri Aug 15 10:45:07 CDT 2014 ppc64 ppc64 ppc64 GNU/Linux

[root@lep8b /]# rpm -qa kimchi
kimchi-1.2.1-20.1.1.pkvm2_1_1.23.ppc64
[root@lep8b /]#

[root@lep8b iso]# ls -l ubuntu-14.10-server-ppc64el-GA.iso
-r--r--r--. 1 qemu qemu 585523200 Oct 22 13:09 ubuntu-14.10-server-ppc64el-GA.iso

[root@lep8b /]# rpm -qa "libvirt*"
libvirt-daemon-1.2.5-1.pkvm2_1_1.20.19.ppc64
libvirt-daemon-driver-storage-1.2.5-1.pkvm2_1_1.20.19.ppc64
libvirt-daemon-driver-lxc-1.2.5-1.pkvm2_1_1.20.19.ppc64
libvirt-daemon-driver-nodedev-1.2.5-1.pkvm2_1_1.20.19.ppc64
libvirt-daemon-config-nwfilter-1.2.5-1.pkvm2_1_1.20.19.ppc64
libvirt-daemon-driver-network-1.2.5-1.pkvm2_1_1.20.19.ppc64
libvirt-daemon-driver-qemu-1.2.5-1.pkvm2_1_1.20.19.ppc64
libvirt-docs-1.2.5-1.pkvm2_1_1.20.19.ppc64
libvirt-daemon-driver-nwfilter-1.2.5-1.pkvm2_1_1.20.19.ppc64
libvirt-daemon-driver-interface-1.2.5-1.pkvm2_1_1.20.19.ppc64
libvirt-daemon-config-network-1.2.5-1.pkvm2_1_1.20.19.ppc64
libvirt-daemon-driver-secret-1.2.5-1.pkvm2_1_1.20.19.ppc64
libvirt-1.2.5-1.pkvm2_1_1.20.19.ppc64
libvirt-client-1.2.5-1.pkvm2_1_1.20.19.ppc64
libvirt-daemon-qemu-1.2.5-1.pkvm2_1_1.20.19.ppc64
libvirt-python-1.2.5-1.pkvm2_1_1.1.ppc64

*** Domain define ***
<domain type='kvm'>
  <name>UbuntuCrypt</name>
  <uuid>7241b165-a0ff-47db-a8a8-40d941fe7fe5</uuid>
  <metadata>
    <kimchi:kimchi xmlns:kimchi="https://github.com/kimchi-project/kimchi">
      <kimchi:os version="14.10" distro="ubuntu"/>
    </kimchi:kimchi>
  </metadata>
  <memory unit='KiB'>4382720</memory>
  <currentMemory unit='KiB'>4382720</currentMemory>
  <vcpu placement='static'>5</vcpu>
  <resource>
    <partition>/machine</partition>
  </resource>
  <os>
    <type arch='ppc64' machine='pseries'>hvm</type>
    <boot dev='hd'/>
    <boot dev='cdrom'/>
  </os>
  <features>
    <acpi/>
    <apic/>
    <pae/>
  </features>
  <clock offset='utc'/>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>restart</on_crash>
  <devices>
    <emulator>/usr/bin/qemu-kvm</emulator>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='none'/>
      <source file='/var/lib/libvirt/images/vcd0a5/UbuntuCrypt.img'/>
      <backingStore/>
      <target dev='vda' bus='virtio'/>
      <alias name='virtio-disk0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
    </disk>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/var/lib/libvirt/images/kal/iso/ubuntu-14.10-server-ppc64el-GA.iso'/>
      <backingStore/>
      <target dev='sdc' bus='scsi'/>
      <readonly/>
      <alias name='scsi0-0-0-2'/>
      <address type='drive' controller='0' bus='0' target='0' unit='2'/>
    </disk>
    <controller type='usb' index='0'>
      <alias name='usb0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
    </controller>
    <controller type='pci' index='0' model='pci-root'>
      <alias name='pci.0'/>
    </controller>
    <controller type='scsi' index='0'>
      <alias name='scsi0'/>
      <address type='spapr-vio' reg='0x2000'/>
    </controller>
    <interface type='network'>
      <mac address='52:54:00:37:73:2e'/>
      <source network='default'/>
      <target dev='vnet21'/>
      <model type='virtio'/>
      <driver name='qemu'/>
      <alias name='net0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/>
    </interface>
    <serial type='pty'>
      <source path='/dev/pts/11'/>
      <target type='isa-serial' port='0'/>
      <alias name='serial0'/>
      <address type='spapr-vio' reg='0x30001000'/>
    </serial>
    <console type='pty' tty='/dev/pts/11'>
      <source path='/dev/pts/11'/>
      <target type='serial' port='0'/>
      <alias name='serial0'/>
      <address type='spapr-vio' reg='0x30001000'/>
    </console>
    <input type='mouse' bus='usb'>
      <alias name='input0'/>
    </input>
    <input type='keyboard' bus='usb'>
      <alias name='input1'/>
    </input>
    <input type='tablet' bus='usb'>
      <alias name='input2'/>
    </input>
    <graphics type='vnc' port='5904' autoport='yes' listen='0.0.0.0'>
      <listen type='address' address='0.0.0.0'/>
    </graphics>
    <video>
      <model type='vga' vram='9216' heads='1'/>
      <alias name='video0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
    </video>
    <memballoon model='virtio'>
      <alias name='balloon0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
      <stats period='890'/>
    </memballoon>
  </devices>
  <seclabel type='dynamic' model='selinux' relabel='yes'>
    <label>system_u:system_r:svirt_t:s0:c208,c245</label>
   <imagelabel>system_u:object_r:svirt_image_t:s0:c208,c245</imagelabel>
  </seclabel>
</domain>

[bugproxy (bugproxy)]

Default Comment by Bridge

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1387107/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1387107

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Liangchang Guo (vcd0a5)]

apport-collect bug: I am the owner who reported the original Bugzilla defect which was mirrored to this one. After I Authorized apport-collect to access Launchpad on my behalf, it just can not work.

To whom with the authorities: Please grant the ownership of this Launchpad defect to me for apport-collect to do its job:

root@UbuntuCrypt:/# apport-collect 1387107
*** Error: Updating problem report
You are not the reporter or subscriber of this problem report, or the report is a duplicate or already closed.
Please create a new report using "apport-bug".
Press any key to continue...

[Jhonny Oliveira (jhonny-oliveira)]

Maybe the same as this bug #1386836

[Liangchang Guo (vcd0a5)]

In reply to comment #5:

Perhaps we may consolidate these two defects. Both are for the same issue, and only have a few minor differences:
He was able to reach "Enter passphrase", but I could not get to that input form; He seemed unable to type upper case letters (bad TERM mode as I pointed out), while I could key in anything line after line (with echo but no response - same as his).

However, his was clearly stuck at luks password step, and my conclusion was based on my sense of reasoning (not really sure where the installation procedure was suspending).

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.18 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.18-rc2-utopic/

[Jhonny Oliveira (jhonny-oliveira)]

Yesterday night downloaded and installed suggested kernel. I must say that in the meawhile and before rebooting systemd also got updated to the latest at that time. The outcome was worst than before. There is no way I can enter the disk encrytpion password anymore. Tried previous kernel, same problem. I'm locked out!

[Launchpad Janitor (janitor)]

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