Eric Nieuwenhuijsen

This happens for me as well on the latest gen instances. Switching instances from t2 and t3 results into the system hanging on a systemd unit that's waiting for device...

Fetched one of the logs from the machines, I see lots of these messages: ``` [* ] (1 of 3) A start job is running for dev-xvdg.device (4s / 1min...

> @enieuw Hey... how did you get that system log? My AWS EC2 system logs are blank :( It takes a while but eventually they show up under "Instance Settings...

Creating a VM as a t2 instance and then changing the instance type to t3 works, I actually see the symlinks working: ``` Container Linux by CoreOS stable (1855.4.0) core@ip-10-14-30-4...

Yeah most likely. It doesn't trigger the wait for the systemd unit and then it does continue booting. If I specify /dev/nvme1n1 in my ignition file it does boot properly....