New installation can't see VM

[arky_]

I have damaged 2 disks on which the Proxmox system was installed. The VMs were on 2 others configured in mirror and zfs (one of these disks also failed).

After reinstalling the system and reconnecting the drive + pool (oldpool) zfs, I can't see my VMs in the GUI. In the console you can already see that they are physically.

Question: How do I restore all VMs to be visible in the GUI?
Possibly How to remove unnecessary VM?

root@proxmox1:~# zfs list
NAME                            USED  AVAIL     REFER  MOUNTPOINT
newpool                        62.3G  1.70T      104K  /newpool
newpool/VMBackup               21.8G  1.70T     21.8G  /newpool/VMBackup
newpool/VMData                 40.6G  1.70T     40.6G  /newpool/VMData
oldpool                         768G   131G      104K  /oldpool
oldpool/ROOT                    114G   131G       96K  /oldpool/ROOT
oldpool/ROOT/pve-1              114G   131G      114G  /
oldpool/data                    447G   131G       96K  /oldpool/data
oldpool/data/vm-101-disk-0      135G   131G      135G  -
oldpool/data/vm-106-disk-0     59.2G   131G     37.1G  -
oldpool/data/vm-106-disk-1       60K   131G       60K  -
oldpool/data/vm-106-state-s1    786M   131G      786M  -
oldpool/data/vm-107-disk-0     1.88G   131G     1.50G  -
oldpool/data/vm-107-disk-1      295M   131G      214M  -
oldpool/data/vm-107-state-d1    312M   131G      312M  -
oldpool/data/vm-107-state-s2    259M   131G      259M  -
oldpool/data/vm-109-disk-1     36.9M   131G     36.2M  -
oldpool/data/vm-109-state-s1   79.8M   131G     79.8M  -
oldpool/data/vm-110-disk-0     13.5G   131G     13.5G  -
oldpool/data/vm-115-disk-0     18.2G   131G     18.2G  -
oldpool/data/vm-115-disk-1     18.1G   131G     18.1G  -
oldpool/data/vm-116-disk-0     12.1G   131G     8.74G  -
oldpool/data/vm-116-state-s1   1.14G   131G     1.14G  -
oldpool/data/vm-117-disk-0     93.1G   131G     48.9G  -
oldpool/data/vm-117-state-s15  5.37G   131G     5.37G  -
oldpool/data/vm-117-state-s16  1.98G   131G     1.98G  -
oldpool/data/vm-117-state-s17  5.93G   131G     5.93G  -
oldpool/data/vm-120-disk-0     15.3G   131G     15.3G  -
oldpool/data/vm-121-disk-0     28.7M   131G     28.4M  -
oldpool/data/vm-121-disk-1     2.22G   131G     1.56G  -
oldpool/data/vm-124-disk-0     15.9G   131G     10.5G  -
oldpool/data/vm-124-state-s1   2.88G   131G     2.88G  -
oldpool/data/vm-124-state-s2   2.70G   131G     2.70G  -
oldpool/data/vm-124-state-s3   2.58G   131G     2.58G  -
oldpool/data/vm-124-state-s4   3.42G   131G     3.42G  -
oldpool/data/vm-127-disk-0     27.3G   131G     27.3G  -
oldpool/data/vm-127-disk-1       76K   131G       76K  -
oldpool/data/vm-128-disk-0     4.19G   131G     3.72G  -
oldpool/data/vm-128-state-S2   1.91G   131G     1.91G  -
oldpool/data/vm-128-state-s1   1.38G   131G     1.38G  -
oldpool/vm-102-disk-0           206G   284G     52.8G  -
rpool                          1.28G   227G      104K  /rpool
rpool/ROOT                     1.24G   227G       96K  /rpool/ROOT
rpool/ROOT/pve-1               1.24G   227G     1.24G  /
rpool/data                       96K   227G       96K  /rpool/data

 

[dcsapak]

that are only the vm disks. the config is stored on the disk pve was installed, so that is not here
you can either
* recreate the vm config from memory (e.g. by creating a new one with similar settings) and use 'qm rescan'
so that pve puts the found disk images into the vm config as 'unused', then you can edit those and add it as the correct disk
* you restore the config from backup (if you have one). if you have configured a backup storage, you can navigate there and click 'show configuration' in the gui

 

[arky_]

Thank you for your response. You showed me the way and I found copies of the VM files (/etc/pve/nodes/proxmox1/qemu-server) on the second server (because both were in Claster) and here I have a question.
For example, I want to restore from a copy of VM 101.conf on a new server or if I just copy this file to the new server to the same path?
What to do if there is already a file with the same name in the new location?
Anything else I need to do?

 

[bbgeek17]

You have two options:

1) If the new VM101 is disposable - remove it to free up the ID
2) Very carefully update the VM you are recovering to new un-used ID in all pertinent places. This will include updating your volumes, ie renaming them to match the new VM-ID.

For both (1) and (2) you need to also make the storage (old pool) available to PVE. That means you need to define appropriate storage type via UI/CLI/manually and make PVE aware of it. You then will need to edit your VM configuration file to point to new storage pool (if the name is now different).

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox