By brain56
I have a 25 GB, 2 GB RAM Perforce droplet that I resized to 80 GB, 4 GB RAM. The resize seemed to have gone smoothly without error or warning. However, after turning the droplet back on, I am unable to access it with P4V, P4Admin, nor the web console.
I can see that there’s CPU usage up to 4%, and Disk I/O up to 750 kB/s, but network Bandwidth remains at 0.
SSH and connection attempts via Command Prompt just time out, and the web console just stays on the waiting stage.
I’ve tried power cycling and turning it off and on again several times. Any suggestions? Thanks!
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
Accepted Answer
The issue I was having was caused by the drive being at 100% capacity (25GB/25GB) when I resized it.
Speaking with DigitalOcean Support (who are terrific, btw!), they said:
When resizing the Droplet, the block device is increased when the resize uses the CPU, Memory and Disk option. In most cases, the next boot will detect this within the software running on the Droplet and kick off some steps to update this. In short, the disk has increased in size but needs to update to be properly reflected.
This can fail however at 100% disk usage ( as some space is still required for temporary files ) or when the particular release of software installed on the Droplet doesn’t accomplish this. The platform isn’t able to determine this however, as we limit the access to the partition/data of the Droplet.
The solution is as follows:
Turn on the droplet.
In Windows, using PowerShell, SSH into the droplet using the command:
ssh -i "C:\Users\PATH_TO_SSH_FILE" root@XXX.XXX.XXX.XXX
Use the following command to analyze disk usage:
df -h
If you’re in the same situation as me, you’ll see that your disk might be at 100% capacity.
From here, you can use the rm command to delete files until you get back to 99% capacity. I deleted some P4 logs, some of which can be hundreds of Megabytes large!
Turn off the the droplet, and then turn it back on again. Repeat the steps above and run df -h and verify that your disk has increased in size. Mine went from 25 GB to the 80 GB resize.
Et voila~!
Hey!
It sounds like your Droplet might’ve had a network misconfig after the resize. Sometimes the network interface doesn’t come up cleanly, especially if cloud-init or network configs get messed up.
If you can, try checking the network settings via the Recovery Console or boot into Recovery Mode to inspect the logs.
Try the answer from the following thread: Networking not working after Droplet resize
And if you’re still stuck, definitely reach out to DigitalOcean support so they can advise you further.
- Bobby
Heya, @brain56
Try booting your Droplet into recovery mode and check the network settings. Look at the netplan or interfaces file, depending on your OS. It’s possible the network config didn’t update properly after the resize.
Also, check the logs in /var/log/syslog or run dmesg to see if the system is stuck on something like a file system check. Make sure SSH is enabled and listening on the right interface.
If you’re still stuck, you can reach out to our support team and they will help you!
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and SMBs
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.