on Amazon's new t1.micro instance type, there is no ephemeral storage at all.
cloud-init is basically hard coded to expect an 'ephemeral0', while other ephemeral devices are more dynamic.
Our images are registered with block-device-mapping indicating ephemeral0, so the metadata service will include ephemeral0 even though there is not one on the instance itself.
We need to do one of 2 things here:
a.) add 'nobootwait' for the ephemeral0 device (/dev/sda2 in this case)
b.) not write a entry in /etc/fstab (or comment it out) if that device is not present on the first boot.
Binary package hint: cloud-init
on Amazon's new t1.micro instance type, there is no ephemeral storage at all.
cloud-init is basically hard coded to expect an 'ephemeral0', while other ephemeral devices are more dynamic.
Our images are registered with block-device- mapping indicating ephemeral0, so the metadata service will include ephemeral0 even though there is not one on the instance itself.
We need to do one of 2 things here:
a.) add 'nobootwait' for the ephemeral0 device (/dev/sda2 in this case)
b.) not write a entry in /etc/fstab (or comment it out) if that device is not present on the first boot.
ProblemType: Bug ature: User Name 2.6.32-308.15-ec2 2.6.32.15+drm33.5 Zone: us-east-1c ture: all
DistroRelease: Ubuntu 10.04
Package: cloud-init 0.5.10-0ubuntu1.2
ProcVersionSign
Uname: Linux 2.6.32-308-ec2 i686
Architecture: i386
Date: Thu Sep 9 14:42:21 2010
Ec2AMI: ami-1234de7b
Ec2AMIManifest: (unknown)
Ec2Availability
Ec2InstanceType: t1.micro
Ec2Kernel: aki-5037dd39
Ec2Ramdisk: unavailable
PackageArchitec
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: cloud-init