CentOS 7 – “Device Eth1 Does Not Seem To Be Present, Delaying Initialization”.

Home » CentOS » CentOS 7 – “Device Eth1 Does Not Seem To Be Present, Delaying Initialization”.
CentOS 3 Comments

Hi All :)

I have three servers, all with CentOS 7 installed 3 days ago. I need on them “old” naming scheme (ethX) for network interfaces, because of that:

# grep GRUB_CMDLINE_LINUX /etc/sysconfig/grub GRUB_CMDLINE_LINUX=”rd.lvm.lv

3 thoughts on - CentOS 7 – “Device Eth1 Does Not Seem To Be Present, Delaying Initialization”.

  • Surprisingly:

    # lspci -vvv | grep ‘Device Serial Number’
    Capabilities: [140 v1] Device Serial Number 00-1e-67-ff-ff-7f-9c-98
    Capabilities: [140 v1] Device Serial Number 00-1e-67-ff-ff-7f-9c-98
    Capabilities: [140 v1] Device Serial Number 00-1e-67-ff-ff-7f-9c-98
    Capabilities: [140 v1] Device Serial Number 00-1e-67-ff-ff-7f-9c-98
    Capabilities: [148 v1] Device Serial Number 00-1e-67-03-00-81-37-0c
    Capabilities: [140 v1] Device Serial Number 90-e2-ba-ff-ff-46-ef-30
    Capabilities: [140 v1] Device Serial Number 90-e2-ba-ff-ff-46-ef-30

    So for mentioned eth1 which should have MAC 00:1e:67:7f:9c:99 there is no entry in lspci but for all 4 ports of Intel I350 the MAC in lspci seems to be the same :) First four lines above are for Intel I350 ethernet adapter and I suspect that some settings in bios could change due to some unknown reason, I will check this.

    BR, Rafal.

  • Hi Yamaban.

    Thanks for the tip, you pushed me in the right direction. I added udev rules file to initramfs:
    dracut -f –include /etc/udev/rules.d/70-persistent-net.rules
    /etc/udev/rules.d/70-persistent-net.rules and afterwards (reboot) it works as expected. Thanks!

    BR, Rafal.

    2015-10-21 12:55 GMT+02:00 Yamaban :

  • If you set net.ifnames=0 and still have trouble with names, then you’re probably fighting with biosdevname, which you should also disable.

    Yes, there are two subsystems that rename ethernet interfaces. It’s gross.

    Add “biosdevname=0″ to your kernel args, and the udev rules shouldn’t be necessary.

    If you decide to keep the systems as they are, you should probably reboot several times to make sure the problem is actually fixed. It was intermittent before, and it may still be present.

    Otherwise, you can configure dracut to always include a file by creating
    /etc/dracut.conf.d/persistent-net.conf with one line:

    install_items+=”/etc/udev/rules.d/70-persistent-net.rules”