I would say that this was a temporary AWS issue. If not, please restart the instance and I'm sure you'll be able to build the image.
Thank you for the quick response.
It is 12 hours later and I still am getting the same issue at that point of the process.
How would I restart the instance - the AMI doesn't exist yet, at least in the aws management console.
I was thinking about restarting the instance where you're trying to build the AMI (host).
Ah... you mean the instance that is doing the boxgrinding - I will try it and close the discussion if that works.
1 of 1 people found this helpful
Well rebooting the boxgrinder instance and starting where i left off, I got this:
D, [2011-11-16T15:22:01.052445 #849] DEBUG -- : Waiting for EBS volume vol-a43ff6c9 to be available...
I, [2011-11-16T15:22:01.130541 #849] INFO -- : Attaching created volume...
F, [2011-11-16T15:22:01.233807 #849] FATAL -- : AWS::EC2::Errors::InvalidParameterValue: Invalid value '/dev/sdf' for unixDevice. Attachment point /dev/sdf is already in use
Here is the file system on the boxgrinder build instance:
[root@ip-10-112-58-253 appliances]# df
Filesystem 1K-blocks Used Available Use% Mounted on
rootfs 10321208 8366908 1430012 86% /
udev 289880 0 289880 0% /dev
tmpfs 305388 0 305388 0% /dev/shm
tmpfs 305388 264 305124 1% /run
/dev/xvda1 10321208 8366908 1430012 86% /
tmpfs 305388 0 305388 0% /sys/fs/cgroup
tmpfs 305388 0 305388 0% /media
Doesn't look right to me.
Got the boxgrinder back into shape and the offending EBS removed. Started over, and all worked out well.
Thanks for the help.