Eth0 won't start up and unable to change kernel

Posted on March 12, 2015

Configuration Management

CentOS

Logging

Control Panels

DigitalOcean

By toepoke

My CentOS droplet rebooted this morning and now networking won’t start up. I get the following error:

FATAL:Could not load /lib/modules/2.6.32-358.6.2.el6.x86_64/modules.dep: No such file or directory

Sure enough, there is no /lib/modules/2.6.32-358.6.2.el6.x86_64 directory. It appears that kernel isn’t available on the server. The available kernels are:

2.6.32-431.5.1.el6.x86_64
2.6.32-431.11.2.el6.x86_64
2.6.32-431.17.1.el6.x86_64
2.6.32-431.20.3.el6.x86_64
2.6.32-504.3.3.el6.x86_64

I shut down the droplet (via “poweroff”) and went into DO’s control panel to change the kernel. I tried each of these kernels but the droplet won’t even boot up. The only way I can get it to boot up is by using my original kernel (2.6.32-358.6.2). The funny thing is – this kernel doesn’t appear in /boot/ and there isn’t a directory for it in /lib/modules/.

So I have a few questions:

Why does it power up with 2.6.32-358.6.2 (which is not on the server)?
Why won’t it power up with those other kernels (which are available on the server)?
Is there some sort of log file so I can see what happens when it fails to boot up with one of the other kernels?

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!

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.

kgolebiowski

May 1, 2015

Hello everybody, I’ve just upgraded Centos with yum upgrade and I spotted exactly the same problem - the eth0 interface does not start because of some strange errors. I’m currently recovering the machine using my last snapshot (created just before update) but it seems to be a critical issue that has not been fixed yet (although the thread is more than one month old!). @toepoke Did they fixed only your machine? Do you have the ticket number?

Regards, KG