touch-packages team mailing list archive

[seond <2ndbase@xxxxxxxxxxxx>]

I had this problem too and while it still exists for me I have
identified a workaround that enables my system to boot. My issue was to
do with cryptsetup not accepting my password. This prevents me for
booting and fixing system issues.

Turns out that my password included a special character '@' as in
P@ssword. At the prompt pressing RIGHT SHIFT and key 2 does not generate
a '@' instead a '2' is generated. This can be confirmed by switching
over to another TTY and typing in the password (CTRL + ALT + F1). I
noted that using LEFT SHIFT and key 2 generated the '@' control
character. Thus if LEFT SHIFT is used in complex password it will be
typed correctly and cryptsetup will be able to decrypt the volume.

Note the Ubuntu install program rates user password with Poor, Fair, or
Good thus encouraging the use of special characters leading to this
scenario in the ubuntu recovery mode.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1273261

Title:
  Cryptsetup error during boot: /scripts/local-top/cryptroot: line 1:
  can't open /dev/mapper/ubuntu--vg-root: no such file

Status in cryptsetup package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  While booting cryptsetup outputs following error: /scripts/local-
  top/cryptroot: line 1: can't open /dev/mapper/ubuntu--vg-root: no such
  file, seems to be not related to this particular installation as saw
  the same output on other machines, also seems to be nothing major as
  everything boots fine, so just reporting to let you know it's there.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: cryptsetup 2:1.4.3-4ubuntu4
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Mon Jan 27 15:58:16 2014
  InstallationDate: Installed on 2014-01-18 (8 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
  MarkForUpload: True
  SourcePackage: cryptsetup
  UpgradeStatus: No upgrade log present (probably fresh install)
  crypttab: sda3_crypt UUID=68851a49-83a4-41eb-84c0-27d15280bbc1 none luks

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