Control: reassign -1 cloud-initramfs-growroot 0.18.debian8 On Thu, Aug 19, 2021 at 02:24:36PM +0200, Josef Dean Butler wrote: > Package: initramfs-tools > Version: 0.140 > Severity: important > > Dear Maintainer, > > *** Reporter, please consider answering these questions, where appropriate *** > > * What led up to the situation? > During the upgrade from buster to bullseye dpkg failed to init the RAM fs. > dpkg --configure -a always led to the same output: > Selecting previously unselected package linux-image-5.10.0-8-amd64. > (Reading database ... 51840 files and directories currently installed.) > Preparing to unpack .../linux-image-5.10.0-8-amd64_5.10.46-4_amd64.deb ... > Unpacking linux-image-5.10.0-8-amd64 (5.10.46-4) ... > Selecting previously unselected package linux-image-amd64. > Preparing to unpack .../linux-image-amd64_5.10.46-4_amd64.deb ... > Unpacking linux-image-amd64 (5.10.46-4) ... > Setting up linux-image-5.10.0-8-amd64 (5.10.46-4) ... > I: /vmlinuz.old is now a symlink to boot/vmlinuz-5.10.0-8-amd64 > I: /initrd.img.old is now a symlink to boot/initrd.img-5.10.0-8-amd64 > I: /vmlinuz is now a symlink to boot/vmlinuz-5.10.0-8-amd64 > I: /initrd.img is now a symlink to boot/initrd.img-5.10.0-8-amd64 > /etc/kernel/postinst.d/initramfs-tools: > update-initramfs: Generating /boot/initrd.img-5.10.0-8-amd64 > E: /usr/share/initramfs-tools/hooks/growroot failed with return 1. > update-initramfs: failed for /boot/initrd.img-5.10.0-8-amd64 with 1. > run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 > dpkg: error processing package linux-image-5.10.0-8-amd64 (--configure): > installed linux-image-5.10.0-8-amd64 package post-installation script > subprocess returned error exit status 1 > dpkg: dependency problems prevent configuration of linux-image-amd64: > linux-image-amd64 depends on linux-image-5.10.0-8-amd64 (= 5.10.46-4); > however: > Package linux-image-5.10.0-8-amd64 is not configured yet. > > * What exactly did you do (or not do) that was effective (or > ineffective)? > > Since the kernel panicked during reboot I had to boot an emergency > environment. I mounted my drives and chrooted into them. I checked, if enough > space was available on the SSD. I tried to re-install initramfs-tools and the > kernel. None helped. A friend discovered that the path for udevadm was wrong > in /usr/share/initramfs-tools/hooks/growroot > . We changed it from /sbin/udevadm to /bin/udevadm and then dpkg --configure > -a worked wirhout errors and the new kernel was installed. A reboot brought > back the system to live. > > * What was the outcome of this action? > Changing the path for udevadm solved the issue completely. dpkg --configure > -a worked again and I could boot just fine.
The hook is shipped by the cloud-initramfs-growroot package, so reassigning there. Regards, Salvatore
