Upgrading server disk space and CPU

[MopeyGecko]

Hi all. I've currently got a cloud compute instance at Vulture with a DirectAdmin install on it. I would like to upgrade from

2 vCPU, 4096 MB RAM, 80 GB SSD, 3.00 TB Transfer

To

4 vCPU, 8192 MB RAM, 160 GB SSD, 4.00 TB Transfer

I assume the CPU upgrade won't cause any issues but I'm not sure if disk space is being upgraded, how I would go about re-partitioning etc. and making the space available to DA. Can any help guide?

Thanks!

 

[zEitEr]

Hello,

That depends on partitioning scheme you've got there, and in certain cases you can not enlarge a partition on a live system without using a rescue mode or temporary drive. Since the steps (if done wrong) might bring to a data loss, I'd rather not publish them here. Guides can be found in internet, and you are the only one to take all the responsibilities. If you're unsure, on how to enlarge a partition you'd better contact your server provider for a paid service, or hire somebody else for it.

If you still want to try it on your own and want a quick consulting here, kindly show output of the following commands:

lsblk -a

and

df -h -T

I won't give you direct steps, but might help to determine the technical possibility of it.

 

[Ohm J]

if you already using cloud, they might use the cloudinit to setup the server, so that meant it could running automatics disk partition extended.

I don't know how Vultture work. so becarefully incase you need to manual extended disk by yourself.

 

[floyd]

Regardless, always make a backup and have it stored somewhere else.

It sounds like this is a VPS. The VPS should extend the partition with no problem. But still make a backup. Very important.

 

[MopeyGecko]

It looks like the disk may have auto repartitioned with the plan change?

@zEitEr Including output from those commands before and after the plan change.

Before

[root@host ~]# lsblk -a
NAME   MAJ:MIN RM  SIZE RO TYPE MOUNTPOINTS
sr0     11:0    1 1024M  0 rom 
vda    253:0    0   80G  0 disk
└─vda1 253:1    0   80G  0 part /
[root@host ~]# df -h -T
Filesystem     Type      Size  Used Avail Use% Mounted on
devtmpfs       devtmpfs  4.0M     0  4.0M   0% /dev
tmpfs          tmpfs     1.8G     0  1.8G   0% /dev/shm
tmpfs          tmpfs     732M   71M  662M  10% /run
/dev/vda1      ext4       75G   62G  9.0G  88% /
tmpfs          tmpfs     366M  4.0K  366M   1% /run/user/1000
tmpfs          tmpfs     366M  4.0K  366M   1% /run/user/0
tmpfs          tmpfs     366M  4.0K  366M   1% /run/user/1009
tmpfs          tmpfs     366M  4.0K  366M   1% /run/user/1003

After

[root@host ~]#  lsblk -a
NAME   MAJ:MIN RM  SIZE RO TYPE MOUNTPOINTS
sr0     11:0    1 1024M  0 rom 
vda    253:0    0  160G  0 disk
└─vda1 253:1    0  160G  0 part /
[root@host ~]# df -h -T
Filesystem     Type      Size  Used Avail Use% Mounted on
devtmpfs       devtmpfs  4.0M     0  4.0M   0% /dev
tmpfs          tmpfs     3.8G     0  3.8G   0% /dev/shm
tmpfs          tmpfs     1.6G  8.8M  1.5G   1% /run
/dev/vda1      ext4      150G   62G   80G  44% /
tmpfs          tmpfs     769M  4.0K  769M   1% /run/user/1000
tmpfs          tmpfs     769M  4.0K  769M   1% /run/user/0

 

[Richard G]

It looks like the disk may have auto repartitioned with the plan change?

Yes it does, you can see that especially here in the before situation:

/dev/vda1 ext4 75G 62G 9.0G 88% /

and after:

/dev/vda1 ext4 150G 62G 80G 44% /

As you can see still 62G in use, but the total space went up from 75G to 150G making the percentage used drop down half from 88% to 44%.

 

[zEitEr]

It looks like the disk may have auto repartitioned with the plan change?

Yes, it does. Actually never worked with cloud compute instances from Vulture. Probably they offer this feature from a box.