Forums | Admin Discussion Forums: help Start New Thread Nested Flat Threaded Ultimate Show 25 Show 50 Show 75 Show 100   By: Kevin Carlson RE: Using Cloudy Scripts [ reply ]   2011-03-09 16:22 So in using the Copy snapshot option I get closer to achieving results but it fails on the mounting part.. assumptions are due to this: Creating the partition is not enough to use it as you are pointing out you need to put a filesystem on it. ie: Code: mkfs.ext3 /dev/hdb1 Then you can mount it using Code: mount -t ext3 /dev/hdb1 /mnt/hdb1 By: Frederic Donnat RE: Using Cloudy Scripts [ reply ]   2011-03-09 16:02 Kevin, You got the point. It should be possible to start a standard linux instance and then mount the volume. The only problem I could see is that this volume contains a Windows filesystem. /fred By: Kevin Carlson RE: Using Cloudy Scripts [ reply ]   2011-03-09 15:37 Thanks for the response Frederic! So lets talk about a way we might accomplish this. What if we were to build a Linux system and have this Linux system mount the windows volume (temporarily) and then start the transfer. Once the transfer is done reverse the process? By: Frederic Donnat RE: Using Cloudy Scripts [ reply ]   2011-03-09 13:56 Hi Kevin, Thanks for your feedback on CloudyScripts project. Currently, Windows AMIs are not supported in the "Copy AMI To Different Region" CloudyScript. Actually, we are starting an instance of the AMI provided in the source region and then connect to that instance using SSH. This involves that Windows AMI are not supported. /fred By: Kevin Carlson Using Cloudy Scripts [ reply ]   2011-03-09 01:03 Hey guys, love the start of this project. You have exactly what I need to copy AMI's from one place to another... dont know why Amazon cant do this themselves. Anyway I would like to use it however got an error when trying to use the: Copy AMI To Different Region. I followed the limited on screen questions and hit submit.. things seem to be working when it stops trying to SSH into the instance. The execution status is: Done (Failed) Execution Time is: 247s Execution failed in status FailedState due to connection attempts stopped (execution expired) Mar, 09 - 00:45:49: starting up instance to execute the script (AMI = ami-e79bcba2) ... Mar, 09 - 00:45:50: Architecture of image ami-******is i386. Use instance_type m1.small. Mar, 09 - 00:45:51: Started instance i-*******. wait until it is ready... Mar, 09 - 00:45:57: instance still starting up... Mar, 09 - 00:46:03: instance still starting up... Mar, 09 - 00:46:09: instance is up and running Mar, 09 - 00:46:10: going to create a snapshot for volume vol-149f2879... Mar, 09 - 00:46:17: snapshot is done with ID=snap-******** Mar, 09 - 00:46:17: going to create a new EBS volume from the specified snapshot... Mar, 09 - 00:46:25: EBS volume vol-********is ready Mar, 09 - 00:46:25: going to attach volume vol-********to instance i-4ed6980a on device /dev/sdj... Mar, 09 - 00:46:32: volume successfully attached Mar, 09 - 00:46:32: connecting 'root' to ec2-***-***-***-***.us-west-1.compute.amazonaws.com... This is a Windows Server AMI if that makes any difference..