Question

New droplet from an existing snapshot misses a network interface (Centos 6 x64)

Re,

I did a snapshot of my system, then created a new droplet using the snapshot and ended up without eth0. Running CentOS 6 x64.

Could be completely unrelated, but there’s a SUSE customer with a missing network interface as well: http://digitalocean.uservoice.com/forums/136585-digital-ocean/suggestions/3639542-put-a-priority-on-fixing-your-32-bit-suse-image


Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

The OpenSUSE image does have a few issues and that’s why we’ve taken it down for maintenance. Some of the smaller less supported distros need a few updates however CentOS and Ubuntu are the most popular and should be pretty rock solid. <br> <br>The issue that you ran into is very surprising and if you open a ticket about it we can move it to engineering and dive deeper into it to see if the problem recurs.

Thanks. Up until yesterday I have also not experienced any problems, having created and restored numerous snapshots of Centos 6. This is the first time (and, as luck would have it, a snapshot of the most configured and complete system) that the network configuration wasn’t properly restored. <br> <br>For those who happen to come across this issue, follows are some basic steps to configure networking: <br> <br>1) run “ifconfig -a” <br>1a) take note of the available “eth” interface and of its HWaddr (MAC) address <br>2) go to “/etc/sysconfig/network-scripts” and check for “ifcfg-ethX” (where X is the interface number from 0 to n) script. <br>2a) it exists but the number does not match the “eth” interface that you got from step 1a), then rename it to “ifcfg-eth[proper interface number]”, edit the file and replace the information inside (DEVICE, HWADDR, IPADDR, NETMASK and GATEWAY fields". <br>2a) if it doesn’t exist, then create it with the following content: <br> <br>DEVICE=“eth[proper interface number]” <br>HWADDR=XX:XX:XX:XX:XX:XX <br>IPADDR=192.XX.XX.XX <br>BOOTPROTO=none <br>ONBOOT=“yes” <br>DNS1=8.8.8.8 <br>NETMASK=255.255.255.0 <br>GATEWAY=192.XX.XX.XX <br>PREFIX=24 <br>TYPE=Ethernet <br>NM_CONTROLLED=“yes” <br> <br>3) reboot and profit.

I would get in touch with DO’s support department directly. I’ve not had any issues with snapshots or backups missing configurations, so it could simply be a blip in the system, or it could be a more widespread failure during the restoration. Either way, they should be able to help you directly via ticket,