Recent content by SawKyrom

Still don't know what the 'Buffer' error means and why the CT would not be removed with the referenced commands, however removing the /etc/pve/lxc conf file in CLI did the trick at destroying the container from GUI. cd /etc/pve/lxc ls rm <lxcid>.conf Hope this helps someone else.

Attempting to remove (i.e. destroy) container in pve 6.4-13 and receive Error: storage 'Buffer' does not exist. Container not running and attempted the following at CLI: root@proxmox:~# pct unmount 204 root@proxmox:~# pct destroy 204 -force -destroy-unreferenced-disks -purge storage 'Buffer'...

What does qm listsnapshot <VM number> report for that VM? You said it's displayed in the web GUI, is it also listed in the CLI?

I've gotten I/O errors from having a full volume. lvs and check that your data is not 100%

I ran into similar problem and discovered I was using the wrong name for snapshot. Try the following: lvs (list snapshots on VG designated as snap_*) qm listsnapshot <VM number> (will list the snapshot name after -> designation) qm delsnapshot <VM number> <snapshot name> The snapshot name...

@CAppa2 I feel your pain. Proxmox evidently doesn't have a safe guard to prevent LVM-thin volume from exceeding storage capacity and once this occurs, VM's are rendered inoperable with I/O errors. From experience, I would definitely NOT try lvresize command. In my case, doing so resulted in...

So there is no way to decrease the LVM thin volume without erasing the entire database?

Anyone have suggestions for fixing the following error: EXT4-fs error (device dm-15): ext4_mb_generate_buddy:747: group 1, block bitmap and bg descriptor inconsistent: 2616 vs 613 free clusters after lvresize --size +1G --poolmetadatasize +16M <VG/LV> I was attempting to increase the LVM-thin...

@bbgeek17 Thank you for the suggestion. The code entered returned error: -bash: awk{print $1}: command not found. However, using your code I was able to tease out the correct means to removing snapshot from CLI: lvs (list snapshots on VG designated as snap_*) qm listsnapshot <VM number> (will...

For anyone who urgently needs space and can sacrifice a VM in order to free LVM-thin space and thus regain functionality, you can use the following command to permanently remove a sacrificial VM: lvs remove <vm name> lvs will show LV data with <100% and should function once more. *Do NOT try...

Proxmox stopped working secondary to LVM full storage. LVS command shows data 100% and several files labeled snap_vm... I would like to delete these snapshots so that I can restore functionality for the VM's, which currently will not load secondary to full storage. I attempted: qm...

@bbgeek17 THANKS!!! Your article is spot on. I deleted the fstab.swp file and can now edit etc/fstab. If anyone else finds this chat, you can also follow these steps as outlined in https://www.getsetsolution.com/solved-error-reading-lock-file 1. Navigate to your Project folder: cd /etc 2...

@bbgeek17 Thank you for the reply. There is plenty of storage space on all drives, but you bring up a good point... There was an episode previously where syslog file overfilled the boot SSD with errors from an USB device. I deleted the syslog file, removed the device and all was forgotten. I...

Any attempt to edit the /etc/fstab file in Proxmox VE 6.4-13 with nano results in [ Error reading lock file /etc/.fstab.swp: Not enough data read ]. The file is empty and will not save any changes. Please see following file status information: cat etc/fstab # <file system> <mount point>...

Any suggestions on troubleshooting poor network performance when serving media would be much appreciated. I have Linux proxmox 5.4.124-1 running Virtual Environment 6.4-13. Hardware is 12 core Xeon E2-1650 v2 64 GiB ECC RAM. pfSense is the network router/firewall via VM, wireless interface...