[SOLVED] Proxmox not working as I fully ran out of space

Vaillant

New Member
Jul 3, 2023
16
4
3
Hello all,

I'm a newbie in everything and I'm really in a pickle at the moment.

I was having some issue with my zfs and almost resolved them all. Albeit, I was running low on space not really knowing why. I was going to delete some vm today but this morning nothing was working as I had forgotten some backup automation which somehow ate the whole disk and crashed the node. I'm able to ssh into the node but the visual interface does not work.

Here is a screenshot of the zfs and the hard drive.
Screenshot 2025-04-07 201201.jpg

If a kind soul could guide me on how to resolve my situation, I would be very grateful.
I'm willing to delete vm-200 to free up space but do not know how to do that from the command line.
 
Hi @Vaillant

I can see issue with space on rpool/ROOTand rpool/DATA

I do not know what issues you had with ZFS (better describe in the post).

Check the rpool/ROOT file system for large files / folders.

du -h --max-depth=1 /

check also sub dirs (example):

du -sh /var/log/*
du -sh /var/tmp/*
du -sh /root/*
du -sh /var/*

For rpool/DATA

Check old snapshots:
zfs list -t snapshot

The old snapshots you can remove with Example:
zfs destroy rpool/data/vm-200-state-BeforeUPS
zfs destroy rpool/data/vm-200-state-Updated
 
Last edited:
  • Like
Reactions: Vaillant
I think you want use the command qm destroy <your vm id>

https://pve.proxmox.com/pve-docs/qm.1.html
Hi @Vaillant

I can see issue with space on rpool/ROOTand rpool/DATA

I do not know what issues you have with ZFS (better describe in the post).

Check the rpool/ROOT file system for large files / folders.

du -h --max-depth=1 /

check also sub dirs (example):

du -sh /var/log/*
du -sh /var/tmp/*
du -sh /root/*
du -sh /var/*

For rpool/DATA

Check old snapshots:
zfs list -t snapshot

The old snapshots you can remove with Example:
zfs destroy rpool/data/vm-200-state-BeforeUPS
zfs destroy rpool/data/vm-200-state-Updated
I wanted to thanks both of you I was able to remove the snapshots and that was enough to unlock the server. However, removing vm200 may not have fully worked.

While doing it in Putty I got the following
error.jpg

and once I was able to boot the interface I got this error
Error: storage 'local-zfs4' does not exist

But I'm so glad thanks to your help my node is working again.
 
  • Like
Reactions: Lukas Moravek