Comment 17 for bug 1732028

I worked on the two messages and related boot messages:
1. the ordering cycle is about media-root, maybe the config is not yet perfect
2. timeouts on
     dev-ttyS0.device
     dev-disk-by\x2dlabel-UEFI.device
Hmm, that is:
  Dependency failed for /boot/efi.
  Dependency failed for Local File Systems.
  local-fs.target: Job local-fs.target/start failed

I checked for network coming up and was first confused between
  systemd[1]: Failed to start Network Service.
And network in general coming up very late.
In a log:
  eth0: DHCPv4 address 10.0.12.15/24
  systemd-networkd[529]: eth0: Configured
In one of my cases ~10 minutes later than I got into the emergency console.

Afterwards boot-efi.mount autocompleted just fine btw.

Early boot is a swarm of red herrings:
I was checking more like
  Started Remount Root and Kernel File Systems.
before
  Started Network Service
It seems the latter just depends on time synchronization and therefore waits.
  Reached target Network is Online.
is before it as it should be.

And as trivial as that may sound, the network seems to be related at least.
Of all the logs only the good cases reach:
  Reached target Network is Online
But that is only reachable after local-fs which in the bad case fails - so it is ok to not be reached if the root is missing.

I also checked if the ordering changed e.g. compared to Bionic?
But it seemed - at least for network init similar in old bad&good cases.

Arr - early boot dependencies are lovely :-)
Following a discussion about fstab modifications next ...