# Why does my Droplet show almost 100% disk usage even after attaching a new volume?

Attaching a volume to a Droplet does not increase the Droplet’s root disk size. Instead, the volume is attached as a separate block device, and the Droplet’s main disk usage remains unchanged. To increase the size of the root disk, you must [resize the Droplet](https://docs.digitalocean.com/products/droplets/how-to/resize/index.html.md) to a larger plan.

If you need additional storage without resizing the Droplet, you can [attach a new volume](https://docs.digitalocean.com/products/volumes/how-to/create/index.html.md) and either [move data to it](https://docs.digitalocean.com/products/volumes/how-to/create/index.html.md#manage-files) or configure applications (such as log directories under `/var/log`) to write directly to the volume. This approach reduces usage on the root disk while keeping the operating system unchanged.

## Related Topics

[How do I fix a "system not initialized" error on multi-GPU Droplets?](https://docs.digitalocean.com/support/how-do-i-fix-a-system-not-initialized-error-on-multi-gpu-droplets/index.html.md): Make sure NVIDIA Fabric Manager is running and has the same version number as the GPU drivers.

[Why am I getting a Droplet autoscale pool error?](https://docs.digitalocean.com/support/why-am-i-getting-a-droplet-autoscale-pool-error/index.html.md): There may be an issue with the autoscale pool or Droplet configuration, the VPC network’s size, or resource limits on the team or datacenter.

[How to Troubleshoot Load Balancer Health Check Issues](https://docs.digitalocean.com/support/how-to-troubleshoot-load-balancer-health-check-issues/index.html.md): Health checks often fail due to firewalls or misconfigured backend server software.