Solved

Cannot find device "ethx" No such device

Posted on 2013-11-06
6
3,600 Views
Last Modified: 2013-11-16
Hello,

I have created a perfect ready install of Ubuntu 14.04 (newest build) and it works just fine on the system it was installed on.

I have cloned that drive and wish to use it on other servers.  However when I am using it for the next machine I have no Ethernet cards.

When I type: ifup eth0 or ifup eth1 I get the reply:

Cannot find device "ethx" Error getting hardware address for "ethx": No such device

I have tried removing: /etc/udev/rules.d/70-persistent-net.rules
I have tried checking the mac address of a card with lspci -v and inserted a visible mac into 70-persistent-net.rules but still nothing

Clearly when Ubuntu installs initially, it figures out the right Ethernet driver to get things going.  How can I reinitialize that process without reinstalling Ubuntu again.

I have two ethernet cards and it's not loading the correct driver for either one.

Screenshots attached of
lspci -v on two ethernet cards
results of ifconfig -a
contents of /etc/network/interfaces

Strangely, ifconfig -a shows strange entries of em1 and p3p1 instead of ethx.

The virbr0 returned in ifconfig -a is expected due to virtual machine needs

What sayeth the group ?

Jay
CompuMatter
ifconfig-a.jpg
interfaces.jpg
lspci-v.jpg
0
Comment
Question by:Jay Lepore
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 2
6 Comments
 
LVL 13

Expert Comment

by:Daniel Helgenberger
ID: 39628352
Hello Jay,
on your Ubuntu you have something called 'bios-device-name' active, like on most modern linux sytems. These make the udev rules obsolete.
Your LAN dev is then something like p3s1.

Background: In the past, udev was initiating devices, including network devs, all at the same time. This led to strange race conditions, having non-persistent network device names if you had more than one NIC installed. Imagine, you had a fixed IP on eth0 and after a reboot eth0 was eth5.
This was really a huge issue; udev persistent rules was a way to workaround this problem. With bios-device-names this is history, it names network devices after their PCI bus port.

See also;
https://linux.dell.com/files/whitepapers/consistent_network_device_naming_in_linux.pdf

Also, I am not sure if you can use ifup/down on U14. Anyway, try for lan:
ifup p3s1

Open in new window

Note, network manager is normally used to configure interfaces, here the cli command, but you better use the GUI:
nmcli dev connect iface p3s1

Open in new window

0
 

Author Comment

by:Jay Lepore
ID: 39628646
Hello and thank you.

This is Ubuntu Server so there no GUI to use.

nmcli is not installed and I cannot install it because I have no internet ;-)

I have two computers. Though one shows p3pi and em1 the other one does not show these things.  

I understand and am grateful for your statements about udev.  However, they do not offer a solid fix to this problem.

At the moment, lspci can see the card but ifconfig sees no ethx

How to resolve ?

Jay
0
 
LVL 13

Assisted Solution

by:Daniel Helgenberger
Daniel Helgenberger earned 200 total points
ID: 39628721
When you cloned the drives, the Ethernet cards are named different, please see above.

So, let's start with the one you made the photos:
You have two Ethernet controllers; one is the e1000e, the other is the igb module. Since I cannot know in which one the LAN cable ends, put both devices in /etc/interfaces. Just rename eth0 to em1 and eth1 to p3s1 everywhere there and leave the rest. I can only tell so far: em1 is an embedded (onboard) NIC device while p3s1 is a PCI add in card; is this info is of any help. Note, I have seen this is a Supermicro system; so em1 might be the Lights Out / OOB - Management port.

So edit /etc/interfaces as you think best, save, and try:
ifup em1
ifup p3s1

Open in new window


One interface will now acquire an address via DHCP.  If you do not have NM installed, do all your configs with /etc/interfaces - this is fine.
0
Don't Cry: How Liquid Web is Ensuring Security

WannaCry is just the start. Read how Liquid Web is protecting itself and its customers against new threats.

 

Author Comment

by:Jay Lepore
ID: 39631132
I have done as you suggested, unfortunately it still did not get us online.  

I am finding out as you suggested that the naming convention of eth0, eth1 etc is changing.

So, I am still stuck.  Will have to do further research online unless you have other idea.

Jay
0
 

Accepted Solution

by:
Jay Lepore earned 0 total points
ID: 39640096
I have resolved this issue and documented the solution here: http://wiki.linuxmatter.com/index.php/Virtual_Servers:central

helge000 gave me a sense of direction as I did not know it could ever be anything except eth0 eth1 etc... I did not know this had changed.

Anyway, thank you for trying.
0
 

Author Closing Comment

by:Jay Lepore
ID: 39653049
Because the thoughts of one provided an inspiration but not a cure. Much work lay ahead in finding the solve.
0

Featured Post

Ransomware-A Revenue Bonanza for Service Providers

Ransomware – malware that gets on your customers’ computers, encrypts their data, and extorts a hefty ransom for the decryption keys – is a surging new threat.  The purpose of this eBook is to educate the reader about ransomware attacks.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

I am a long time windows user and for me it is normal to have spaces in directory and file names. Changing to Linux I found myself frustrated when I moved my windows data over to my new Linux computer. The problem occurs when at the command line.…
Using 'screen' for session sharing, The Simple Edition Step 1: user starts session with command: screen Step 2: other user (logged in with same user account) connects with command: screen -x Done. Both users are connected to the same CLI sessio…
Connecting to an Amazon Linux EC2 Instance from Windows Using PuTTY.
Get a first impression of how PRTG looks and learn how it works.   This video is a short introduction to PRTG, as an initial overview or as a quick start for new PRTG users.

724 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question