Comment 17 for bug 1958260

Hi.

I was also hit by this issue.

I think I did something like follows:

[1] I booted the Ubuntu system from an external kernel and initrd.
[2] copymods mounted tmpfs because /root/lib/modules/$(uname -r) was missing.
[3] I installed a new linux-module package by running "sudo dpkg -i <package>" or "sudo apt upgrade".
[4] The modules from that package were installed onto the tmpfs, hence lost after the reboot.
[5] I booted the Ubuntu with the new kernel, but modules are missing, and copymods is active again.

Maybe it is my "mis-administrating the system".

Once you get into a situation that activates copymods, the problem is sticky - you cannot fix it by rebooting the system or by reinstalling a kernel because /lib/modules/ is hidden by tmpfs.

Perhaps, people might want the kernel parameter "copymods=disable" instead of "copymods=force".

I do not think there is much situation to enable it forcibly, but there is good reason, as many people reported, to disable it forcibly.

Anyway, I did "sudo apt remove cloud-initramfs-copymods" to avoid stumbling on this again.