Xenial server install fails with "targeted" initrd

Bug #1571592 reported by Tom Hager
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
initramfs-tools (Ubuntu)
New
Undecided
Unassigned

Bug Description

Hi,

I've been testing the Xenial Beta2 server ISO in our VMware environment and stumbled across
an issue with the "targeted" initrd option. I tested normal and minimal setup, with generic
and virtual kernels, but whenever I choose to use a targeted initrd, Xenial install fails when
configuring the kernel.

I tested again with the latest daily build (17.4.) today, and the issue is still there.

In the logs I found the following:

Apr 18 09:26:21 in-target: Examining /etc/kernel/postinst.d.^M
Apr 18 09:26:21 in-target: run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-18-generic /boot/vmlinuz-4.4.0-18-generic^M
Apr 18 09:26:21 in-target: run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-18-generic /boot/vmlinuz-4.4.0-18-generic^M
Apr 18 09:26:21 in-target: update-initramfs: Generating /boot/initrd.img-4.4.0-18-generic^M
Apr 18 09:26:21 in-target: mkinitramfs: failed to determine device for /^M
Apr 18 09:26:21 in-target: mkinitramfs: workaround is MODULES=most, check:^M
Apr 18 09:26:21 in-target: grep -r MODULES /etc/initramfs-tools/^M
Apr 18 09:26:21 in-target: ^M
Apr 18 09:26:21 in-target: Error please report bug on initramfs-tools^M
Apr 18 09:26:21 in-target: Include the output of 'mount' and 'cat /proc/mounts'^M
Apr 18 09:26:21 in-target: update-initramfs: failed for /boot/initrd.img-4.4.0-18-generic with 1.^M
Apr 18 09:26:21 in-target: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1^M
Apr 18 09:26:21 in-target: Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-4.4.0-18-generic.postinst line 1052.

So here I am reporting the issue, with the requested output:

mount:
/var/log # mount
rootfs on / type rootfs (rw,size=495168k,nr_inodes=123792)
none on /run type tmpfs (rw,nosuid,relatime,size=100748k,mode=755)
none on /proc type proc (rw,relatime)
none on /sys type sysfs (rw,relatime)
devtmpfs on /dev type devtmpfs (rw,relatime,size=495184k,nr_inodes=123796,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
/dev/sr0 on /cdrom type iso9660 (ro,relatime)
/dev/sda1 on /target type ext4 (rw,relatime,errors=remount-ro,data=ordered)
/dev/sr0 on /target/media/cdrom type iso9660 (ro,relatime)

/proc/mounts:
/var/log # cat /proc/mounts
rootfs / rootfs rw,size=495168k,nr_inodes=123792 0 0
none /run tmpfs rw,nosuid,relatime,size=100748k,mode=755 0 0
none /proc proc rw,relatime 0 0
none /sys sysfs rw,relatime 0 0
devtmpfs /dev devtmpfs rw,relatime,size=495184k,nr_inodes=123796,mode=755 0 0
devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
/dev/sr0 /cdrom iso9660 ro,relatime 0 0
/dev/sda1 /target ext4 rw,relatime,errors=remount-ro,data=ordered 0 0
/dev/sr0 /target/media/cdrom iso9660 ro,relatime 0 0

I'll keep the VM at it's current state, so I can always gather more information.

Cheers,
Tom.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.