Problem with zfs over iSCSI

Sebastian Salmhofer

Renowned Member
Nov 11, 2012
20
2
68
Paraguay
Hi,

I have the following setup: 2 pve nodes in a cluster, the first node has a VM with NexentaStor running on local storage. The Nexenta VM has some disks passed trough and configured in RAIDz1 and is configured as an iSCSI target and there is also a NFS share for ISOs.
I want to use the zfs over iSCSI option for shared storage and the ability to take snapshots and so on. I think I configured everything correctly and everything looks fine. I can see the storage on both nodes, it shows the size and so on, and I can create a VM and it creates a volume that also shows up on the NexentaStor GUI. So everything looks perfect but I can't start the VM. It gives me this Error:
kvm: -drive file=iscsi://192.168.2.20/iqn.2010-08.org.illumos:02:8b729e6f-11fa-6c12-e7b2-e4384a2dc548/0,if=none,id=drive-virtio0,format=raw,cache=none,aio=native,detect-zeroes=on: iSCSI: Failed to connect to LUN : Failed to log in to target. Status: Target not found(515)
TASK ERROR: start failed: command '/usr/bin/kvm -id 101 -chardev 'socket,id=qmp,path=/var/run/qemu-server/101.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -pidfile /var/run/qemu-server/101.pid -daemonize -smbios 'type=1,uuid=6ac84f91-ad24-4c9c-b512-beeb93cb2285' -name WindowsServer-1 -smp '8,sockets=1,cores=8,maxcpus=8' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000' -vga std -vnc unix:/var/run/qemu-server/101.vnc,x509,password -no-hpet -cpu 'host,hv_spinlocks=0x1fff,hv_vapic,hv_time,hv_relaxed,+kvm_pv_unhalt,+kvm_pv_eoi' -m 4096 -k de -device 'pci-bridge,id=pci.1,chassis_nr=1,bus=pci.0,addr=0x1e' -device 'pci-bridge,id=pci.2,chassis_nr=2,bus=pci.0,addr=0x1f' -device 'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2' -device 'usb-tablet,id=tablet,bus=uhci.0,port=1' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:9cd2a1478a26' -drive 'file=/mnt/pve/shared-data-storage/template/iso/de_server_install_disc_windows_server_2012_essentials_x64_dvd_1022283.iso,if=none,id=drive-ide2,media=cdrom,aio=threads' -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200' -drive 'file=iscsi://192.168.2.20/iqn.2010-08.org.illumos:02:8b729e6f-11fa-6c12-e7b2-e4384a2dc548/0,if=none,id=drive-virtio0,format=raw,cache=none,aio=native,detect-zeroes=on' -device 'virtio-blk-pci,drive=drive-virtio0,id=virtio0,bus=pci.0,addr=0xa,bootindex=100' -netdev 'type=tap,id=net0,ifname=tap101i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=32:62:38:34:61:32,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300' -rtc 'driftfix=slew,base=localtime' -global 'kvm-pit.lost_tick_policy=discard'' failed: exit code 1​

If anyone knows what the problem is please tell me, I am out of ideas.

Thanks
Sebastian Salmhofer
 
What output do you get from both proxmox nodes running this command?
iscsiadm -m discovery -t sendtargets -p <IP_ADDRESS_TARGET>

You should have configured Nexenta to allow access from both nodes identified by their initiator name like initiator-name=iqn.1993-08.org.debian:01:9cd2a1478a26
 
  • Like
Reactions: Sebastian Salmhofer
Yup, that's the problem. Thank you very much! I didn't update the iqn after I reistalled the NexentaStor VM because it had a problem.
Works perfectly fine now, thanks again :)
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!