CentOS中Device eth0 does not seem to be present错误解决办法

直接复制了Oracle VM VirtualBox的镜像文件vdi 可以直接创建新的系统镜像真是方便,不过遇到了
Device eth0 does not seem to be present 的问题,在网上找到遇到同样问题的解决方法,
很顺利的解决,记录之:

ifconfig…没有看到eth0.。然后重启网卡又报下面错误。

故障现象:

service network restart
Shutting down loopback insterface: [ OK ]
Bringing up loopback insterface: [ OK ]
Bringing up interface eth0: Device eth0 does not seem to be present,delaying initialization. [FAILED]

CentOS Linux解决Device eth0 does not seem to be present

解决办法:
 
 
首先,打开/etc/udev/rules.d/70-persistent-net.rules内容如下面例子所示:

# vi /etc/udev/rules.d/70-persistent-net.rules
# This file was automatically generated by the /lib/udev/write_net_rules
# program, run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single
# line, and change only the value of the NAME= key.
# PCI device 0×1022:0×2000 (pcnet32)
SUBSYSTEM==”net”, ACTION==”add”, DRIVERS==”?*”, ATTR{address}==”08:00:27:7e:8c:e7″, ATTR{type}==”1″, KERNEL==”eth*”, NAME=”eth0″
# PCI device 0×1022:0×2000 (pcnet32)
SUBSYSTEM==”net”, ACTION==”add”, DRIVERS==”?*”, ATTR{address}==”08:00:27:30:c2:57″, ATTR{type}==”1″, KERNEL==”eth*”, NAME=”eth1″

记录下,eth1网卡的mac地址08:00:27:30:c2:57

接下来,打开/etc/sysconfig/network-scripts/ifcfg-eth0

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

将 DEVICE=”eth0″ 改成 DEVICE=”eth1″ ,
将 HWADDR=”08:00:27:7e:8c:e7″ 改成上面的mac地址 HWADDR=”08:00:27:30:c2:57″

最后,重启网络

# service network restart
或者

# /etc/init.d/network restart

正常了,搞定

时间: 2024-09-06 01:23:27

CentOS中Device eth0 does not seem to be present错误解决办法的相关文章

Android 中读取SD卡文件时抛出NullPointerException错误解决办法

Android 中读取SD卡文件时抛出NullPointerException错误解决办法 相关源码: package com.example.musicplayer; import java.io.File; import java.util.ArrayList; import java.util.List; import android.app.Activity; import android.os.Bundle; import android.os.Environment; import

CentOS Linux解决网卡启动时候报Device eth0 does not seem to be present错误

  在VMware里克隆出来的CentOS Linux.. ifconfig...没有看到eth0..然后重启网卡又报下面错误. 故障现象: service network restart Shutting down loopback insterface: [ OK ] Bringing up loopback insterface: [ OK ] Bringing up interface eth0: Device eth0 does not seem to be present,delay

js中form.submit()提交object is not a function错误解决办法

form.submit()提交时报错object is not a function 在写表单提交时遇到一个很扯淡的问题,分享一下. 比如有个表单,其中某元素的id为submit,像下面这样写: <input id="submit" type="xxx" /> 即,如果在表单某元素中,设置了一个id名为submit的元素, 然后在使用form.submit()进行提交表单时, 表单无动作,浏览器控制台中会提示一个js错误: Uncaught TypeEr

CentOS Linux解决Device eth0 does not seem to be present

一,问题描述 在VMware里克隆出来的CentOS Linux.. ifconfig...没有看到eth0..然后重启网卡又报下面错误. 故障现象: service network restart Shutting down loopback insterface:                                                   [ OK ] Bringing up loopback insterface:                          

centos网卡错误Device eth0 does not seem to be present

在使用vmware及VirtualBox迁移linux系统过程中,发现部署后的linux系统无法启动网卡 报错为 Bringing up interface eth0: Device eth0 does not seem to be present,delaying initialization 错误原因,是因为linux网卡绑定了原mac地址导致   解决方法为 1.使用ifcnfig -a 查看当前主机mac地址 2.修改eth0网卡硬件地址为当前地址 vi /etc/sysconfig/n

Linux解决Device eth0 does not seem to be present

  CentOS Linux解决Device eth0 does not seem to be present 在VMware里克隆出来的CentOS Linux.. ifconfig...没有看到eth0..然后重启网卡又报下面错误. 故障现象: 解决办法: 首先,打开/etc/udev/rules.d/70-persistent-net.rules内容如下面例子所示: # vi /etc/udev/rules.d/70-persistent-net.rules # This file was

Linux 克隆虚拟机引起的“Device eth0 does not seem to be present, delaying initialization”

虚拟机Vmware上克隆了一个Red Hat Enterprise Linx启动时发现找不到网卡,如下所示,如果你在命令窗口启动网络服务就会遇到"Device eth0 does not seem to be present, delaying initialization"错误 关于这个错误,搜索了一下网上的资料,发现还蛮多人遇到过这类错误,了解了一下错误产生的原因和解决方案   错误原因:         克隆的Linux系统在新的机器上运行,新服务器网卡物理地址已经改变.而/et

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

执行 service network restart  出现了网卡无法启动,说找到不到 Bringing up interface eth0: Device eth0 does not seem to be present, delaying initialization 解决办法: 1> 修改/etc/udev/rules.d/70-persistent-net.rules文件,删除或注释掉第一个网卡记录,并将第二个的NAME="eth1"改为NAME="eth0&q

Linux出现&quot;Device eth0 does not seem to be present&quot;问题解决办法

这个问题的出现是继"Linode通过克隆平移服务器系统和数据以及保留IP地址"在迁移机房数据的时候出现的,以前我也有记得玩过迁移数据到不同的机房,也没有出现这样的问题.这次在迁移完毕之后IP地址PING不同,而且也链接不上SSH,开始我以为是数据迁移不完整导致的,后来一想数据不完整与IP不通是没有关系的,肯定是MAC地址配置问题导致的.   还好Linode VPS服务器有"Lish via Browser"功能,可以通过WEB模式登入进入,查看是不是有错误.