XFS: wrong fs type, bad option, bad superblock

0

My AWS Linux 2 instance boot drive is snapshotted daily. I'd like to mount one of the snapshots to my instance to review changes I've made in /etc. I created a volume based on the snapshot, attached to my instance and tried to mount it. I used df -T to determine my existing boot drive filesystem is xfs. I presume my snapshot is xfs. I can't seem to mount it. I tried with several of the snapshots. Am I trying to do something weird, adding a second bootable drive to my instance?

mount /dev/xvdi1 /mnt/tmp mount /dev/xvdi1 /mnt/tmp -t xfs mount -t xfs /dev/xvdi1 /mnt/tmp

mount: /mnt/tmp: wrong fs type, bad option, bad superblock on /dev/xvdi1, missing codepage or helper program, or other error.

from fdisk -l: Disk /dev/xvdi: 16 GiB, 17179869184 bytes, 33554432 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: EB7656A9-A5D7-4AAF-B8A8-67A3FBEC56BA

Device Start End Sectors Size Type /dev/xvdi1 4096 33554398 33550303 16G Linux filesystem /dev/xvdi128 2048 4095 2048 1M BIOS boot

已提问 2 年前5188 查看次数
2 回答
0

Hi there ,I understand that you would like to mount the volume that you created and now you are unable to mount it.Correct me if I misunderstood.

Based on the tests that I ran you will need to : [1]create a snapshot [2]attach it to a volume [3]Stop the instance that you want to mount the volume to [4]attach the volume of the snapshot to your rescue instance [5]SSH into the rescue instance [6]Run this command < lsblk -f > to check the name of the disk you want to mount [7]run the following command to mount [7.1] mount -o nouuid /dev/<diskname> /data

I have provided you with additional documentation under the reference section.

I hope this was helpful!

Reference [1]https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-creating-volume.html#ebs-create-volume-from-snapshot [2]https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-using-volumes.html

Karabo
已回答 2 年前
0

You might have found your way around. Just in case someone stumbles upon the same issue: Try running mount -o nouuid /dev/xvdi1 /mnt/tmp r. Just in case someone stumbles upon same issue:

已回答 11 天前

您未登录。 登录 发布回答。

一个好的回答可以清楚地解答问题和提供建设性反馈,并能促进提问者的职业发展。

回答问题的准则