Menu
I am trying to launch an instance, and I'm adding an EBS volume on top of the root volume. In the extra EBS volume, I'm specifying a snapshot I created. When I click "Launch", I immediately get the following error:
snapshotId can only be modified on EBS devices
Can you explain the problem please?
228
While it is completing, an in-progress snapshot is not affected by ongoing reads and writes to the volume. You can take a snapshot of an attached volume that is in use. However, snapshots only capture data that has been written to your Amazon EBS volume at the time the snapshot command is issued.
It can take several hours, but it generally doesn't matter how long it takes. If you need a completely consistent snapshot you shut the server down, trigger the snapshot, then start the server immediately.
Snapshots go across regions where volumes stay in the same region as the snapshot. You can create a copy of a snapshot but you can't create a copy of a volume. In order to make a copy of a volume you have to use a snapshot. Volumes, images, instances all depend on the snapshot.
Ran into the same issue while mounting EBS volume to /dev/sdc on an instance (c3.2xlarge) using HVM image.
The solution which worked for me was to use an available AWS recommended device name e.g. /dev/sdf. AWS recommended device name for attaching EBS volume is /dev/sd[f-p]
For Linux/Unix instance recommended device names are
/dev/sd[f-p]
Source: AWS Block Device Naming on Linux Instances
177
I had the same issue, described it here Amazon Launch Template - Updated AMI .
tl;dr You need to keep AMI and volume's sizes the same. I had 15 GB AMI and 8 GB volume.
1
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
