EC2 kernel decision and issues with creating a new machine with my AMI

Posted by roacha on Server Fault See other posts from Server Fault or by roacha
Published on 2012-11-09T16:48:04Z Indexed on 2012/11/09 17:03 UTC
Read the original article Hit count: 246

Filed under:
|
|

I could really use some advice. I started a new instance on EC2 using Amazon's AMI and during the deployment process I selected a Kernel ID of "Use Default". I then configured my server the way that I wanted to and took a snapshot of it. I then created my own AMI to create new servers with. When I try and create a new server with this AMI the server fails to start and I get the error: EXT3-fs: sda1: couldn't mount because of unsupported optional features (240).

Which appears to happen because I am selecting a kernel id of "Use default" again when building my second server. I have read that in order for this to work I need to choose the same kernel id that was used in my original server. I have deleted my original server and don't know what it was using.

What is the best process to follow in order to not have these issues? Should I choose "Use Default" for my original server? How do you know which kernel it selected? Then should I just document this and always specify this during the deployment of my next servers using my custom AMI? OR should I choose a custom kernel id during the initial build and always use this one moving ahead hoping Amazon never retires it?
Thanks for any advice!

© Server Fault or respective owner

Related posts about amazon-ec2

Related posts about kernel