Attach iscsidirect storage

R

RocketSam

Member
Proxmox Subscriber
Feb 20, 2024
37
5
8
Hello dear Proxmox Developers, Support Engineers and Comminuty Members.
I'm trying to add storage as User Mode iSCSI Backend (iscsidirect).
Code: 
/etc/pve/storage.cfg
iscsidirect: iscsi-direct
        portal 172.24.132.152
        target iqn.2010-06.com.nutanix:iscsidisksforpvedirect-f97645ea-c3e3-45bb-9e3c-ced98ea67457

pve_iscsidirect_1.png

But unfortunately I can't select a device on VM creation.
pve_iscsidirect_2.png

Even though I can get LUNs listed with iscsiadm.
Code: 
# iscsiadm --mode discovery --type sendtargets --portal 172.24.132.152
172.24.132.152:3260,1 iqn.2010-06.com.nutanix:iscsidisksforpvedirect-f97645ea-c3e3-45bb-9e3c-ced98ea67457
172.24.132.153:3260,1 iqn.2010-06.com.nutanix:iscsidisksforpvedirect-f97645ea-c3e3-45bb-9e3c-ced98ea67457
172.24.132.154:3260,1 iqn.2010-06.com.nutanix:iscsidisksforpvedirect-f97645ea-c3e3-45bb-9e3c-ced98ea67457
172.24.132.155:3260,1 iqn.2010-06.com.nutanix:iscsidisksforpvedirect-f97645ea-c3e3-45bb-9e3c-ced98ea67457

What additional information should I provide to get some advices?
Thanks!

Code: 
# iscsi-ls -i iqn.1993-08.org.debian:01:ca3bbfba8185 -s iscsi://172.24.132.152
Target:iqn.2010-06.com.nutanix:iscsidisksforpvedirect-f97645ea-c3e3-45bb-9e3c-ced98ea67457 Portal:172.24.132.155:3260,1
Lun:1    Type:DIRECT_ACCESS (Size:127G)
Lun:0    Type:DIRECT_ACCESS (Size:127G)
Target:iqn.2010-06.com.nutanix:iscsidisksforpvedirect-f97645ea-c3e3-45bb-9e3c-ced98ea67457 Portal:172.24.132.154:3260,1
Lun:1    Type:DIRECT_ACCESS (Size:127G)
Lun:0    Type:DIRECT_ACCESS (Size:127G)
Target:iqn.2010-06.com.nutanix:iscsidisksforpvedirect-f97645ea-c3e3-45bb-9e3c-ced98ea67457 Portal:172.24.132.153:3260,1
Lun:1    Type:DIRECT_ACCESS (Size:127G)
Lun:0    Type:DIRECT_ACCESS (Size:127G)
Target:iqn.2010-06.com.nutanix:iscsidisksforpvedirect-f97645ea-c3e3-45bb-9e3c-ced98ea67457 Portal:172.24.132.152:3260,1
Lun:1    Type:DIRECT_ACCESS (Size:127G)
Lun:0    Type:DIRECT_ACCESS (Size:127G)

proxmox-ve: 8.1.0 (running kernel: 6.5.11-8-pve)
pve-manager: 8.1.4 (running version: 8.1.4/ec5affc9e41f1d79)
proxmox-kernel-helper: 8.1.0
proxmox-kernel-6.5: 6.5.11-8
proxmox-kernel-6.5.11-8-pve-signed: 6.5.11-8
ceph: 18.2.1-pve2
ceph-fuse: 18.2.1-pve2
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx8
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-4
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.0
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.3
libpve-access-control: 8.1.1
libpve-apiclient-perl: 3.3.1
libpve-common-perl: 8.1.0
libpve-guest-common-perl: 5.0.6
libpve-http-server-perl: 5.0.5
libpve-network-perl: 0.9.5
libpve-rs-perl: 0.8.8
libpve-storage-perl: 8.0.5
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 5.0.2-4
lxcfs: 5.0.3-pve4
novnc-pve: 1.4.0-3
proxmox-backup-client: 3.1.4-1
proxmox-backup-file-restore: 3.1.4-1
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.2.3
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.4
proxmox-widget-toolkit: 4.1.3
pve-cluster: 8.0.5
pve-container: 5.0.8
pve-docs: 8.1.3
pve-edk2-firmware: 4.2023.08-4
pve-firewall: 5.0.3
pve-firmware: 3.9-1
pve-ha-manager: 4.0.3
pve-i18n: 3.2.0
pve-qemu-kvm: 8.1.5-2
pve-xtermjs: 5.3.0-3
qemu-server: 8.0.10
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.2-pve1
 
Last edited:
bbgeek17 said:
I believe iscsi-direct depends on iscsi-ls binary, which is not installed by default.
Take a look here:
https://forum.proxmox.com/threads/using-iscsi-lun-directly.119369/

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Click to expand...
Thanks for a quick reply, bbgeek17!
I've got libiscsi-bin package installed and therefor ls-iscsi is available for me. It was installed prior the problem described in the thread had happened.
iscsi-ls also discovers presented LUNs. I've updated my initial message.
 
bbgeek17 said:
I dont know if thats the cause but the target name in your storage.cfg is completely different from the target name returned by either iscsi-ls or iscsiadm.

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Click to expand...
Oh crap, it was a dumbest mistake. I've updated storage.cfg and my post accordingly but it did not solve the issue. :(
1712595844020.png
 
Last edited:
Have you checked the log?
Perhaps try CLI ("qm set" based on output of "pvesm list").
Or, perhaps you need to restart services: systemctl try-reload-or-restart pvedaemon pveproxy pvestatd pvescheduler
Or, even reboot the system. It seems like things might be ok configuration wise, but without having hands on the system and access to full combination of command output and logs - its hard to guide you.

If the storage vendor was friendly to Proxmox, they could have been a source of information :)

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
You must log in or register to reply here.
Top Bottom
Back