Argh, I bet I know what's happening... it's that damned tmpfs mount. On resolute, the /tmp directory was changed to a tmpfs mount with mandates to allow it to grab up to 50% of the RAM. Absolutely fine on a PC with 8GB+ of RAM, and a dreadful idea on anything with less than that. I really need to just disable that on the Pi images (either universally or with some simple check to disable it on any model with <8GB of RAM).
Anyway, let's confirm that's *actually* the problem first of all. Just unmounting /tmp is a bad idea (various things may have open handles to files under there) so we'll: * check that /tmp is a tmpfs mount * disable the tmp.mount * reboot * check /tmp is no longer a tmpfs mount * ensure sure something is scheduled to actually clean up /tmp still (it should be) * regenerate the initramfs * check its size is correct * copy it to the boot partition and ... fingers crossed ... reboot. findmnt /tmp Check this shows SOURCE is tmpfs. If it's not: stop here, my theory is wrong. Otherwise ... sudo systemctl disable tmp.mount sudo reboot findmnt /tmp This time findmnt should output nothing (and exit with an error). Switch to root for all the next steps. First we ensure something is configured to keep /tmp clean now that it's not a tmpfs. sudo -i echo "D /tmp 1777 root root 30d" > /etc/tmpfiles.d/tmp.conf Then we're going to regenerate *both* your initrds under /boot (because they're both truncated), and check their sizes: dracut --force /boot/initrd.img-7.0.0-1009-raspi 7.0.0-1009-raspi dracut --force /boot/initrd.img-7.0.0-1011-raspi 7.0.0-1011-raspi ls -lh /boot/initrd.img* Make sure the images are somewhere north of 60MB in size (not the few hundred KB they are now). Finally, write the new boot assets and reboot. flash-kernel reboot At this point ... *hopefully* you should be on the new assets! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2155094 Title: RPi 3B, Zero 2W, 4B: New boot assets in /boot/firmware/new failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2155094/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
