Take the 2-minute tour ×
Ask Ubuntu is a question and answer site for Ubuntu users and developers. It's 100% free, no registration required.

Every time I restart my Ubuntu Server 11.10 I can't ssh into it because ETH0 doesn't come up automatically. I never had this problem before upgrading to 11.10. I have to login to the server and start the ETH0 manually. I would appreciate it any help. Thanks.

Here is my /etc/network/interfaces file:

#The loopback network interface
auto lo eth0
iface lo inet loopback

# The primary network interface

iface eth0 inet static
    address 192.168.1.102
    netmask 255.255.255.0
    broadcast 192.168.1.255
    network 192.168.1.0
    gateway 192.168.1.1
share|improve this question
1  
Hi Joel, there was a change made in 11.10 to make sure that the system doesn't go into runlevel 2 before all interfaces have come up. Can you add to the question the output of ls -lR /run/network ? Thanks! –  SpamapS Nov 9 '11 at 17:43
    
I have the same problem, upgrade to 11.10 and eth0 does not start –  user35625 Nov 27 '11 at 16:12
add comment

5 Answers

Joel, add a line with auto eth0 before the iface eth0 inet static line, that should bring it up on boot.

share|improve this answer
    
SpamapS, the command didn't run..joel@Snoopy:/etc/network$ sudo ls -lR /run/network ls: cannot access /run/network: No such file or directory.... then i deleted the /network and it ran but the output was too long to paste here. –  LLR Nov 10 '11 at 1:31
1  
If you run "sudo ifconfig eth0 up" when you log in on console, it brings up the interface? Can you grep for eth0 in /var/log/syslog or dmesg and paste any interesting output that you get? –  deej Nov 10 '11 at 4:07
    
@deej +1, fixed me up. –  hydroparadise Jun 18 '12 at 23:54
add comment

found a link with the answer.

It seems the move from /var/run to /run did not work during the upgrade process.

I fixed with this:

cd /var mv run _run ln -s /run .

share|improve this answer
add comment

Well, as it says, it could not find /run/network. That's why it doesn't start with /etc/init.d/networking start

I have the same problem, just a few days ago and still trace the failure since the directory gets destroyed every reboot.

If you simply create the /run/network directory you'll be able to start the network with a configured ethX but you'll lose it again next reboot. I haven't figured out what service is so persistent to destroy my work every time. Try it, creating a directory can't hurt too much.

share|improve this answer
    
It's not that anyone or anything is deleting your directory. /run is usually stored in RAM (filesystem type tmpfs) so it isn't persistent over reboots. –  bseibold Jan 18 '13 at 23:27
add comment

I had, and solved, a similar problem--perhaps my solution will work for you. The problem in my case was that in /etc/network/interfaces I had both eth0 and vin to auto as shown below:

# The primary network interface
auto eth0
iface eth0 inet dhcp

# The INside Virtual Network
auto vin
iface vin inet dhcp
bridge_ports eth0
bridge_stp off
bridge_fd 0
bridge_maxwait 0

After I commented out the first line, changing it to

#auto vin

the eth0 worked.

share|improve this answer
add comment

Just ran across this webpage http://pingbin.com/2011/02/ubuntu-eth0-missing-after-reboot/ it seems to make a lot of sense, check it out.

share|improve this answer
1  
Whilst this may theoretically answer the question, it would be preferable to include the essential parts of the answer here, and provide the link for reference. –  Mahesh Aug 11 '12 at 12:21
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.