New to Proxmox VE- Likely a simple fix (failing backups after removing local-lvm)

[Neo1337]

Hey everyone,

I was super excited to setup proxmox & got it spun up with a ubuntu vm & pihole deployment. I was following a Network Chuck guide where it advised to remove local-lvm to get more space (after I setup a VM already).

Now when I run my backups I get errors as below. I tried modifying the /etc/pve/storage.cfg and messing with it but cannot seem to figure out where the LVM is being referenced to remove it completely. I have not restarted the server yet either.

^this is my current config (The original didn't reference vgname or nodes)



Stop
INFO: starting new backup job: vzdump 100 --storage local --remove 0 --mode snapshot --compress zstd --node ProxMox --notes-template '{{guestname}}'
INFO: Starting Backup of VM 100 (qemu)
INFO: Backup started at 2022-11-27 10:10:34
INFO: status = running
INFO: VM Name: Ubunutu-Svr
INFO: include disk 'scsi0' 'local-lvm:vm-100-disk-0' 30G
ERROR: Backup of VM 100 failed - storage 'local-lvm' does not exist
INFO: Failed at 2022-11-27 10:10:34
INFO: Backup job finished with errors
TASK ERROR: job errors


What am I missing?

 

[BobhWasatch]

Apparently your VM disks were on the storage you removed. The default setup of Proxmox on a single disk is to store VM disks on a thin provisioned lvm. Not sure why this guide says to remove it but doing so without ensuring it is not in use or making backups is a bad plan.

 

[Dunuin]

Jup, if you want to get access to your VM again, you would need to revert everything backup. So you will have to add that local-lvm storage again at Datacenter -> Storage -> Add -> LVM-Thin

 

[Neo1337]

Apparently your VM disks were on the storage you removed. The default setup of Proxmox on a single disk is to store VM disks on a thin provisioned lvm. Not sure why this guide says to remove it but doing so without ensuring it is not in use or making backups is a bad plan.

I am confused on this because my VM is actively running without an issue. I did create a backup off the proxmox server that is on my computer, I am simply looking for how to repair the backup configuration as I ran out of google info/ideas.

 

[Neo1337]

Jup, if you want to get access to your VM gain, you would need to revert everything backup. So you will have to add that local-lvm storage again at Datacenter -> Storage -> Add -> LVM-Thin

Is a gain an assigned storage container or something? There's no way to modify the configuration to change where the backup saves? The VM is running totally fine, its just the backups looking to the LVM.

I did offload backups from Proxmox to my local W10 PC before making any of these changes, I simply noticed I couldn't create new one's after I removed the LVM.

 

[Dunuin]

The problem isn't your backup configuration, but that you deleted the storage your VMs are stored on. Reboot the PVE host, and your VM won't be able to run. Your PVE installation isn't totally screwed up yet, as you only removed the "local-lvm" storage but not actual LVM-Thin pool it is pointing to. But you will have to create that "local-lvm" storage again.

 

[Neobin]

I am confused on this because my VM is actively running without an issue. I did create a backup off the proxmox server that is on my computer, I am simply looking for how to repair the backup configuration as I ran out of google info/ideas. View attachment 43815

If you shutdown that VM or at the latest reboot the PVE-host, it will not start again without its assigned storage(-link)...

 

[Dunuin]

A pvesm add lvmthin local-lvm --content rootdir,images --disable 0 --thinpool data --vgname pve should add it again.

 

[Neo1337]

The problem isn't your backup configuration, but that you deleted the storage your VMs are stored on. Reboot the PVE host, and your VM won't be able to run. Your PVE installation isn't totally screwed up yet, as you only removed the "local-lvm" storage but not actual LVM-Thin pool it is pointing to. But you will have to create that "local-lvm" storage again.

Thank you!

 

[Neo1337]

A pvesm add lvmthin local-lvm --content rootdir,images --disable 0 --thinpool data --vgname pve should add it again.

That fixed it, my love for you is eternal. I will spend more time researching this virtualization platform before blindly following youtube . VM is online & backups are working again.

 

[Neo1337]

If you shutdown that VM or at the latest reboot the PVE-host, it will not start again without its assigned storage(-link)...

Thanks a bunch for the intel man