Same errors came up after reboot, but it seemed to progress past it anyway. Here's a boot.log after the updates, still quite clearly showing the failure to map the partition but seemingly eventually succeeding and getting past it (rather quickly too, actually):
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... Reading all physical volumes. This may take a while... Found volume group "vmhost2lvmg1" using metadata type lvm2 3 logical volume(s) in volume group "vmhost2lvmg1" now active /scripts/local-top/cryptroot: line 1: can't open /dev/mapper/vmhost2lvmg1-2--root: no such file done. Begin: Running /scripts/local-premount ... done. Begin: Running /scripts/local-bottom ... done. done. Begin: Running /scripts/init-bottom ... done. * Starting Read required files in advance^[[154G[^[[31mfail^[[39;49m] * Starting Mount filesystems on boot^[[154G[ OK ] * Starting Fix-up sensitive /proc filesystem entries^[[154G[ OK ] * Stopping Fix-up sensitive /proc filesystem entries^[[154G[ OK ] * Starting Populate /dev filesystem^[[154G[ OK ] * Starting Populate and link to /run filesystem^[[154G[ OK ] * Stopping Populate /dev filesystem^[[154G[ OK ] * Stopping Populate and link to /run filesystem^[[154G[ OK ] * Stopping Track if upstart is running in a container^[[154G[ OK ] * Starting Signal sysvinit that the rootfs is mounted^[[154G[ OK ] * Stopping Read required files in advance (for other mountpoints)^[[154G[ OK ] * Starting Clean /tmp directory^[[154G[ OK ] * Stopping Clean /tmp directory^[[154G[ OK ] * Stopping Read required files in advance (for other mountpoints)^[[154G[ OK ] * Starting Initialize or finalize resolvconf^[[154G[ OK ] * Starting set console keymap^[[154G[ OK ] * Starting Signal sysvinit that virtual filesystems are mounted^[[154G[ OK ] * Starting Signal sysvinit that virtual filesystems are mounted^[[154G[ OK ] * Starting Bridge udev events into upstart^[[154G[ OK ] * Starting Signal sysvinit that local filesystems are mounted^[[154G[ OK ] * Starting Signal sysvinit that remote filesystems are mounted^[[154G[ OK ] * Starting Flush boot log to disk^[[154G[ OK ] * Starting flush early job output to logs^[[154G[ OK ] * Stopping Mount filesystems on boot^[[154G[ OK ] * Stopping Flush boot log to disk^[[154G[ OK ] * Stopping flush early job output to logs^[[154G[ OK ] * Starting Bridge file events into upstart^[[154G[ OK ] * Stopping set console keymap^[[154G[ OK ] * Starting device node and kernel event manager^[[154G[ OK ] * Starting load modules from /etc/modules^[[154G[ OK ] * Starting cold plug devices^[[154G[ OK ] * Starting log initial device creation^[[154G[ OK ] * Starting D-Bus system message bus^[[154G[ OK ] * Stopping load modules from /etc/modules^[[154G[ OK ] * Starting SystemD login management service^[[154G[ OK ] * Starting system logging daemon^[[154G[ OK ] * Starting Uncomplicated firewall^[[154G[ OK ] * Starting configure network device security^[[154G[ OK ] * Starting configure network device security^[[154G[ OK ] * Starting Mount network filesystems^[[154G[ OK ] * Starting Failsafe Boot Delay^[[154G[ OK ] * Stopping Mount network filesystems^[[154G[ OK ] * Starting Bridge socket events into upstart^[[154G[ OK ] * Starting enable encrypted block devices^[[154G[ OK ] * Starting configure network device^[[154G[ OK ] * Starting Mount network filesystems^[[154G[ OK ] * Stopping Mount network filesystems^[[154G[ OK ] * Starting configure network device^[[154G[ OK ] * Stopping Failsafe Boot Delay^[[154G[ OK ] * Stopping enable encrypted block devices^[[154G[ OK ] * Starting System V initialisation compatibility^[[154G[ OK ] * Starting System V runlevel compatibility^[[154G[ OK ] * Starting ACPI daemon^[[154G[ OK ] * Starting dovecot - pop3/imap mail server^[[154G[ OK ] * Starting save kernel messages^[[154G[ OK ] * Starting configure network device security^[[154G[ OK ] * Starting regular background program processing daemon^[[154G[ OK ] * Starting deferred execution scheduler^[[154G[ OK ] * Stopping save kernel messages^[[154G[ OK ] * Starting CPU interrupts balancing daemon^[[154G[ OK ] * Starting configure virtual network devices^[[154G[ OK ] * Starting automatic crash report generation^[[154G[ OK ] * Starting OpenSSH server^[[154G[ OK ] * Starting Postfix Mail Transport Agent postfix ^[[160G ^M^[[154G[ OK ] * Starting MD monitoring service mdadm --monitor ^[[160G ^M^[[154G[ OK ] * Restoring resolver state... ^[[160G ^M^[[154G[ OK ] * Stopping System V runlevel compatibility^[[154G[ OK ] -- 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
