Monday, January 28, 2013

9 How to fix “Device eth0 does not seem to be present, delaying initialization.”

After clone the VM within Virtual box, I receive the error message “

Device eth0 does not seem to be present, delaying initialization.” when start the network service.

image

The /etc/sysconfigu/network-scripts/ifcfg-eth0 does exist. The issue is that the network device eth0 is non longer exist. The VM clone processes create the new device eth1.

The device file is at /sys/class/net.

ip link show

image

We can rename the device by using the up command.

ip link set eth1 name eth0

image

After the device being renamed, we can successfully bring up the network interface.

9 comments:

  1. I tried to rename but 'RTNETLINK answers: Device or resource busy '
    how can i fix?
    Please help me

    ReplyDelete
  2. hi i THOUGHT i have same problem as you..
    but when i saw the result of command, i got "Device "eth0" does not exist."
    actually, i've tried to remove all of the files in a folder somewhere because of some blogs..
    but after that, my network is totally broken.
    now.. i'm eager to turn it back..
    please, any advice will be appreciated.
    thank you

    ReplyDelete
  3. Delete networking interface rules file so that it can be regenerated and reboot your CentOS system.

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

    ReplyDelete
  4. Try the below command it worked for me
    # ifdown eth0
    # rm /etc/sysconfig/network-scripts/ifcfg-eth0
    # rm /etc/udev/rules.d/70-persistent-net.rules
    # reboot

    ReplyDelete
  5. thank you for replying.
    fortunately i've solved the problem somehow..
    I can't be sure but as my memory, I might setup another CentOS machine and copied the network interface files
    or.. I just typed "setup" and reset the configuration.

    anyway, again, thank you for your replies you guys

    ReplyDelete
  6. This comment has been removed by the author.

    ReplyDelete
  7. Hi,

    Its solved my problem temporally. But the same thing is reoccurred once system reboot.

    Please help me with permanent solution.

    Regards,
    Tarak Nath

    ReplyDelete
  8. I done all this but is not working is show the same error again

    (Process: 3566 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=1/FAILURE

    ReplyDelete
  9. Melbourne Motorcycle Accident Attorney I would like to thank you for your nicely written post, its informative and your writing style encouraged me to read it till end. Thanks

    ReplyDelete

 

SQL Panda Copyright © 2011 - |- Template created by O Pregador - |- Powered by Blogger Templates