Corresponding initrd.img not created on update

I reported this as a bug but I post the bug report here for reference or if there is a work around. It’s got to the point where I can’t adopt 17.04 amd64 without resolving this issue as I can’t have a broken system every time the kernal decides to update.


Whenever mate updates vmlinuz the corresponding initrd.img is not created and thus boot fails with kernal panic unable to mount the root directory.

From example on an update from yesterday a link in the root for vmlinuz is created pointing to boot/vmlinuz-4.10.0-26-generic. That file exists. A link for initrd.img is also created pointing to boot/initrd.img-4.10.0-26-generic but the initrd.img ramdisk was not created and the file does not exisit in the /boot directory.

This happens on every install mate 17.04 no matter the machine. If I delete the vmlinuz for which no initrd.img exists then I can bt to the previous version for which initrd.img exists but as soon as mate decides (and I never authorize this update so not sure why it happens) to update vmlinuz then the issue occurs again.

Since it happens every time vmlinuz is updated and on every machine it seems like a bug in the updater. I have NEVER had this issue with any install of linux mint nor ubuntu server, nor in the RPi mate version. Only with this particular 17.04 amd64 mate version