Tell me more ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.
up vote 3 down vote favorite

So basically, I created a large windows server for development, and then I created a micro windows server for production. I set up everything how I wanted it on my development server, and then i unmounted the drives, and mounted them to my micro server.

Now I'm trying to get back into my large windows development server, and I'm getting the error.

Invalid value 'i-4896ce28' for instanceId. Instance does not have a volume attached at root (/dev/sda1)

this error pops up when I try to start my large windows server. I've remounted the drives to the large development server, and I still get this message.

I'm not really sure what to do, I've read other posts and everyone is giving these almost like command line arguments and talking about other tools, and I really have no clue what any of that means, or where I even have an option to enter any commands without be logged into a specific instance.

share|improve this question

migrated from stackoverflow.com Oct 26 '11 at 9:24

1 Answer

up vote 3 down vote accepted

Make sure the EBS-drive has the name /dev/sda1 in the EC2-Console.

share|improve this answer
It was confusing to me how they put on the botton of the attach device dialog that windows devices should be xvdg-xvdh..I wasn't aware I could just type in /dev/sda1. Thanks alot. – Kyle Oct 29 '11 at 2:56
I've been there to; wouldn't know it otherwise ;) – Bart De Vos Oct 29 '11 at 6:46

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.