The same problem appears also in other configurations, not only with cloned live systems but with all Ubuntu live systems made with 19.10 and Focal Fossa. When running live-only (without the boot option 'persistent') the casper-rw partition will be mounted and busy.
I tested and verified the problem with
- a system extracted into a FAT32 file system, (that is samll in order to leave drive space behind it for a casper-rw partition. When running live-only (without the boot option 'persistent') the casper-rw partition will be mounted and busy.
- a system created with mkusb (where the casper-rw partition is already created). Also in this case, when selecting the live-only menuentry, the casper-rw partition will be mounted and busy.
The same problem appears also in other configurations, not only with cloned live systems but with all Ubuntu live systems made with 19.10 and Focal Fossa. When running live-only (without the boot option 'persistent') the casper-rw partition will be mounted and busy.
I tested and verified the problem with
- a system extracted into a FAT32 file system, (that is samll in order to leave drive space behind it for a casper-rw partition. When running live-only (without the boot option 'persistent') the casper-rw partition will be mounted and busy.
- a system created with mkusb (where the casper-rw partition is already created). Also in this case, when selecting the live-only menuentry, the casper-rw partition will be mounted and busy.