Thanks for the update. Initial testing seems to indicate that the extra delaying appears to work, but I still need to check this out a bit more.
I will point out that during one boot (after rebooting the same machine a few times), I got the following fatal error: ln: /tmp/mountroot-fail-hooks.d/scripts/init-premount/lvm2: No such file or directory I've only seen it once so far, using the new initrd, and, at the moment, I don't exactly believe that this is related, but since it mentions mount scripts, I'm not entirely sure. Another thing I've been consistently observing (I'll open a new issue -- haven't had a chance to do that yet) is that, when persistence is active, and regardless of whether the partition is labelled 'casper-rw' or 'writeable', I'm seeing "access beyond end of device" for /dev/sda and "I/O error while writing superblock" for /dev/sda2 (peristent partition) on powerdown/reboot. On occasion, this actually seems to freeze powerdown altogether and I have to perform a hard reset, whereas none of this happens when persistence is not in used. If it can be replicated, you should see it if you follow the persistent partition process I gave above (again, using either 'writable' or 'casper-rw'). All this to say that it still seems to me like, even if you are doing a good job fixing problems, the persistent partition handling process of 20.04 appears to be a lot more brittle than it was in 19.10, so I would still advise you to consider reverting, and wait for a non LTS release to "upgrade" it... Oh I have to still URGE you do change your choice of introducing 'writable' as the newly allowed label for persistent partitions to 'persistence', which is what Debian and derivatives use. By supporting 2 labels, you have a unique opportunity to bridge a gap that has been causing a lot of pain for many Linux users, by UNIFYING the means in which users are advised to create a persistent partition, and finally stop this utter nonsense of having this or that distro doing something entirely different for persistence, when the fundamental underlying user-process (add option XYZ to the kernel boot options and create an ext# partition with label ABC) is the same and has no valid reason to deviate that much from one distro to another. So can you please at least switch to using 'persistence' instead of 'writable' for the 20.04 release? If you need additional validation that Debian Live uses 'persistence' as its persistent partition label (since, from regularly testing the automated persistent media creation process of my app with the latest Debian Live I believe I do have a pretty accurate view of what label Debian requires), you can find some at https://unix.stackexchange.com/a/538665/314167. I'll post some more about my testing as well as provide a link to that additional issue I'm planning to open when I get a chance. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863672 Title: The 'new' persistent live method starting in 19.10 no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1863672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
