Bug#793906: linux-image-3.16.0-4-amd64: Fails to boot
On 2015-07-28 23:11, Ben Hutchings wrote:
> This is very likely a bug in one of the packages that goes into the
> initramfs, not in the kernel.
>
> Which versions of cryptsetup and lvm2 are installed?
Thanks for the quick reply!
2:1.6.6-5 and not installed, respectively. I'll attach more in case it
helps.
> Please boot in recovery mode and send a picture of the screen when you
> get to the shell.
OK, will send later, have to wait for my camera battery to charge up.
Thanks,
--
Nick
Script started on Wed 29 Jul 2015 07:27:57 BST
nick@nickpad$ dpkg --status cryptsetup
Package: cryptsetup
Status: install ok installed
Priority: optional
Section: admin
Installed-Size: 365
Maintainer: Debian Cryptsetup Team <pkg-cryptsetup-devel@lists.alioth.debian.org>
Architecture: amd64
Version: 2:1.6.6-5
Replaces: cryptsetup-luks, hashalot (<< 0.3-2)
Provides: cryptsetup-luks
Depends: libc6 (>= 2.15), debconf (>= 0.5) | debconf-2.0, dmsetup, cryptsetup-bin (>= 2:1.6.0)
Recommends: kbd, console-setup, initramfs-tools (>= 0.91) | linux-initramfs-tool, busybox | busybox-static
Suggests: dosfstools, liblocale-gettext-perl, keyutils
Breaks: hashalot (<< 0.3-2)
Conflicts: cryptsetup-luks
Conffiles:
/etc/bash_completion.d/cryptdisks 758d5cfcd9df55c82a7bb094728114b5
/etc/default/cryptdisks 756141f7eacf1a272a2f6e51646b3aa4
/etc/init.d/cryptdisks 20b58baefc1aed5021a28e2fb9439edd
/etc/init.d/cryptdisks-early 9c58f4b1314fe50c79ec0caff22bf298
/etc/init/cryptdisks-udev.conf ed789690d1770e3f3a2682c11e359bb6
/etc/init/cryptdisks.conf e5527ceb5c020174a6464b81126bb5f7
Description: disk encryption support - startup scripts
Cryptsetup provides an interface for configuring encryption on block
devices (such as /home or swap partitions), using the Linux kernel
device mapper target dm-crypt. It features integrated Linux Unified Key
Setup (LUKS) support.
.
Cryptsetup is backwards compatible with the on-disk format of cryptoloop,
but also supports more secure formats. This package includes support for
automatically configuring encrypted devices at boot time via the config
file /etc/crypttab. Additional features are cryptoroot support through
initramfs-tools and several supported ways to read a passphrase or key.
Homepage: http://code.google.com/p/cryptsetup/
nick@nickpad$
nick@nickpad$ dpkg --status lvm2
Package: lvm2
Status: deinstall ok config-files
Priority: optional
Section: admin
Installed-Size: 1624
Maintainer: Debian LVM Team <pkg-lvm-maintainers@lists.alioth.debian.org>
Architecture: amd64
Multi-Arch: foreign
Version: 2.02.111-2.2
Config-Version: 2.02.111-2.2
Depends: libc6 (>= 2.15), libdevmapper-event1.02.1 (>= 2:1.02.74), libdevmapper1.02.1 (>= 2:1.02.90), libreadline5 (>= 5.2), libudev1 (>= 183), init-system-helpers (>= 1.18~), lsb-base, dmsetup (>> 2:1.02.47), dmeventd (>> 2:1.02.90), initscripts (>= 2.88dsf-13.3)
Suggests: thin-provisioning-tools
Breaks: initramfs-tools (<< 0.99), thin-provisioning-tools (<< 0.3.2)
Conffiles:
/etc/init.d/lvm2 70063dce3a90eca5ef673579e5fcc402
/etc/lvm/lvm.conf c3219a98322101a8c4d20497ad3d4bee
Description: Linux Logical Volume Manager
This is LVM2, the rewrite of The Linux Logical Volume Manager. LVM
supports enterprise level volume management of disk and disk subsystems
by grouping arbitrary disks into volume groups. The total capacity of
volume groups can be allocated to logical volumes, which are accessed as
regular block devices.
Homepage: http://sources.redhat.com/lvm2/
nick@nickpad$ exit
exit
Script done on Wed 29 Jul 2015 07:28:18 BST
Reply to: