Comment 4 for bug 1863672

Hmm. You're almost certainly right that it was the casper upload that caused this.

I changed casper so that it creates a filesystem with the label "writable" but it should still mount a pre-existing filesystem with label "casper-rw" (and there are autopkgtests that it does this). There could be a race in this area I suppose.

Can I get you to try a few things?

1. attach casper.log from a failing boot (possibly after adding verbose to the kernel command line)
2. change your script to create a filesystem with label writable instead and see if that works