怎么挂载这个盘呢？(EBS)

Question

我恢复了一个 EBS 卷并将其附加到一个新的 EC2 实例。当我lsblk可以在名字下看到它时/dev/nvme1n1。

\n

更具体地说，输出lsblk是：

\n

NAME        MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT\nloop0         7:0    0   25M  1 loop /snap/amazon-ssm-agent/4046\nloop1         7:1    0 55.4M  1 loop /snap/core18/2128\nloop2         7:2    0 61.9M  1 loop /snap/core20/1169\nloop3         7:3    0 67.3M  1 loop /snap/lxd/21545\nloop4         7:4    0 32.5M  1 loop /snap/snapd/13640\nloop5         7:5    0 55.5M  1 loop /snap/core18/2246\nloop6         7:6    0 67.2M  1 loop /snap/lxd/21835\nnvme0n1     259:0    0    8G  0 disk \n\xe2\x94\x94\xe2\x94\x80nvme0n1p1 259:1    0    8G  0 part /\nnvme1n1     259:2    0  100G  0 disk \n

\n

如您所见，nvme1n1没有分区。结果，当我尝试使用以下命令将其安装到文件夹上时：

\n

sudo mkdir mount_point\nsudo mount /dev/nvme1n1 mount_point/\n

\n

我明白了

\n

mount: /home/ubuntu/mount_point: wrong fs type, bad option, bad superblock on /dev/nvme1n1, missing codepage or helper program, or other error.

\n

该卷内部有数据：

\n

/dev/nvme1n1: data\n

\n

使用sudo mkfs -t xfs /dev/nvme1n1创建文件系统不是一个选项，亚马逊指出：

\n

\n

警告\n如果您正在装载已包含数据的卷（例如，从快照创建的卷），请勿使用此命令。否则，您将格式化该卷并删除现有数据。

\n

\n

事实上，我用我恢复的第二个虚拟 ebs 快照进行了尝试，得到的只是一个虚拟lost+found linux 文件夹。

\n

这个EBS恢复的快照里面有有用的数据，我如何挂载它而不破坏它们？

\n

---

\n

# parted -l /dev/nvme1n1 print\nModel: Amazon Elastic Block Store (nvme)\nDisk /dev/nvme0n1: 8590MB\nSector size (logical/physical): 512B/512B\nPartition Table: msdos\nDisk Flags: \n\nNumber  Start   End     Size    Type     File system  Flags\n 1      1049kB  8590MB  8589MB  primary  ext4         boot\n\n\nError: /dev/nvme1n1: unrecognised disk label\nModel: Amazon Elastic Block Store (nvme)                                  \nDisk /dev/nvme1n1: 107GB\nSector size (logical/physical): 512B/512B\nPartition Table: unknown\nDisk Flags: \n

\n

dmesg | grep nvme1n1\n[   68.475368] EXT4-fs (nvme1n1): VFS: Can\'t find ext4 filesystem\n[   96.604971] EXT4-fs (nvme1n1): VFS: Can\'t find ext4 filesystem\n[  254.674651] EXT4-fs (nvme1n1): VFS: Can\'t find ext4 filesystem\n[  256.438712] EXT4-fs (nvme1n1): VFS: Can\'t find ext4 filesystem\n

\n

\n sudo fsck /dev/nvme1n1\nfsck from util-linux 2.34\ne2fsck 1.45.5 (07-Jan-2020)\next2fs_open2: Bad magic number in super-block\nfsck.ext2: Superblock invalid, trying backup blocks...\nfsck.ext2: Bad magic number in super-block while trying to open /dev/nvme1n1\n\nThe superblock could not be read or does not describe a valid ext2/ext3/ext4\nfilesystem.  If the device is valid and it really contains an ext2/ext3/ext4\nfilesystem (and not swap or ufs or something else), then the superblock\nis corrupt, and you might try running e2fsck with an alternate superblock:\n    e2fsck -b 8193 <device>\n or\n    e2fsck -b 32768 <device>\n

\n

Answer 1

我自己一直在努力解决这个问题，然后随着信息不断涌入，我突然意识到

disk util 管理驱动器和媒体以及挂载点，使用风险由您自行承担，它是大多数 Linux 发行版中的标准实用程序