iSCSI Storage Not Sharing Across Nodes

[ThatNaysayer`]

So I have been trying to figure this out for a while and wondering if there was a good fix for this. When I add a new LVM attached to an iSCSI share to a single node, it will show up only on the node that I was connected to when I added it. With all other nodes showing it with an unknown status. When the other nodes reboot the storage appears connected just fine.

I am wondering if there is a way to force the nodes to connect without a reboot which cannot be done during the day.

 

[bbgeek17]

You can try " pvesm scan lvm" or "/sbin/vgscan --ignorelockingfailure --mknodes"

A VM migration will also activate the volume group without reboot.

Another thing to try "systemctl try-reload-or-restart pvedaemon pveproxy pvestatd pvescheduler"

I've seen the behavior your described but it was never enough of the pain point to figure out the solution just for the sake of clean UI. Especially since it never happens with our storage.
Creating a VM on node with unknown status with storage on the new LVM should activate it as well.

---

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

 

[ThatNaysayer`]

Interestingly the volume is found when I run /sbin/vgscan --ignorelockingfailure --mknodes but when I run pvesm scan lvm it doesnt show up in the list.

Similarly when I do a migration of the VM in a stopped state I get the error TASK ERROR: can't activate LV '/dev/HATest/vm-310-disk-0': Cannot process volume group HATest

 

[bbgeek17]

There may be a few causes of this behavior. You need to check/tail the journal on source and destination to get more details around the time of error.

---

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

 

[Mrbibi]

Any news?

I have the same problem...

EDIT: Solved, it was a right management issue on my Syno NAS.