You have probably created a new additional volume, or an additional disk.
This guide will explain how to create an additional disk, and then how to attach it to one of your instances.
From an instance on Linux
- List disks
sudo fdisk -l /dev/vd*
/dev/vda generally corresponds to the disk of your instance, /dev/vdb will thus be the first additional volume. Some operating systems recognize disks using another driver. In this case, they appear as /dev/sd*.
- Create a partition with parted
sudo parted /dev/vdb mktable gpt mkpart primary ext4 512 100% quit
- Format the partition
sudo mkfs.ext4 /dev/vdb1
- Mount the partition
sudo mount /dev/vdb1 /mnt
- Checking the mount
For a persisting disk mount, you will need to change the
- Retrieve the block ID
$ sudo blkid /dev/vda1: UUID="51ba13e7-398b-45f3-b5f3-fdfbe556f62c" TYPE="ext4" PARTUUID="000132ff-01" /dev/vdb1: UUID="2e4a9012-bf0e-41ef-bf9a-fbf350803ac5" TYPE="ext4" PARTUUID="95c4adcc-01"
- Add your disk in the
$ sudo vim /etc/fstab /etc/fstab: static file system information. # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # <file system> <mount point> <type> <options> <dump> <pass> UUID=51ba13e7-398b-45f3-b5f3-fdfbe556f62c / ext4 defaults 0 0 UUID=2e4a9012-bf0e-41ef-bf9a-fbf350803ac5 /mnt ext4 nofail 0 0
From an instance on Windows
- Access the disk management tool
- Format the disk
If the message "offline" appears (the disk is offline because of policy set by an administrator), you will need to change the disk attributes by right-clicking your disk, and then selecting "Online" and "Initialize" or by using Diskpart:
- Launch Powershell or the command prompt
- Checking the strategy followed
- Change the strategy
- Applying the strategy on the additional disk
- Initialize the disk from the disk manager and then format the disk.
Once the disk is formated, you can easily access it from your file explorer.