[pkg-cryptsetup-devel] Bug#774700: initramfs-tools: Cryptsetup tools are not included by update-initramfs command
Michaël P.
aleph-g+deb at parienti.net
Mon Jan 19 11:06:10 UTC 2015
Hi,
On [2015-01-19 11:06:06], Jonas Meurer wrote:
> Hi Michael,
>
> On Tue, 06 Jan 2015 14:40 "Michael P." wrote:
> > The update-initramfs command create a initrd.img without cryptsetup
> > tools, but my root partition is crypted.
> >
> > I tried to debug a little the
> > /usr/share/initramfs-tools/hooks/cryptroot file and found that the
> > add_device() function returned an empty string, when passing
> > /faith--vg-root as first argument.
> >
> > I am on a new machine. Everything was fine after a fresh install from
> > jessie beta 2 installer. But after an update, the machine didn't
> > reboot anymore: grub halted after "Waiting for root device".
>
> I changed the logic of add_device() recently in order to fix another
> bug. I fear that you discovered a new bug that I introduced by these
> changes.
>
> In order to help me to better understand what is going on, please do the
> following (as root, on the broken system):
>
> 1) append '-x' to the end of the first line at
> /usr/share/initramfs-tools/hooks/cryptroot, so that it is: '#/bin/sh -x'.
>
> 2) execute '/usr/sbin/mkinitramfs -o /tmp/initrd.img-$(uname -r) $(uname
> -r) >/tmp/mkinitramfs_debug.log 2>&1'
>
> 3) send /tmp/mkinitramfs_debug.log to this bugreport.
>
> 4) change the first line of /usr/share/initramfs-tools/hooks/cryptroot
> back to '#/bin/sh' (i.e. remove the trailing '-x').
>
> 5) remove the created files: 'rm /tmp/initrd.img-$(uname -r)
> /tmp/mkinitramfs_debug.log'.
I am sorry, but I couldn’t wait so I re-installed every thing. And now I
don’t get the probleme anymore.
For now, every thing works fine with the following versions:
ii cryptsetup 2:1.6.6-4 amd64 disk encryption support - startup
ii cryptsetup-bin 2:1.6.6-4 amd64 disk encryption support - command
ii initramfs-tool 0.118 all generic modular initramfs generat
ii libcryptsetup4 2:1.6.6-4 amd64 disk encryption support - shared
The diffences between the two installations I made is that I was more
careful with the second one: I updated packages, and installed new ones step
by step, with several reboots after each big steps.
The first installation was more "brute":
1. Installation with jessie installer beta 2
2. Reboot
3. Remove systemd
4. Reboot
5. Upgrade to Sid
6. Installation of a lot of packages
7. Reboot
8. Bug #774700
Tell me if I still can helpfull,
Cheers,
--
Michaël P.
gpg: D4C8 F73D A000 71C7 44EF 27E6 8982 4991 7126 3CE3
More information about the pkg-cryptsetup-devel
mailing list