Lorem ipsum dolor sit amet, consectetur adipiscing elit lobortis arcu enim urna adipiscing praesent velit viverra sit semper lorem eu cursus vel hendrerit elementum morbi curabitur etiam nibh justo, lorem aliquet donec sed sit mi dignissim at ante massa mattis.
Vitae congue eu consequat ac felis placerat vestibulum lectus mauris ultrices cursus sit amet dictum sit amet justo donec enim diam porttitor lacus luctus accumsan tortor posuere praesent tristique magna sit amet purus gravida quis blandit turpis.
At risus viverra adipiscing at in tellus integer feugiat nisl pretium fusce id velit ut tortor sagittis orci a scelerisque purus semper eget at lectus urna duis convallis. porta nibh venenatis cras sed felis eget neque laoreet suspendisse interdum consectetur libero id faucibus nisl donec pretium vulputate sapien nec sagittis aliquam nunc lobortis mattis aliquam faucibus purus in.
Nisi quis eleifend quam adipiscing vitae aliquet bibendum enim facilisis gravida neque. Velit euismod in pellentesque massa placerat volutpat lacus laoreet non curabitur gravida odio aenean sed adipiscing diam donec adipiscing tristique risus. amet est placerat in egestas erat imperdiet sed euismod nisi.
“Nisi quis eleifend quam adipiscing vitae aliquet bibendum enim facilisis gravida neque velit euismod in pellentesque massa placerat”
Eget lorem dolor sed viverra ipsum nunc aliquet bibendum felis donec et odio pellentesque diam volutpat commodo sed egestas aliquam sem fringilla ut morbi tincidunt augue interdum velit euismod eu tincidunt tortor aliquam nulla facilisi aenean sed adipiscing diam donec adipiscing ut lectus arcu bibendum at varius vel pharetra nibh venenatis cras sed felis eget dolor cosnectur drolo.
While working on a failed EC2 (ebs backed) instance recently, we were presented with an instance that would not start after reboot or stop/start.tl;dr: Create a snapshot of the existing EBS vol; remount and edit etc/fstab; re-attach and start the instance.The only symptom was in the console log:$ ec2-get-console-output i-nnnnnnnninit: console-setup main process (63) terminated with status 1%Ginit: plymouth main process (45) killed by SEGV signalinit: plymouth-splash main process (194) terminated with status 2cloud-init running: Sat, 29 Jan 2011 23:33:24 +0000. up 2.65 secondsmountall: Disconnected from PlymouthIt turned out this instance was running as a t1.micro instance, which do not have instance storage on /dev/sdb like all other instance types.The problem with this is the /etc/fstab entry contained and entry:/dev/sdb /mnt auto defaults,comment=cloudconfig 0 0The parameter "nobootwait" is missing!This was causing the instance to hang on reboot. The solution to this problem is as follows:
$ ec2-describe-instances i-brokeninst
$ ec2-create-snapshot vol-brokenvol$ ec2-create-volume --snapshot snap-fromcreateabove -z us-east-1dVOLUME vol-newvolume 15 snap-fromcreateabove us-east-1d creating 2011-01-30T00:01:30+0000
$ ec2-attach-volume vol-newvol -i i-tempinstance -d /dev/sdX #use a free /dev/sd letterNote: You can remove the /dev/sdb entry, or use you should also be able to use an entry like:/dev/sdb /mnt auto defaults,nobootwait 0 0
$ ec2-detach-volume vol-newvol
$ ec2-detach-volume vol-oldvolume
$ ec2-attach-volume vol-newvol -i i-brokeninstance -d /dev/sda1