Comment 18 for bug 1958260

Revision history for this message
Stefan (stsichler) wrote (last edit ):

Hi,

I'm also affected by this bug on my RasPi in exactly the same way Masahiro wrote.
In my case, it was initally caused by an incomplete/aborted kernel update (because of a disk full error) which temporarily caused the kernel version and modules version to become inconsistent, so copymods correctly switched itself on at reboot and now I'm stuck, because all re-installs of the modules and all further module updates end up in copymods tmpfs.
The only way to escape that situation seems to manually unmount the copymods tmpfs from /lib/modules and then 'apt install --reinstall' the current linux-modules(-extra) packages.

I think in order to mitigate this bug in the first place, the /usr/share/initramfs-tools/scripts/init-bottom/copymods script may be adapted to mount the initramfs modules in a tmpfs on /lib/modules/$(uname -r) only instead of whole /lib/modules.
This way, the situation would at least be automatically fixed by the next kernel update, because the updated linux-modules(-extra) packages would no longer decompress into the copymods tmpfs.