Questions tagged with Amazon Elastic Block Store
Content language: English
Sort by most recent
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" ```
How do I transfer data from EBS volume to EFS site using DataSync?
Hi There, I want to copy some data from my EBS volume to EFS site and for this purpose I want to use AWS DataSync. When I am trying to choose source location (while setting up Datasync Task) there is no option to choose EBS volume as source point. Can someone guide on how can I accomplish data transfer from EBS volume to EFS using DataSync service?
EBS Unoptimized Product
Hello Everyone, We have an AMI product on AWS and I have been updating the version as we make progress on our application. I have never changed from the way I have created the AMI that I am associating with the new version of the product. Last night I tried to change the version of the AMI product and put in the new AMI and received the following error which I have never seen before and can't find any information on it on the interwebs. Ebs unoptimized product This product does not support EBS optimized AMIs. Provide a new AMI that has EBS Optimization disable. Did I click on something by accident that would make this message appear? Any help would be greatly appreciated. Thanks!
DLM cloud watch matrics
Hi All, I have setup the DLM for daily & weekly backup of EBS volumes. I have setup the cloud matrics to get the total count of the Snapshot completed & failed. The sum of data is based on the period filter not the duration i.e., 1) If the period =1day and Duration : 1 months, it shows sum= 1 2) If the period=7days and Duration : 1 Months, it shows sum = 7 3) If the period=30days and Duration : 1 Months, it shows sum = 30 I want that when I select the duration, it should show total count of completed & failed snapshot. Please suggest. Regards, Nikhil Shah
InternalError creating EBS snapshot
With both web console and awscli, I get InternalError when trying to create a snapshot of an (8120GB gp3) EBS Volume. Running awscli with --debug shows no additional error information. I can find no prior snapshots for the volume(s). I've never made snapshots with this account before.
How to attach EBS volume from original EC2 instance to a new EC2 instance?
currently my website is running under a t3a.small EC2 instance (Origin - N California) and the volume size is 10 GIB. Now i have launched a new EC2 t2.micro instance (Origin - Mumbai) and the volume size is 8 GIB. All i'm doing for avoiding charges as i am a free tier user and the original instance is not cover the free tier promotion. So how can i attach EBS volume from original instance to new instance without losing any data?
EC2 Instance with recurrent I/O errors, but fsck reports filesystems as clean
I have a Linux (Ubuntu) instance running as m3.xlarge - this server is getting IO errors across multiple EBS volumes. I have unmounted the volumes and run fsck on them. One found some problems that were fixed, the others reported as clean. On restart, after a while (hour) I received more IO errors. As multiple volumes are involved, I wondered if there was an underlying hardware problem (I have multiple other very similar instances which are functioning as normal). I have stopped/started the instance to see if that would move it to a new host, but there is no way of telling. Suggestions on finding the issue? Is there a way to confirm if an instance has moved to a new host?
MBT to GPT format change
Hi, We have a 2TB volume m5.2xlarge instance, the root volume limit is 2TB and cannot increase the size because of size limit of it being MBR partion. Model: Amazon Elastic Block Store (nvme) Disk /dev/nvme0n1: 2147GB Sector size (logical/physical): 512B/512B Partition Table: msdos Disk Flags: The only way out seems https://aws.amazon.com/premiumsupport/knowledge-center/ec2-ubuntu-convert-mbr-to-gpt/ Is that the only way out here, is there a better way of increasing the limit without data loss?