This bug was fixed in the package initramfs-tools - 0.130ubuntu3.3
---
initramfs-tools (0.130ubuntu3.3) bionic; urgency=medium
[ Scott Moser ]
* scripts/functions: write netplan config files to /run/netplan for
network devices configured with configure_networking. (LP:
Verification-done on bionic with initramfs-tools 0.130ubuntu3.3:
Verified that with the SRU applied, the initramfs configured to use
MODULES=dep can still determine that the root is over ZFS, and
accordingly add the files needed in the initramfs.
** Description changed:
[Impact]
- Ubuntu
@Mathieu, thanks for your work on this.
Regarding the test cases, I think that the second case needs an
additional step:
-- initramfs update --
1) install Ubuntu, using ZFS as a rootfs.
2) change 'MODULES=most' to 'MODULES=dep' in /etc/initramfs-tools/initramfs.conf
3) run "sudo update-initramfs
Thank you for your work. I will test.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1661629
Title:
upgrade of kernel fails with mkinitramfs: failed to determine device
for /
To manage
Hello Fredrik, or anyone else affected,
Accepted initramfs-tools into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/initramfs-
tools/0.130ubuntu3.3 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
** Also affects: initramfs-tools (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1661629
Title:
upgrade of kernel fails with mkinitramfs:
This bug was fixed in the package initramfs-tools - 0.131ubuntu9
---
initramfs-tools (0.131ubuntu9) cosmic; urgency=medium
[ John Gallagher ]
* Work out the kernel modules required to support ZFS filesystems and add
them as necessary. (LP: #1661629)
-- Mathieu
@John, I've uploaded initramfs-tools with your patch to both cosmic and
18.04. Now, for the process of stable release updates [1]; we do need
test cases and what is likely to break in case of a regression. I've
added this to the best of my knowledge, but I don't have any systems
with ZFS -- given
** Changed in: initramfs-tools (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1661629
Title:
upgrade of kernel fails with mkinitramfs: failed to
The attachment "mkinitramfs.patch" seems to be a patch. If it isn't,
please remove the "patch" flag from the attachment, remove the "patch"
tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the
team.
[This is an automated message performed by a Launchpad user owned by
** Patch added: "mkinitramfs.patch"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1661629/+attachment/5162606/+files/mkinitramfs.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
> It might be easier to resolve this by considering this as "mkinitramfs
fails on ZFS root without /etc/fstab lines for the ZFS filesystems when
MODULES=dep is used".
Yes, that sounds like an accurate summary. I'm not sure I follow how
/etc/fstab is related, though. Looking briefly through
I can reproduce this on my 18.04 laptop with zfs on root.
kdump-tools.postinst ends up calling /etc/kernel/postinst.d/kdump-tools
4.15.0-23-generic, which fails at this mkinitramfs line:
mkinitramfs -d /var/lib/kdump/initramfs-tools -o
/var/lib/kdump/initrd.img-4.15.0-23-generic.new
My fstab has only an entry for /boot/efi. Everything else is zfs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1661629
Title:
upgrade of kernel fails with mkinitramfs: failed to determine device
On Wed, Jul 04, 2018 at 01:21:35AM -, John Gallagher wrote:
> > I'm not particularly familiar with this part of initramfs-tools, but
> it seems to me that essentials like the loading of the virtio_pci module
> would be short-circuited by your patch.
>
> Yes, you're right, thanks for pointing
> I'm not particularly familiar with this part of initramfs-tools, but
it seems to me that essentials like the loading of the virtio_pci module
would be short-circuited by your patch.
Yes, you're right, thanks for pointing that out. If the driver isn't
built-in to the kernel, it would be omitted.
I was just pointed to
https://github.com/zfsonlinux/zfs/wiki/Ubuntu-18.04-Root-on-ZFS and told
that ZFS filesystems aren't expected to be in /etc/fstab according to
those instructions. Is this correct? I haven't checked but it seems that
initramfs-tools wouldn't then fail under these conditions.
Thank you for taking the time to file this patch and helping to make
Ubuntu better.
Does this apply and work correctly on the current Ubuntu development
release (Cosmic) please? We land changes there first and only once
successful consider backporting to existing releases as appropriate.
> With
Maybe there is something better, but it seems like the simplest change
that would fix this would be something along the lines of the patch
below. This just assumes that if the filesystem type is listed as zfs
then it actually is zfs, and it adds the zfs module. With this change I
was able to build
The problem is the bash function dep_add_modules_mount in /usr/share
/initramfs-tools/hook-functions which doesn't handle zfs.
By adding "MODULES=most" to /usr/share/initramfs-tools/conf-hooks.d/zfs,
the error goes away.
I'm still having trouble getting kdump to actually create a crash dump
with
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: initramfs-tools (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1661629
21 matches
Mail list logo
