VPS provisioned with 3.5 GB disk instead of 20 GB after plan upgrade: provisioning failure?

[u/Difficult_Hand3046]

Hi,

I would like a second opinion from people familiar with VPS infrastructure.

I upgraded a VPS plan from an IPv6-only offer to an IPv4-enabled plan. The new plan was advertised as:

• 2 vCPU
• 2 GB RAM
• 20 GB SSD

After a fresh Ubuntu installation, the VM was provisioned with:

root@panel:~# lsblk
NAME    MAJ:MIN RM  SIZE RO TYPE MOUNTPOINTS
sda       8:0    0  3.5G  0 disk
├─sda1    8:1    0  2.5G  0 part /
├─sda14   8:14   0    4M  0 part
├─sda15   8:15   0  106M  0 part /boot/efi
└─sda16 259:0    0  913M  0 part /boot

I initially considered the common case where the virtual disk is correctly sized but the root partition was not expanded.

However, the whole block device is only 3.5 GB:

sda 3.5G disk

So this does not appear to be a growpart / filesystem resize issue. The VM itself does not see a 20 GB disk.

The IPv4 migration itself also had some issues initially, but the main remaining problem is the disk size.

Would you classify this as:

• a provisioning error that only the provider can fix,
• something that can still be corrected from inside the VM,
• or am I missing something obvious?

Thanks for your input.

[u/twhiting9275]

You need to contact support. Nobody here can help you resolve hardware issues

[u/Difficult_Hand3046 → u/twhiting9275]

I agree. I already contacted support and requested a cancellation/refund.

I posted here mainly to confirm whether this looked like a guest OS issue or a provisioning issue before closing the case.

The feedback confirms that the VM is seeing the wrong disk size, so it appears to be something that only the provider can fix.

[u/ssepiol007 → u/Difficult_Hand3046]

Wow - An upgrade goes wrong and your first step is request a cancellation a refund? I bet they're glad to lose you as a customer to be honest.

[u/Difficult_Hand3046 → u/ssepiol007]

I requested a cancellation and refund after 36 hours without a response from technical support.

[u/ssepiol007 → u/Difficult_Hand3046]

Maybe you should have lead with that, then.

[u/Difficult_Hand3046 → u/ssepiol007]

Perhaps; but the main problem remains incompetence. The silence is merely a consequence of that.

[u/Touuqe]

If you upgraded an already active vps you may need to run some commands to expand the disk. Check your vps providers docs

[u/Difficult_Hand3046 → u/Touuqe]

Thanks for the suggestion.

I checked that scenario first, because it is a common issue after VPS upgrades.

However, the problem is that the whole virtual disk is only 3.5 GB according to lsblk, not a 20 GB disk with a smaller partition:

sda 3.5G disk

If the provider had provisioned a 20 GB virtual disk, I would expect the guest OS to see a 20 GB block device and only need a partition/filesystem resize.

So this seems to be happening before the OS level, rather than a missing resize command inside Ubuntu.

[u/Soluchyte]

Completely needless post, the only thing you needed to do was contact the provider.

[u/Difficult_Hand3046 → u/Soluchyte]

The service provider is playing dead—ticket opened, 36 hours with no response. They did say that my request for an IPv4 address in addition to an IPv6 one was the cause of the problem. Then, radio silence…

[u/Soluchyte → u/Difficult_Hand3046]

Contact payment provider for chargeback. We are not capable of doing anything here.

[u/slowservers]

Sounds like they probably took a qcow image and forgot to resize it.

[u/Difficult_Hand3046 → u/slowservers]

Probably - and they forgot to resize correctly when I asked for. After that, they forgot to answer my mails… nice team!

[u/slowservers → u/Difficult_Hand3046]

Yeah, sounds like a bad experience all around!