Issues reproducible with ubuntu-20.04.4-live-server-amd64.iso.
Apparently, ctrl-c does not stop the integrity check anymore
because casper-md5check runs as systemd service/disconnected
from plymouth. Per [1], iiuic. -- Well, this is _not_ a bug.
So, fsck.mode=skip is the only option available.
However, there's a bug in casper-md5check that ignores that
_if_ it is the last option in /proc/cmdline (likely, if the
user adds it after '---' or deletes '---' to insert it.)
Workaround: make sure to add fsck.mode=skip before '---'.
Patch proposed [2], with technical details and testing.
Issues reproducible with ubuntu- 20.04.4- live-server- amd64.iso.
Apparently, ctrl-c does not stop the integrity check anymore disconnected
because casper-md5check runs as systemd service/
from plymouth. Per [1], iiuic. -- Well, this is _not_ a bug.
So, fsck.mode=skip is the only option available.
However, there's a bug in casper-md5check that ignores that
_if_ it is the last option in /proc/cmdline (likely, if the
user adds it after '---' or deletes '---' to insert it.)
Workaround: make sure to add fsck.mode=skip before '---'.
Patch proposed [2], with technical details and testing.
[1] https:/ /launchpad. net/ubuntu/ +source/ casper/ 1.457 /code.launchpad .net/~mfo/ casper/ +git/casper/ +merge/ 417120
[2] https:/