4.3 Mount and prep volumes

Mount and prep volumes

  1. From the AWS console, click Services and select EC2.
  2. Select Instances from the menu on the left.
  3. Right-click on the EC2 Initiator Instance and select Connect from the menu.
  4. From the dialog box, select the Session Manager option, as shown below:

  1. Click Connect. A new tab will be opened in your browser with a command line interface (CLI) to the EC2 Initiator Instance.

  2. Run the command:

    lsblk

and note the device of the 500GB volume we have attached. Providing no other EBS volumes have been attached, it will be nvme[0-26]n1. We can also see previous 200GB volume as sda, take a note of this.

Note: The device names that you specify for NVMe EBS volumes in a block device mapping are renamed using NVMe device names (/dev/nvme[0-26]n1). The block device driver can assign NVMe device names in a different order than you specified for the volumes in the block device mapping. For more details on Amazon EC2 Device naming on Linux instances: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/device_naming.html

  1. We are going to unmount the 200GB Volume Gateway Volume under data1 and mount the 500GB EBS Volume. To start, run the following commands:

    sudo umount /data1

    sudo mount /dev/<devicename> /data1

  1. There should be the 1GB files pre-populated on the volume. This can be confirmed with the following two commands. To see the list of files:

    ls -l /data1

and to check the amount of data used on /dev/[devicename]

df -h

Note: the disk partition has not been expanded on nvme[0-26]n1 / the snapshot clone volume, so this will still show as 200GB in size.