Questions tagged with Amazon Elastic Block Store
Content language: English
Sort by most recent
Unable delete a volume - struck with deleting status
I created a EBS volume and attached with an instance. Partitioned, mounted, created files. Unmounted, detached, created snapshot and then tried to delete the volume. But unable to delete the volume and its struck with "Deleting" status. And also I terminated the instance as well. Only the volume is deletion is pending. How to delete this volume forcefully?
How to decrease size of a root volume EC2 Amazon Linux2?
I want to decrease the size of a root volume in an EC2 running Amazon Linux2. I have followed some posts from internet and a post from [here](https://repost.aws/questions/QUypl3Te6QSxGMbRRA6RuCPQ/how-to-decrease-size-of-boot-volume-on-m-5-instance-using-nv-me) but it does not work for Amazon Linux2.
Increasing EBS Volume disk size created a 3rd drive on Windows Disk Management
I have 2 EBS storage volumes attached to a Windows EC2 instance. The volumes were 40gb and 100gb. I increased the 100gb disk to 300 gb, and RDP'ed to the EC2 Windows box ran disk management to allocate the new space to the D drive, but this is what I found instead: https://pasteboard.co/swhXG4lEqQDA.png It shows a new drive W that isn't formatted, but has 200gb unallocated to it. Now if I look at the total amount of space available I'd have 40gb (C:/) + 100gb (D:/) + 300gb (W:/)= 440gb!? But in the AWS console I show only 340gb total between 2 EBS volumes. Which brings up the issue that if I format the disk I might be overwriting data because there isn't 440gb allocated. I've tried rebooting the box without success it still shows this extra drive. And I can't find any information about this situation or how to fix it.
EBS IOPS, Throughput and EBS bandwidth
we need to deploy ec2 with following EBS configuration- random 4k write : 2,00,000 IOPS sequential read-2000Mb/s sequential write-2000Mb/s this is database server requirement. 1. I have some confusion if I select **io2** EBS type with 200000 provision IOPS let say for 24 hours and after that I have modified EBS type to GP3 do AWS charge me for full month or only for 24 hours? if AWS would accrued 24 hours charge what would be charges? 2. what ec2 type I should go for any suggestions? Or am I making any mistake in selecting EBS type please guide me.
Snapshots of encrypted EBS volumes
We know that the first snapshot of an EBS volume is a full copy and the next snapshots are incremental i.e. only the blocks that have been changed since the last snapshot are copied to S3. I want to know if this is true for **encrypted volumes** as well. Are the subsequent snapshots of an **encrypted EBS volume** full or incremental?
Cannot mount volumes made from snapshots, get "Bad message", invalid superblock
My old EC2 server, that was launched in 2011, has finally died. It is unreachable and cannot be rebooted. It was running an Amazon AMI. I created a new VPC server with a new Amazon Linux2. My plan was to copy my website files from an old snapshot to the new drive on the new server. I created a volume from an old snapshot taken a few days before the server died. I can see the volume has a filesystem. $ sudo file -s /dev/xvdf /dev/xvdf: SGI XFS filesystem data (blksz 4096, inosz 256, v2 dirs) But it fails when I try to mount it. $ sudo mkdir /olddata $ sudo mount /dev/xvdf /olddata mount: /old_data: mount(2) system call failed: Bad message. $ sudo e2fsck -p /dev/xvdf e2fsck: Bad magic number in super-block while trying to open /dev/xvdf I tried the same things for older snapshots a month before the server died and got the same result. I know the website was running. So the old filesystem must have been somewhat OK. I tried: $ sudo e2fsck -b 8193 /dev/xvdf No luck. I also tried "Fast snapshot restore" so that I knew I was working with a fully restored snapshot. But it made no difference. Any suggestions for how to recover the files from the old snapshot? Or how to get the old server to launch so I can FTP the files?
Orchestrating single container hosts
We have a fleet of EC2 instances that are used to run one Docker container per instance. These instances are pretty large and use AWS EBS as storage backend as storage io requirements are pretty high. The docker containers are run using basic docker-compose on the EC2 instances and these docker-compose files are managed by ansible globally. The workload requires quite a lot of cpu and iops so EBS as a storage is a requirement This is a legacy setup and at some point we need to move over away from docker compose to something more flexible and modern. The workload specifics where one huge container is used per host makes me think that this is not really a case for kubernetes or ECS, especially when EBS are in the mix too. At least not vanilla kubernetes in the sense I understand how kubernetes work. Could anyone point me to a right direction here?
cloudformation to create ec2 using volume attachment for root.
Hello I am trying to create one EC2 using cloudformation. The requirement is to use volume attachment with a snapshot id. This snapshot id is coming from my AMI and the snapshot id provided is the root device. (AMI only consist of one snapshot) I got the error message: Property ImageId cannot be empty when deploying the resource. When I input the ImageId for AWS::EC2::Instance, it will crash with AWS::EC2::VolumeAttachment property. Can someone help to modify my template and point out how can I fix this issue? ``` --- Description: "AWS CloudFormation sample template. Create a new EC2 instance" Resources: myEC2Instance: Properties: IamInstanceProfile: ec2role InstanceType: t2.micro SecurityGroupIds: - sg-123456 SubnetId: subnet-123456 Tags: - Key: Name Value: ec2test Type: "AWS::EC2::Instance" myMountPoint: Properties: Device: /dev/xvda InstanceId: myEC2Instance VolumeId: myVolume Type: "AWS::EC2::VolumeAttachment" myVolume: Properties: AvailabilityZone: !GetAtt myEC2Instance.AvailabilityZone Size: 10 SnapshotId: snap-123456 Tags: - Key: Name Value: ebstest VolumeType: gp2 Size: 10 Type: "AWS::EC2::Volume" ```