I forgot to mention that this is not an EBS-backed image; it's instance storage only.
On Wed, Feb 22, 2012 at 8:11 PM, Rodney Quillo <[email protected]> wrote: > Hmm.. Seems like the disk label is changed. > How about instead of using: > > mkfs.ext3 ${EBS_DEVICE} -L uec-rootfs > > use: > > mkfs.ext3 ${EBS_DEVICE} -L cloudimg-rootfs > > > when making the AMI root device. > > Rodney > > On 2/23/12 8:30 AM, Chetan Sarva wrote: > > Hi, > > I'm trying to create an AMI using a recent Lucid AMI as my base. I've > done this in the past without any problems but suddenly I'm running into > the following when trying to boot my newly created AMI: > > http://pastebin.com/raw.php?i=2m16AfFs > > I can reboot the instance used to create this AMI just fine, so I'm not > sure what's going on here. I saw this post about a similar issue: > > > http://return1.at/ubuntu-ec2-ami-with-xfs-root-ebs-volume-10-04-lts-lucid-lynx/ > > However we are not using xfs -- just the default ext3 for root. Our > customizations to the image are fairly minimal -- installing some base > packages and our application -- nothing to do with any of the mounts, etc. > > Is anyone else seeing similar issues? > > regards, > > chetan > > >
-- Ubuntu-cloud mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-cloud
