How to resize ubuntu partition after adding diskspace in AWS?

Questions
1

After creating my Ubuntu 20.04 instance with only 8GB, I went into AWS and increased the volume to 50 GiB in the t3.large instance. Yet, back in Ubuntu, that disk space isn't shown anywhere (based on my current Linux abilities...). FileMaker server is loaded on /dev/root and that disk space did not change after the disk space addition.

Here's what df -HT displays:

Filesystem Type Size Used Avail Use% Mounted on
'==============================================
/dev/root ext4 8.2G 6.5G 1.7G 80% / (FileMaker Server)
devtmpfs devtmpfs 4.2G 0 4.2G 0% /dev
tmpfs tmpfs 4.2G 33k 4.2G 1% /dev/shm
tmpfs tmpfs 823M 869k 823M 1% /run
tmpfs tmpfs 5.3M 0 5.3M 0% /run/lock
tmpfs tmpfs 4.2G 0 4.2G 0% /sys/fs/cgroup
/dev/loop0 squashfs 26M 26M 0 100% /snap/amazon-ssm-agent/6312
/dev/loop3 squashfs 67M 67M 0 100% /snap/core20/1738
/dev/loop2 squashfs 59M 59M 0 100% /snap/core18/2667
/dev/loop1 squashfs 59M 59M 0 100% /snap/core18/2632
/dev/loop4 squashfs 67M 67M 0 100% /snap/core20/1778
/dev/loop5 squashfs 97M 97M 0 100% /snap/lxd/24061
/dev/loop6 squashfs 53M 53M 0 100% /snap/snapd/17883
/dev/loop7 squashfs 53M 53M 0 100% /snap/snapd/17950
/dev/nvme0n1p15 vfat 110M 6.3M 104M 6% /boot/efi
tmpfs tmpfs 823M 0 823M 0% /run/user/1000

The 50 GiB I added in the AWS Console doesn't appear in the list above.

In AWS that 50 GiB disk space I added is on /dev/sda1.

So, how to get this 50 GiB into /dev/root so FileMaker Server can enjoy/use it?

Thanks very much.

2

Hi Oliver

Some hints may help here:

"fdisk -l" should show the new free space (reboot if it does not).
If /dev/root is the only/last partition on the disk, the "growpart" / "resize2fs" will do the trick, otherwise the more complicated (and fear-inducing) ways like answer 4 there will be needed.

Or, if "fdisk -l" shows the free space, create a new partition in the free space (using fdisk, cfdisk, parted,...), format it using mkfs.ext4, mount it somewhere & add it to /etc/fstab. Then move /opt/FileMaker or /opt/FileMaker/FileMaker\ Server/Data to the new partition and link it to the original place.
Or, I would probably stop FMS, copy all of /opt/FileMaker to the new volume and then mount it as /opt/FileMaker. IMHO the cleanest final setup.

2 Likes
3

Thanks. I finally got it resized using the AWS webpage for that. It did use the resize command, but not exactly like any of the examples in that link. :slight_smile:

4

There are many ways of seeking my fortune :slight_smile :slight_smile:
(Steve Hackett – Racing in A Lyrics | Genius Lyrics)
Glad you did it.

5

Thanks @EdwinS. :slight_smile:

I had the additional problem that Tomcat and MariaDB simply weren't externally reachable when installed on the same machine as FMS. Setting up another Linux instance for these two programs worked perfectly. Baffling. Two days spent on this... Now, it looks like I'll need either a single Windows AWS instance where FMS and Tomcat/MariaDB can run or two Linux instances. It's only money, I guess!