- 最新
- 投票最多
- 评论最多
Dag nab it, thanks for the response. After taking a few days away from the issue, I started looking at the creation of the EBS device script again with fresh eyes and noticed I was omitting the snapshot-id option. So it was indeed creating a blank EBS device. After adding the snapshot-id option, I'm seeing the partitions present as expected.
Hello, thank you for your post. I understand you have created a snapshot of a root volume of a RHEL 8 EC2 instance. You then created a new EBS volume from the snapshot and then attached the new EBS volume to a RHEL 8 EC2 instance as a secondary volume. After this, lsblk does not show any partitions on the new EBS volume, even though there were multiple partitions originally.
I was unable to reproduce this issue when following the same procedure.
I launched a new EC2 instance using a RHEL 8 AMI, then created a snapshot of its root volume. From the snapshot I created a new EBS volume. I then launched a new EC2 instance using a RHEL 8 AMI again, and attached the EBS volume from the previous step. When I ran the lsblk command, I was able to see that all of the original partitions were present and visible for the secondary volume:
# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
nvme0n1 259:0 0 10G 0 disk
├─nvme0n1p1 259:1 0 1M 0 part
└─nvme0n1p2 259:2 0 10G 0 part /
nvme1n1 259:3 0 10G 0 disk
├─nvme1n1p1 259:4 0 1M 0 part
└─nvme1n1p2 259:5 0 10G 0 part
I encourage you to open a support case so that one of our support engineers can inspect the details of the specific snapshot and EBS volume in question, and provide further assistance with this issue.
相关内容
- AWS 官方已更新 1 年前
- AWS 官方已更新 1 年前
can you check. entries in fstab before and after to validate the issue
I'm not at the point of manipulating or saving information in fstab, but here is a look at the fstab before and after the attachment of the disk:
[ec2-user@ip-172-31-78-116 tmp]$ cat /etc/fstab UUID=4df66650-964a-4178-b95f-97717f4059a5 /boot xfs defaults 0 0 UUID=b2de97b2-9d86-42ff-94f2-ed2c0bc1d661 / xfs defaults 0 0 UUID=7B77-95E7 /boot/efi vfat defaults,uid=0,gid=0,umask=077,shortname=winnt 0 2
Looks like it is only holding entries for the root block device, which doesn't seem unexpected at this time.
And parted doesn't seem to know anything about the drive either: [ec2-user@ip-172-31-78-116 tmp]$ sudo parted /dev/nvme2n1 GNU Parted 3.2 Using /dev/nvme2n1 Welcome to GNU Parted! Type 'help' to view a list of commands. (parted) p Error: /dev/nvme2n1: unrecognised disk label Model: NVMe Device (nvme) Disk /dev/nvme2n1: 21.5GB Sector size (logical/physical): 512B/4096B Partition Table: unknown Disk Flags: