The journal you've attached unfortunately doesn't show timing information for anything that happened before systemd started, so it's impossible to say what is causing a 20-minute delay (the timestamps in the journal only cover a 3-minute period). Would it be possible for you to also attach the output of 'dmesg' from after one of these 20-minute boots, so that we can see where the kernel is spending its time before the root filesystem is mounted?
Also, there are these very strange entries in the journal: oct 21 16:46:22 ubuntu kernel: EXT4-fs (sda6): INFO: recovery required on readonly filesystem oct 21 16:46:22 ubuntu kernel: EXT4-fs (sda6): write access will be enabled during recovery oct 21 16:46:22 ubuntu kernel: random: crng init done oct 21 16:46:22 ubuntu kernel: EXT4-fs (sda6): orphan cleanup on readonly fs oct 21 16:46:22 ubuntu kernel: EXT4-fs (sda6): 24 orphan inodes deleted oct 21 16:46:22 ubuntu kernel: EXT4-fs (sda6): recovery complete oct 21 16:46:22 ubuntu kernel: EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null) [...] oct 21 16:46:22 ubuntu kernel: EXT4-fs (sdb4): mounted filesystem with ordered data mode. Opts: (null) [...] I know of no reason that we should be mounting ext4 filesystems from the host system prior to actually starting the installer. That seems like a casper bug. But given that you had an ext4 filesystem that required journal recovery, that could certainly contribute to the boot taking some time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900715 Title: The initial screen of Plymouth takes 20 minutes to appear (Groovy live) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1900715/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
