how to fix a start job is running for wait for network to be configured
The ACTUAL solution is to set the adapters to optional, removing the need of an active DHCP lease or other services on the interface.
if you use a radhat based distro:
by linux-syr
windows server dhcp
Thank you for making this video
the .yuml file was named differently for me, however it was the right solution. ty
I did this in the moon and it 💪
I was trying to solve this since somany days. excellent solution thank you very much😀
hello i'm on rocky minimal iso and when i do ctrl alt delete and hold shift after i don't see the recovery mode is this normal ???
Hello sir do I need internet connection while doing this
Hello sir
When I put all that code my system say new file or new line
It didn't show like yours
Six line
Help me
After ctrl+x when I wrote what you said there was an error saying version 2 not found or undifind
Worked for me (Ubuntu server 23.04). I am using WiFi and the system was waiting for the unconnected ethernet port to come up with a connection.
You're a savior
When I try to boot my ubuntu, it sticks at the loading page and shows "A start job is running for load kernel modules"
How to fix this issue
0:38 Holding Shift key to get recovery mode is not working
Thx alot 🙂, this fixed my slow ubuntu clone vm boot.
This fix does not work on Ubuntu 23.04!
Thanks!
Thx
Unfortunately this doesn't fix the real issue. It just tells Ubuntu it doesn't have to have that network. If that is the only network connection you have and it is not working for some ??? reason, this just leaves you with no network at all, still.
bro thx a lot, my ubuntu server now starts 5x faster xd
thank you
I don't even have a netplan folder. Is this only for ubuntu?
Worked beautifully for me. The problem was that the system was waiting for an unused ethernet connection to come up. This fix tells the system that it's optional.
Thanks!
Obrigado 🙂
Thanks, this fixed my issue.
Bro what for hp laptop
thanks
Good information but this wasn't the problem in my case. I have two physical NICs on the MB. Only one has a cable connected but both have: dhcp4: true set. The solution in this case is, though I haven't tried it yet, to set the NIC without a cable connected to 'false'. Or I'm assuming that's the case.
I'd also mention that I would think that setting the adapter to 'optional' is going to cause some serious issues if you have NAS drives mounted with nfs. Particularly if you have your /home/<user_name> directories on a NAS. Those can't be mounted until the network is 'up'. If it's taking a long time for your network to come up you have problems other than this one.
Great info on where to find the relevant file, though. Honestly, that's usually most of the problem when you're trying to correct something, "What file do I need to edit to fix this?"
Thanks for the useful info!
Et voilà ! Thanks
thanks