CentOS 6.4 Cloning failed to load network card problem solving method

Source: Internet
Author: User
Tags custom name

a . Failure Phenomena:

[[Email protected] ~] #service Network restart

Shutting downloopback insterface: [OK]

Bringing Uploopback insterface: [OK]

Bringing Upinterface eth0:device eth0 does notseem to be present,delaying initialization. [FAILED]

Ii. Solutions

Law One:

Workaround:

[[Email protected] ~] #rm-rf/etc/udev/rules.d/70-persistent-net.rules

[[Email protected] ~] #reboot ....... .....

[[Email protected] ~] #service Network restart

Shutting downloopback insterface: [OK]

Bringing Uploopback insterface: [OK]

Bringing Up interfaceeth0: [OK]

Law II:

after installing a CentOS virtual machine, and another copy, the network card can not start normally after the boot, error: Device eth0 does not seem to be present,

Delayinginitialization

Solution: # mv/etc/sysconfig/network-scripts/ifcfg-eth0/etc/sysconfig/network-scripts/ifcfg-eth1

Vim/etc/sysconfig/network-scripts/ifcfg-eth1

Modify device= "Eth0"

to be device= "Eth1"

Then reboot the boot Nic and try

Fahsarm

in theRHEL5the same thing happens because copying a virtual machineMACis regenerated, but the operating system'sMACIt is written inIfcfg-ethxcauses inconsistencies, so the network interface cannot be started,RHEL5can be used inkudzuor note the network card configuration fileMACfield to resolve the problem. But inRHEL6inside,kudzuhave beenHalservice has been replaced. AlthoughLspciThe network card can be recognized correctly, but it cannot be used/etc/init.d/networkrestartto start the service. Try commentingIfcfg-eth0of theMACfield, or an error. Viewed the nextUdevthe rules and find out where the problem lies.

[[Email protected]~]# cat/etc/udev/rules.d/70-persistent-net.rules
# This file is automatically generated by the/lib/udev/write_net_rules
# program, run by the Persistent-net-generator.rules rules file.
#
# can modify it, as long as you keep each rule to a single
# line, and change is only the value of the Name= key.

#net device () (custom name provided by external tool)
subsystem== "NET", action== "Add", drivers== "? *", attr{address}== "08:00:27:16:31:11″, attr{type}==" 1″, KERNEL== "eth*" , name= "Eth0″

# NET device ()
subsystem== "NET", action== "Add", drivers== "? *", attr{address}== "08:00:27:32:66:63″, attr{type}==" 1″ , kernel== "eth*", name= "Eth1″
[[email protected] ~]#

original udev mac style= font-size:15px; Font-family:georgia, Serif;color:rgb (0,34,0); " >eth0mac 08:00:27:32:66:63 Yes eth1 mac

to solve this problem, just delete the old config, modified to:
[[email  Protected] ~]# cat/etc/udev/rules.d/70-persistent-net.rules
# This file is automatically generated by the/lib/udev/ Write_net_rules
# program, run by the Persistent-net-generator.rules rules file.
#
# can modify it, as long as you keep each rule to a single
# line, and the change is only the value of the Name= key.

# NET device () (custom name provided by external tool)
subsystem== "NET", action== "Add", drivers== "? *", attr{address}== " 08:00:27:32:66:63″, attr{type}== "1″, kernel==" eth* ", name=" Eth0″

restart network services can sometimes not, rebooting the system is all ok ! Tried many times!
[[email  Protected] ~]#/etc/init.d/network restart
Shutting down interface eth0: [OK]
shutting down loopback interface: [ OK]
Bringing up loopback interface: [OK]
bringing up interface eth0: [OK]

not really . reboot Restart, that's how I solve the problem.


This article is from "Try to be brave" blog, declined reprint!

CentOS 6.4 Cloning failed to load network card problem solving method

Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.