[SOLVED] Delete lxc/vm on a broken disk

[crc-error-79]

Hello, I have this lxc that was on a disk that has broke.

Since I have removed the disk, I can't remove the lxc. It returns "TASK ERROR: storage 'backup_locale' does not exist"

Can I simply remove its configuration file from the /etc/ folder, or there are other files / folder to delete?

 

[Moayad]

Since, you already removed the backup_local storage, you can then remove the 999.conf file in `/etc/pve/qemu-server/999.conf` safely. The something applies to LXC.

 

[charleslcso]

Hello

For my PVE 7.4-17, in /etc/pve/qemu-server/xxx.conf I have 1 VM .conf file because I have 1 VM. That's great.

Now for lxc the path should be /etc/pve/nodes/<node>/lxc/xxx.conf, right? I found one file that has the ID of my LXC.

Is moving this file enough? There seems to be other files relating to this LXC scattered in other directories...more cleaning needed?

My LXC has ID 102

/var/log/pve/tasks/5/UPID:360g9:000FF438:0075E673:653E1CE5:vzcreate:102:root@pam:
/var/log/pve/tasks/5/UPID:360g9:0010DFD8:007A3EB6:653E2805:vncproxy:102:root@pam:
/var/log/pve/tasks/6/UPID:360g9:000263D3:00102395:653E5506:vncproxy:103:root@pam:
/var/log/pve/tasks/6/UPID:360g9:00106857:0076DAA2:653E1F56:vncproxy:102:root@pam:
/var/log/pve/tasks/6/UPID:360g9:00107BBC:00776416:653E20B6:vncproxy:102:root@pam:
/var/log/pve/tasks/4/UPID:360g9:000060B2:0002129C:653E3104:vzstart:102:root@pam:
/var/log/pve/tasks/0/UPID:360g9:0000101D:000048B4:653E2C70:vzstart:102:root@pam:
/var/log/pve/tasks/E/UPID:360g9:00001630:000060F3:653E2CAE:move_volume:102:root@pam:
/var/log/pve/tasks/1/UPID:360g9:0010E066:007A4367:653E2811:vncproxy:102:root@pam:
/var/log/pve/tasks/9/UPID:360g9:0010C11B:007907C4:653E24E9:vncproxy:102:root@pam:
/var/log/pve/tasks/B/UPID:360g9:00001016:00004718:653E2C6B:vzstart:102:root@pam:
/var/log/pve/tasks/F/UPID:360g9:0010CA79:00794F3D:653E259F:vncproxy:102:root@pam:
/var/log/pve/tasks/8/UPID:360g9:000FF58F:0075EDD0:653E1CF8:vzstart:102:root@pam:
/var/log/pve/tasks/7/UPID:360g9:000FD1F9:007550FF:653E1B67:imgdel:102@debian11-template-128-1:root@pam:
/var/log/pve/tasks/A/UPID:360g9:00000989:00001ACC:653E2BFA:vzstart:102:root@pam:
/var/cache/lxc/apparmor/c4f50b60.0/lxc-102_<-var-lib-lxc>
/var/lib/rrdcached/db/pve2-vm/102
/var/lib/lxc/102
/sys/kernel/irq/102
/sys/devices/pci0000:00/0000:00:01.0/0000:03:00.0/msi_irqs/102
/sys/devices/system/node/node1/memory102
/sys/devices/system/memory/memory102
/sys/bus/memory/devices/memory102
/etc/pve/nodes/360g9/lxc/102.conf
/proc/irq/102
/proc/1771/task/1771/fd/102
/proc/1771/task/1771/fdinfo/102
/proc/1771/fd/102
/proc/1771/fdinfo/102
/proc/22326/task/22326/fd/102
/proc/22326/task/22326/fdinfo/102
/proc/22326/fd/102
/proc/22326/fdinfo/102
/run/lxc/lock/var/lib/lxc/.102
/run/lock/lxc/pve-config-102.lock

 

[Moayad]

Now for lxc the path should be /etc/pve/nodes/<node>/lxc/xxx.conf, right?

Yes, in this case you have to move LXC config file from `/etc/pve/nodes/<node>/lxc/xxx.conf`.