Linux Administrator - eth0 not showing up on reboot

Linux Administrator

Privacy Policy

RSS Feed


Acoustic Guitar Tips
Anna Kendrick
Beekeeping Tips
BLISS
Carpentry
Catherine Zeta Jones
My View On Things
Cheap Auto Insurance
Cheap Places to Live
Delta Shaper
Easy Wood Projects
Felicity Jones
Free Sheet Music
Funny Clean Jokes
Healthy Carbs
Heidi Klum
Improve Your Credit
Ivory Tower Group
Keke Palmer
Linda Ronstadt
Linux Administrator
Money Spigot
Nicole Kidman
Planet Cabinet
Quality Dating Advice
Rustic Cabinets
Sacramento Hiking
Sandra Bullock
Spintax Tool
The Actress
Tristan Prettyman
Viola Davis
Who Are The Beatles


eth0 not showing up on reboot

eth0 not showing up on reboot

I had a server that failed, but I needed to get it back up and running as quickly as possible. That meant pulling the drives and putting them into a similar machine. Not a problem. Or so I thought...

I put the drives in the new machine and powered it on. And then, for some reason I couldn't figure out, Linux could not find eth0! I couldn't believe it. How could it not? It was the same hardware as the failed box, so it wasn't a matter of a missing driver or something like that. But, reboot after reboot, the thing refused the see eth0. Looking at the dump of dmesg, it even looked like it was loading the proper driver, so why wasn't it finding eth0? I hunted around the Internet a bit, and finally, I found the culprit. Being a slightly new installation of Debian Linux, it was using a /dev system that gets built when you set up the system the first time. And if there are any changes in hardware after that, forget about it finding the changes!

Luckily, the solution was simple. I looked for a directory called:

/etc/udev/rules.d/

In this directory is a file called z25_persistent-net.rules. All I needed to do was delete that file, then reboot. The system regenerates the file with new rules, based on the hardware it sees on the reboot.


Return To Main Page