Proxmox unlinked my VM's disk, and now it does not show up in the VM's storage

[Unbent3949]

Hello everyone, I am having some trouble right now, and I'm unsure how to solve it. My VM was running like normal, and after a while (probably after proxmox restarted) it disconnected one of the drives for that VM without allowing me to reconnect it. But it still shows up in the storage area of proxmox i would like to figure out how to reconnect the drive the right way, as that drive is associated with my NAS, so it is very important to have it reconnected instead of starting over
This is my proxmox version:
proxmox-ve: 7.2-1 (running kernel: 5.15.64-1-pve) pve-manager: 7.2-11 (running version: 7.2-11/b76d3178) pve-kernel-5.15: 7.2-13 pve-kernel-helper: 7.2-13 pve-kernel-5.4: 6.4-20 pve-kernel-5.15.64-1-pve: 5.15.64-1 pve-kernel-5.15.60-2-pve: 5.15.60-2 pve-kernel-5.15.60-1-pve: 5.15.60-1 pve-kernel-5.4.203-1-pve: 5.4.203-1 pve-kernel-5.4.34-1-pve: 5.4.34-2 ceph: 15.2.17-pve1 ceph-fuse: 15.2.17-pve1 corosync: 3.1.5-pve2 criu: 3.15-1+pve-1 glusterfs-client: 9.2-1 ifupdown: 0.8.36+pve2 ksm-control-daemon: 1.4-1 libjs-extjs: 7.0.0-1 libknet1: 1.24-pve1 libproxmox-acme-perl: 1.4.2 libproxmox-backup-qemu0: 1.3.1-1 libpve-access-control: 7.2-4 libpve-apiclient-perl: 3.2-1 libpve-common-perl: 7.2-3 libpve-guest-common-perl: 4.1-4 libpve-http-server-perl: 4.1-4 libpve-storage-perl: 7.2-10 libqb0: 1.0.5-1 libspice-server1: 0.14.3-2.1 lvm2: 2.03.11-2.1 lxc-pve: 5.0.0-3 lxcfs: 4.0.12-pve1 novnc-pve: 1.3.0-3 proxmox-backup-client: 2.2.7-1 proxmox-backup-file-restore: 2.2.7-1 proxmox-mini-journalreader: 1.3-1 proxmox-widget-toolkit: 3.5.1 pve-cluster: 7.2-2 pve-container: 4.2-3 pve-docs: 7.2-2 pve-edk2-firmware: 3.20220526-1 pve-firewall: 4.2-6 pve-firmware: 3.5-6 pve-ha-manager: 3.4.0 pve-i18n: 2.7-2 pve-qemu-kvm: 7.0.0-4 pve-xtermjs: 4.16.0-1 qemu-server: 7.2-4 smartmontools: 7.2-pve3 spiceterm: 3.2-2 swtpm: 0.7.1~bpo11+1 vncterm: 1.7-1 zfsutils-linux: 2.1.6-pve1

 

[fiona]

Hi,

Hello everyone, I am having some trouble right now, and I'm unsure how to solve it. My VM was running like normal, and after a while (probably after proxmox restarted) it disconnected one of the drives for that VM without allowing me to reconnect it.

That really shouldn't happen. How was the drive connected? Are you sure you didn't have a change pending? Many changes are only applied when the VM shuts down or is restarted from the outside.

But it still shows up in the storage area of proxmox i would like to figure out how to reconnect the drive the right way, as that drive is associated with my NAS, so it is very important to have it reconnected instead of starting over

Try using qm rescan --vmid <ID> replacing <ID> with the actual ID of your VM. Then the disk should show up as an unused disk in the VM's Hardware panel and you can Edit it in the GUI to re-attach.

 

[Unbent3949]

so unfortunately i am unable to try the rescan because the rescan is also trying to scan my nas associated storage on proxmox and that is unavailable right now because my nas is the one that has lost the storage

 

[Unbent3949]

ok removing the nfs share from the node made that work but im also getting an issue with truenas see the pool from that drive i just added back but i think that is a truenas issue