Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
08-10-2013, 09:41 AM
|
#1
|
Senior Member
Registered: Feb 2004
Location: lost+found
Distribution: CentOS
Posts: 1,430
Rep:
|
Can't bring up eth0 or eth1 after replacing main harddrive (centos)
I replaced the harddrive on my box with one with centos preinstalled (the previous drive with centos went bad).
However it would not let me bring up any of the eth interfaces and would give the error:
Code:
]#ifup eth0
Device eth0 does not seem to be present, delaying initialization.
If there a way to get it to recognize the interfaces without reinstalling the OS?
TIA
|
|
|
08-10-2013, 09:54 AM
|
#2
|
Senior Member
Registered: Feb 2011
Location: Massachusetts, USA
Distribution: Fedora
Posts: 4,269
|
Post the output of
and
Code:
cat /etc/sysconfig/network-scripts/ifcfg-eth0
|
|
|
08-10-2013, 10:05 AM
|
#3
|
Senior Member
Registered: Feb 2004
Location: lost+found
Distribution: CentOS
Posts: 1,430
Original Poster
Rep:
|
# ifconfig -a
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:16436 Metric:1
RX packets:435612 errors:0 dropped:0 overruns:0 frame:0
TX packets:435612 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:206646569 (197.0 MiB) TX bytes:206646569 (197.0 MiB)
# cat ifcfg-eth0
DEVICE="eth0"
NM_CONTROLLED="yes"
ONBOOT=yes
TYPE=Ethernet
BOOTPROTO=none
IPADDR=11.11.11.11
PREFIX=24
GATEWAY=11.11.11.1
DNS1=8.8.8.8
DNS2=8.8.8.8
DOMAIN=domain.com
DEFROUTE=yes
IPV4_FAILURE_FATAL=yes
IPV6INIT=no
NAME="System eth0"
|
|
|
08-10-2013, 11:02 AM
|
#4
|
Senior Member
Registered: Feb 2011
Location: Massachusetts, USA
Distribution: Fedora
Posts: 4,269
|
Hmm.. looks like no driver for your ethernet. What hardware do you have?
Easiest way to check is
|
|
|
08-10-2013, 11:32 AM
|
#5
|
Senior Member
Registered: Feb 2004
Location: lost+found
Distribution: CentOS
Posts: 1,430
Original Poster
Rep:
|
# lspci |grep Ether
0d:00.0 Ethernet controller: Intel Corporation 82573E Gigabit Ethernet Controller (Copper) (rev 03)
0f:00.0 Ethernet controller: Intel Corporation 82573L Gigabit Ethernet Controller
|
|
|
08-10-2013, 11:51 AM
|
#6
|
Senior Member
Registered: Feb 2011
Location: Massachusetts, USA
Distribution: Fedora
Posts: 4,269
|
Please try:
Code:
modprobe e1000
ifconfig -a
|
|
|
08-23-2013, 10:45 PM
|
#7
|
LQ Newbie
Registered: Aug 2013
Posts: 2
Rep: 
|
Have you found the solution yet?
A lot of times if /etc/sysconfig/network-scripts/ifcfg-eth* has a detailed "static" configuration it will not work on any other box as is... being preconfigured, I'm guessing this is the issue.
|
|
|
08-27-2013, 05:48 AM
|
#8
|
Member
Registered: Aug 2010
Location: Netherlands
Distribution: Kubuntu, Debian, Suse, Slackware
Posts: 317
Rep:
|
The OP stated that he installed a new harddisk with an pre-installed OS. I bet he's having problems with udev rules.
@abe Check in /etc/udev/rules.d. There should be a net-persistent rules file. Remove all references to the eth devices and restart your system.
Cheers
|
|
|
08-28-2013, 02:27 PM
|
#9
|
LQ Newbie
Registered: Feb 2010
Posts: 27
Rep:
|
Quote:
Originally Posted by abefroman
I replaced the harddrive on my box with one with centos preinstalled (the previous drive with centos went bad).
However it would not let me bring up any of the eth interfaces and would give the error:
Code:
]#ifup eth0
Device eth0 does not seem to be present, delaying initialization.
If there a way to get it to recognize the interfaces without reinstalling the OS?
TIA
|
yes you can remove 70-persistent-net.rules in cd /etc/udev/rules.d/ and must restart the box.
|
|
|
All times are GMT -5. The time now is 02:58 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|