I've been tinkering with a zimacube, and I finally got my SATA drives for it. I had a handful of SSD SATA drives in there so I could experiment. I removed all of those from the storage.cfg after deleting the pools and replacing the drives, and probably did some other things getting the storage bits initialized. This is probably super simple, but all of my other nodes are just mini-PCs and I've never had to do anything storage related :| I've been all over the place looking at different posts where people have had similar issues or are getting the same errors I am, but their situations are usually because something is broken and not because they accidentally unmounted the vm's disk.
Here's my problem.. . I think I accidentally detached the partition that contains an existing VM from the lvm pool (?) The VM disk file is 120GB. I know it's on there somewhere... I just don't know how to get it mounted properly (and put back in the lvm pool or wherever it needs to be).
root@Voyager:~# qm rescan
rescan volumes...
no such logical volume pve/data
root@Voyager:~# pvs
PV VG Fmt Attr PSize PFree
/dev/nvme0n1p1 Pool lvm2 a-- 12.00m 12.00m
/dev/nvme4n1p3 pve lvm2 a-- 237.47g <160.11g
root@Voyager:~# vgs
VG #PV #LV #SN Attr VSize VFree
Pool 1 0 0 wz--n- 12.00m 12.00m
pve 1 2 0 wz--n- 237.47g <160.11g
root@Voyager:~# lvs
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
root pve -wi-ao---- <69.37g
swap pve -wi-ao---- 8.00g
root@Voyager:~# pveversion -v
proxmox-ve: 8.3.0 (running kernel: 6.8.12-2-pve)
pve-manager: 8.3.1 (running version: 8.3.1/fb48e850ef9dde27)
proxmox-kernel-helper: 8.1.0
proxmox-kernel-6.8.12-2-pve-signed: 6.8.12-2
proxmox-kernel-6.8.12-1-pve-signed: 6.8.12-1
proxmox-kernel-6.8.4-2-pve-signed: 6.8.4-2
ceph: 18.2.4-pve3
ceph-fuse: 18.2.4-pve3
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx11
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.1
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.4
libpve-access-control: 8.2.0
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.0.10
libpve-cluster-perl: 8.0.10
libpve-common-perl: 8.2.9
libpve-guest-common-perl: 5.1.6
libpve-http-server-perl: 5.1.2
libpve-network-perl: 0.10.0
libpve-rs-perl: 0.9.1
libpve-storage-perl: 8.3.0
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.5.0-1
proxmox-backup-client: 3.3.1-1
proxmox-backup-file-restore: 3.3.2-1
proxmox-firewall: 0.6.0
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.3.1
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.7
proxmox-widget-toolkit: 4.3.3
pve-cluster: 8.0.10
pve-container: 5.2.2
pve-docs: 8.3.1
pve-edk2-firmware: 4.2023.08-4
pve-esxi-import-tools: 0.7.2
pve-firewall: 5.1.0
pve-firmware: 3.14-2
pve-ha-manager: 4.0.6
pve-i18n: 3.3.2
pve-qemu-kvm: 9.0.2-4
pve-xtermjs: 5.3.0-3
qemu-server: 8.3.2
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.6-pve1
Here's my problem.. . I think I accidentally detached the partition that contains an existing VM from the lvm pool (?) The VM disk file is 120GB. I know it's on there somewhere... I just don't know how to get it mounted properly (and put back in the lvm pool or wherever it needs to be).
root@Voyager:~# qm rescan
rescan volumes...
no such logical volume pve/data
root@Voyager:~# pvs
PV VG Fmt Attr PSize PFree
/dev/nvme0n1p1 Pool lvm2 a-- 12.00m 12.00m
/dev/nvme4n1p3 pve lvm2 a-- 237.47g <160.11g
root@Voyager:~# vgs
VG #PV #LV #SN Attr VSize VFree
Pool 1 0 0 wz--n- 12.00m 12.00m
pve 1 2 0 wz--n- 237.47g <160.11g
root@Voyager:~# lvs
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
root pve -wi-ao---- <69.37g
swap pve -wi-ao---- 8.00g
root@Voyager:~# pveversion -v
proxmox-ve: 8.3.0 (running kernel: 6.8.12-2-pve)
pve-manager: 8.3.1 (running version: 8.3.1/fb48e850ef9dde27)
proxmox-kernel-helper: 8.1.0
proxmox-kernel-6.8.12-2-pve-signed: 6.8.12-2
proxmox-kernel-6.8.12-1-pve-signed: 6.8.12-1
proxmox-kernel-6.8.4-2-pve-signed: 6.8.4-2
ceph: 18.2.4-pve3
ceph-fuse: 18.2.4-pve3
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx11
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.1
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.4
libpve-access-control: 8.2.0
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.0.10
libpve-cluster-perl: 8.0.10
libpve-common-perl: 8.2.9
libpve-guest-common-perl: 5.1.6
libpve-http-server-perl: 5.1.2
libpve-network-perl: 0.10.0
libpve-rs-perl: 0.9.1
libpve-storage-perl: 8.3.0
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.5.0-1
proxmox-backup-client: 3.3.1-1
proxmox-backup-file-restore: 3.3.2-1
proxmox-firewall: 0.6.0
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.3.1
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.7
proxmox-widget-toolkit: 4.3.3
pve-cluster: 8.0.10
pve-container: 5.2.2
pve-docs: 8.3.1
pve-edk2-firmware: 4.2023.08-4
pve-esxi-import-tools: 0.7.2
pve-firewall: 5.1.0
pve-firmware: 3.14-2
pve-ha-manager: 4.0.6
pve-i18n: 3.3.2
pve-qemu-kvm: 9.0.2-4
pve-xtermjs: 5.3.0-3
qemu-server: 8.3.2
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.6-pve1