Package: initramfs-tools
Version: 0.120
Followup-For: Bug #784234
Hi, I also still got this error, after purged and reinstalled btrfs-tools.
$ sudo update-initramfs -u
update-initramfs: Generating /boot/initrd.img-3.16.0-4-amd64
cryptsetup: WARNING: failed to detect canonical device of /dev/sda3
On Sun, May 10, 2015 at 10:26:36AM +0800, Adam Lee wrote:
Package: initramfs-tools
Version: 0.120
Followup-For: Bug #784234
Hi, I also still got this error, after purged and reinstalled btrfs-tools.
$ sudo update-initramfs -u
update-initramfs: Generating /boot/initrd.img-3.16.0-4-amd64
reopen 784234
thanks
Hi Dimitri, hi Ben,
On Mon, 04 May 2015, Ben Hutchings wrote:
If fsck can find fsck.$fstype anywhere in $PATH then mkinitramfs should
do so too. But it would be helpful for you to move it back until we fix
mkinitramfs. Thanks.
On Mon, 04 May 2015, Dimitri John Ledkov
Package: initramfs-tools
Version: 0.120
Severity: important
With the update of btrfs-tools to 4.0-1 I get this:
update-initramfs: Generating /boot/initrd.img-4.1.0-rc2
Warning: /sbin/fsck.btrfs doesn't exist, can't install to initramfs, ignoring.
and indeed, the changelog states
btrfs-tools
Thanks for this.
I will check the previous /sbin/ binaries and move them back to sbin
location.
There was a change of build system upstream as well, and I thought i got
the splits right.
Thanks for pointing this out.
On 4 May 2015 at 11:42, Norbert Preining prein...@logic.at wrote:
On Mon, 2015-05-04 at 18:20 +0100, Dimitri John Ledkov wrote:
Thanks for this.
I will check the previous /sbin/ binaries and move them back to sbin
location.
There was a change of build system upstream as well, and I thought i
got the splits right.
Thanks for pointing this out.
On 4 May 2015 at 19:25, Ben Hutchings b...@decadent.org.uk wrote:
On Mon, 2015-05-04 at 18:20 +0100, Dimitri John Ledkov wrote:
Thanks for this.
I will check the previous /sbin/ binaries and move them back to sbin
location.
There was a change of build system upstream as well, and I
7 matches
Mail list logo
