Ec2 Linux Ubuntu 18.04 increased space resulted in second volume

Question

```

```
![fdisk-l](/media/postImages/original/IM0eKYF3vVSpiJz9ZTaZ27LQ)
I installed my Ubuntu instance on the default volume which was 8 GB.  I then decided to go into the instance and increase its storage by clicking on the volume and then clicking on the modify link and entering 500 GB. But this resulted in a second volume of 500 GB And I am unable to continue my work on the existing instance because I do not have enough space. I actually get the error message I was getting before which states that there is not enough space left in that volume.

Is there a way to merge both volumes or what else would I have to do in order for the original volume to somehow will be automatically connected to the new one such that I no longer get the not enough space available error on the console?

Here are the results for df -h:

```
[cloudshell-user@ip-10-2-6-242 ~]$ df -h
Filesystem      Size  Used Avail Use% Mounted on
overlay          20G  3.9G   16G  21% /
tmpfs            64M     0   64M   0% /dev
tmpfs           1.3G     0  1.3G   0% /sys/fs/cgroup
shm              64M     0   64M   0% /dev/shm
/dev/vde         20G  3.9G   16G  21% /root
/dev/loop0      974M  6.9M  900M   1% /home/cloudshell-user
```

Im not seeing the 500GB volume that shows up on the web interface of AWS.  I followed the instructions for expanding the volume from 8 to 500gb.  If it doesnt show up, the document referred to (expanding filesystem) says to do the following:

```
[cloudshell-user@ip-10-2-6-242 ~]$ sudo lsblk
NAME  MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
loop0   7:0    0    1G  0 loop /home/cloudshell-user
vda   254:0    0    2G  0 disk 
vdb   254:16   0   10G  0 disk 
vdc   254:32   0   10G  0 disk 
vdd   254:48   0   10G  0 disk 
vde   254:64   0 20.3G  0 disk /aws/mde/logs
```

and Im on nitro according to the instance type command.  Since I dont see any partitions, then i move to Step 3:

```
[cloudshell-user@ip-10-2-6-242 ~]$ df -hT
Filesystem     Type     Size  Used Avail Use% Mounted on
overlay        overlay   20G  3.9G   16G  21% /
tmpfs          tmpfs     64M     0   64M   0% /dev
tmpfs          tmpfs    1.3G     0  1.3G   0% /sys/fs/cgroup
shm            tmpfs     64M     0   64M   0% /dev/shm
/dev/vde       ext4      20G  3.9G   16G  21% /root
/dev/loop0     ext4     974M  6.9M  900M   1% /home/cloudshell-user
[cloudshell-user@ip-10-2-6-242 ~]$ sudo xfs_growfs -d /
sudo: xfs_growfs: command not found
```

but growfs command fails.  Should I do sudo xfs_grows -d /root/vde/?  Or use the resize command?  That is the only step I haven't been through because I was worried not knowing the pount or partition to use:

```
sudo resize2fs /dev/??

```

How should i structure the command?

Accepted Answer

CloudShell doesn't log you in to the EC2 instance you're working with, use SSH or Instance Connect or AWS Systems Manager Session Manager.

It sounds like you originally had 1 x 8GB disk, and you want to expand this to 1 x 500GB disk, is that right? But instead you have ended up with two disks, 1x8GB + 1x500GB.

Confirm this by running `lsblk`.

You cannot merge these volumes. If you haven't made any use of the second disk yet, then it's safe to detach the 500GB disk from the EC2 instance and delete the volume.

If you actually want to end up with a 500GB rootdisk then the high-level steps are in this Knowledge Centre document https://repost.aws/knowledge-center/expand-root-ebs-linux

Once you have read through this it will direct you to two more links, firstly to expand the volume https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/requesting-ebs-volume-modifications.html

And once that has been done, to expand the filesystem https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/recognize-expanded-volume-linux.html

I would caution that it's probably not a good idea to have a 500GB root disk, and in all likelihood you should want to have a second disk which you mount as a separate filesystem on another mountpoint. But this is getting away from answering the question that you have submitted.

Answer

Hi,

If you have added additional volume to your EC2 instance, the only way to extend the original one is using LVM, but I'm not sure if you want to go this way. It could be that after extending the volume, you used additional space to create an additional partition but it's hard to say without having an output of `fdisk -l`

In this documentation, you can see how to extend the volume https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/step3-increase-size-of-data-volume.html, and there is an additional step on how to extend the filesystem.

Answer

I've run sudo lsblk.  Here is what my developer sees when he tries to upload the data:![Enter image description here](/media/postImages/original/IMLcvYpfyRSpKjq2axpVgsWg)

Here are the lsblk results:

```
[cloudshell-user@ip-10-2-6-242 ~]$ sudo lsblk
NAME  MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
loop0   7:0    0    1G  0 loop /home/cloudshell-user
vda   254:0    0    2G  0 disk 
vdb   254:16   0   10G  0 disk 
vdc   254:32   0   10G  0 disk 
vdd   254:48   0   10G  0 disk 
vde   254:64   0 20.3G  0 disk /aws/mde/logs
```
I also updated the original question with more recent actions taken to expand the filesystem.

Ec2 Linux Ubuntu 18.04 increased space resulted in second volume

Relevant content