But after shutting down and starting up again, I am met with this screen. Booting into the previous version also results in the same error: timed out waiting for udev to rename interface(s)
Run into the same issue occasionally. As far as I know this is related to some underlying network interface issue. In most cases a restart solved it for me but sometimes I had to reset my network settings.
Properly best to file an issue on the IncusOS github providing as much details as you can. Did you try to reinstall and can you reproduce it?
I haven’t tried reinstalling yet, but I will if there aren’t any other options to try. Luckily there isn’t really any significant configuration that I would lose.
That normally means that an interface MAC address it’s looking for can’t be found.
My gut feeling here is that this machine may have a network interface with a dynamic MAC address, like a virtual network interface used for a BMC.
If that’s left in the network configuration, then you may hit that situation after reboot.
I’d recommend re-installing and when the server is online, go through incus admin os system network edit and make sure that your network configuration only touched the interfaces you actually care about, that should fix the issue of it not finding some interface on boot.
@gibmat we probably should better handle missing network interfaces 
I actually just hit this too in some of my testing; in my case it’s definitely triggered by a MAC change on the network interface.
IncusOS keys network configuration around MACs, since we typically don’t expect them to be changing on us. 
I’d have to think about how we can handle this – if an interface is configured but its MAC doesn’t match, maybe we could try to re-detect it based on the interface name? That would mirror how we handle interface-to-MAC mapping in the network seed, but would only work if the interface name still matches what the kernel sees.
I was going more after the, let’s complain loudly about it in log but move on and not fail the entire boot
That will at least make it clear what happened which in the case of VM will allow for it to be corrected (changing the MAC in the VM config) or on a physical system will let you know that you have a NIC that doesn’t have a stable MAC and that you shouldn’t rely on that NIC.
