Comment 46 for bug 1863672

Hi, I've uploaded yet another initrd -- I think this one might fix the bug, hopefully. It seems that for whatever reason, it takes a long time for the block device to show up at all in your system (seems it's more the kernel being slow rather than udev lagging behind which is what I suspected at first). It also I guess means that the chances of encountering this bug might depend on the model of the motherboard of the system or something equally crazy.

So what I've done is to just delay the check for the /dev/disk/by-label/casper-rw to later. It's a bit unsatisfactory but I'm reasonably confident this will work (because if the device hasn't appeared by this point, persistence would not work with a writable filesystem label either). Please let me know how it goes.