Pages Menu
TwitterRssFacebook
Categories Menu

Posted by on Nov 17, 2013 in AWS, CloudLinux, cpanel/whm, hosting, tech |

AWS Server fails after cPanel install

AWS Server fails after cPanel install

So, you boot up your shiny new AWS CentOS 6 server, and run the cPanel installation script. Next you reboot the server… ever… and it never comes back online? My question to you: is your IP also licenced for CloudLinux?

When you install cPanel on any server, if your server’s primary IP address also has a current CloudLinux license, the cPanel installation will also install CloudLinux. Then, when you reboot, you’ll see a beautiful little kernel panic, like this:

[ 43.125106] dracut Warning: No root device "block:/dev/xvde" found
[ 43.128780] dracut Warning: Boot has failed. To debug this issue add "rdshell" to the kernel command line.
[ 43.128957] dracut Warning: Signal caught!
[ 43.131931] dracut Warning: Boot has failed. To debug this issue add "rdshell" to the kernel command line.
[ 43.132214] Kernel panic - not syncing: Attempted to kill init!
[ 43.132228] Pid: 1, comm: init veid: 0 Not tainted 2.6.32-458.18.1.lve1.2.39.el6.x86_64 #1

This is caused by a differentiation in drive detection in naming, described in detail here.

The Fix

To fix this is the simplest of simple. Start with one of the CloudLinux built images, and then follow their directions for completing your installation process.