Hey everyone, I’m currently using proxmox to virtualize my OPNsense and another VM. Today when I went to create a third VM, everything crashed with I/O errors, and I realized my local-lvm was out of space. This was odd to me since I have a 1TB drive and only have two small VMs.
To my surprise, proxmox is only using 100GB of my disk. Can someone please guide me on how I can fix this without having to reinstall proxmox? I would prefer to have my OPNsense VM running while I fix this. Here are some diagnostics to help. Thanks
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.
Rules:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
I can’t give you specifics but generally what is likely necessary:
I’ll give that a shot with gparted on the weekend if all else fails. Thanks!
I would also make sure you have a Proxmox install USB ready to go just in case.
Edit: nevermind, sda3 is already being used. The lv group needs to be embiggened.
Would you know how I would go about doing that?
I’ve done it before, but there’s always a lot of googling involved. I think a combination of
vgdisplay
andvgextend
may help: https://www.redhat.com/sysadmin/resize-lvm-simpleIf sda3 is really <100GB it gets a lot scarier but is likely still doable.
I’m not a fan of Proxmox’s partitioning scheme and usually use a separate drive for the OS and the VMs because of this exact scenario.
That led me in the right direction!
Fixed it with:
Thank you!