7

I have a t1.micro instance with /dev/sda1 volume attached. Now I am out of disk space and migrating to a larger volume. I created the larger volume from the original disk snapshot and attached it to a new instance (for test) as /dev/sda1. The instance doesn't start with error: 

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

If I attach the volume as /dev/xvda, the instance doesn't start. First, it goes into "Running" state, but then the state falls back to "Stopped".

There are threads on Stackoverflow and AWS Developer Forums, but they both seem to be obsolete and not helping.

Improve this question
7
  • 1
    Just a thought, but have you tried to create a new instance from this snapshot, instead of creating a volume from it?
    – SPRBRN
    Jul 14, 2016 at 12:18
  • 1
    Apparently, you can create only a volume, or an image from a snapshot... Volumes can then be attached to an instance.
    – Michael Zelensky
    Jul 14, 2016 at 12:31
  • 1
    Then try to attach it to a new instance. No guarantees, just see if that makes a difference.
    – SPRBRN
    Jul 14, 2016 at 13:17
  • 1
    This is actually what I am doing...
    – Michael Zelensky
    Jul 14, 2016 at 13:41
  • 1
    Create a new instance with a clean root volume, just like starting fresh. Then attach the old one. Does that work?
    – SPRBRN
    Jul 14, 2016 at 13:56

1 Answer 1

Reset to default
6

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

your instance is pointing to root device name "/dev/xvda". So the attached volume should also be mounted at same location but in your case it is mounted at /dev/sda1.

Hence while attaching the volume enter /dev/xvda against device text box.

Image

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .