Bug#708722: initramfs-tools: update-initramfs fails with btrfs
On 11/02/2015 05:05, Ben Hutchings wrote:
> On Wed, 2015-02-11 at 03:04 +0000, jnqnfe wrote:
>> I think that my issues might all stem from initramfs-tools, so
>> reassigning.
> I don't think so - other packages hook into initramfs-tools and are
> quite capable of breaking it.
I see, I wasn't aware of that.
> What are the error messages?
When executing update-initramfs -u in a chroot via a live CD, I get:
update-initramfs: Generating /boot/initrd.img-3.16.0-4-amd64
cryptsetup: WARNING: could not determine root device from /etc/fstab
Warning: /sbin/fsck.btrfs doesn't exist, can't install to initramfs,
ignoring.
<perl locale warnings>
More details of the setup are described in the following mailing list
message (please ignore issue #1), including fstab, crypttab contents and
blkid output:
https://lists.debian.org/debian-user/2015/02/msg00323.html
(please excuse the use of '<etc>' in the UUID's, I couldn't be bothered
to type them all out in full)
The filesystem after installation does contain an install of cryptsetup,
just no copy in initrd. I added 'cryptsetup' into the
/etc/initramfs-tools/modules file before executing update-initramfs -u,
resulting in the above output, and no cryptsetup binary or config files
present in the /boot initrd image.
>> Secondly, the other issue I believe is due to the initrd created by
>> debian-installer missing at least cryptsetup; I believe
>> debian-installer runs update-initramfs towards the end, so perhaps
>> this is where debian-installer is trying to add things like cryptsetup
>> to initrd, and it is actually silently failing here due to same issue
>> above.
> initramfs-tools doesn't make that decision - cryptsetup does. And if
> cryptsetup isn't installed or configured properly, that's the fault of
> partman-crypto.
I'm not going to dispute whether the fault lies with initramfs-tools or
partman-crypto, because I don't have a clue.
All I know at this time is that comparing two VM installs, one using
luks + btrfs and one using luks + ext4, otherwise identical, the btrfs
one lacks cryptsetup in its initrd after installation, causing boot
failure, while the ext4 one is fine, and using a live CD + chroot to try
to fix things via update-initramfs, the tool runs fine on the ext4
install, but fails on the btrfs install. I am guessing that both
problems have a common cause.
Thank you for taking some time to respond to my issue. I appreciate any
help you can offer in resolving it.
Reply to: