Home Linux troubleshooting How To Solve “Device eth0 does not seem to be present, delaying initialization” Error

How To Solve “Device eth0 does not seem to be present, delaying initialization” Error

By sk
Published: Updated: 83.3K views

The other day, I encountered with a strange error after I cloned a CentOS 6 guest machine in Oracle VirtualBox. After logging in to the CentOS guest, I noticed that the network card is disappeared. I can't SSH into the CentOS guest anymore.

I checked the IP address using command:

# ifconfig

Sample output:

 lo Link encap:Local Loopback 
 inet addr:127.0.0.1 Mask:255.0.0.0
 inet6 addr: ::1/128 Scope:Host
 UP LOOPBACK RUNNING MTU:65536 Metric:1
 RX packets:0 errors:0 dropped:0 overruns:0 frame:0
 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
 collisions:0 txqueuelen:0 
 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

As you see in the above output, the eth0 config details is not displayed. It only shows the details of the loopback interface.

I tried to restart the network service to sort out the issue.

# service network restart

Nothing! It simply displayed the following error.

Bringing up interface eth0: Device eth0 does not seem to be present, delaying initialization
Bringing up interface eth0: Device eth0 does not seem to be present, delaying initialization
Error Message - Bringing up interface eth0: Device eth0 does not seem to be present, delaying initialization

I thought that there could be any misconfiguration in network configuration file. So, I decided to look into the eth0 configuration file to make sure if everything is correct.

# vi /etc/sysconfig/network-scripts/ifcfg-eth0

Sample output:

DEVICE=eth0
BOOTPROTO=none
DEVICE=eth0
GATEWAY=192.168.1.1
HWADDR=08:00:27:DC:33:3F
IPADDR=192.168.1.150
NETMASK=255.255.255.0
NM_CONTROLLED=no
ONBOOT=yes
TYPE=Ethernet
USERCTL=no
View Network card configuration file
View Network card configuration file

Everything seems OK.

Again, I tried to bring Network card up using command:

# ifup eth0

But, still no luck! It keeps showing the same error message as shown below.

Device eth0 does not seem to be present, delaying initialisation
Device eth0 does not seem to be present, delaying initialisation
Error Message - Device eth0 does not seem to be present, delaying initialisation

I added an additional virtual network interface card and configured it. I restarted network service and CentOS guest several times. But, nothing helped. I keep getting the same error over and over.

After a bit searching on web, I found the solution. The MAC address is the problem! After cloning the CentOS VM, the CentOS guest was still using the old machine's MAC address in the Virtual machine settings.

Solve "Device eth0 does not seem to be present, delaying initialization" error

If you ever encountered with the same issue, you can fix it as described in the following two methods.

Method 1:

To fix this problem, simply remove the file /etc/udev/rules.d/70-persistent-net.rules and reboot your system.

# rm /etc/udev/rules.d/70-persistent-net.rules

Now, you will see the network card is up.

Method 2:

If the problem is still not solved, open up the eth0 config file:

# vi /etc/sysconfig/network-scripts/ifcfg-eth0

Note down the MAC id (HWADDR).

[...]
HWADDR=08:00:27:DC:33:3F
[...]
eth0 config file
View eth0 config file

Close the file. Then, power off the CentOS guest and go to Settings -> Network -> Adapter 1 -> Advanced from VirtualBox menu bar.

Replace the old MAC id and update it with new one.

Update virtual machine's mac id in virtualbox
Update virtual machine's mac id in virtualbox

After changing the MAC address, Click OK to save it. and power on your guest.

Now, Check if the network card is up using command:

# ifconfig
ifconfig command output
ifconfig command output

That's it. It worked!

Reference link:

You May Also Like

39 comments

Kevin December 15, 2020 - 10:02 pm

May I recommend editing ifcfg-ethx to change the MAC address to match VMware’s generated address instead of the other way around. This helps avoid having a duplicate MAC in your VMware infrastructure if you were to use vCenter to clone a VM.

Reply
Md. Zahirul Islam May 15, 2021 - 10:34 pm

Thank you so much, It worked with the last solution.

Reply
aviad October 24, 2021 - 3:16 pm

Very good. helped me alot

Reply
Dan December 22, 2022 - 5:50 pm

many thanks, great article!

Reply
1 2 3 4

Leave a Comment

* By using this form you agree with the storage and handling of your data by this website.

This site uses Akismet to reduce spam. Learn how your comment data is processed.

This website uses cookies to improve your experience. By using this site, we will assume that you're OK with it. Accept Read More