Rebooted and ZFS over ISCSI is no longer working

retali8

New Member
Oct 29, 2024
1
0
1
I was upgrading my main server that has ZFS running on it and when I got it all back up and running and restarted targetclid my Proxmox VM's aren't able to start. I see a record at /etc/iscsi/send_targets/10.100.100.2,3260/st_config and noticed it is set for discovery.startup = manual. Does that mean I need to manually execute some commands to reconnect the Proxmox nodes so they connect over ISCSI again? I don't know what commands to run to make it try and reconnect. I see that targetclid is listening on 3260 on my ZFS server and I tried to reboot each Proxmox node and none of them established a connection and the VM's still will not start.

One of the VM's returns the error message:

Task viewer: VM 100 - Start

kvm: -device scsi-hd,bus=virtioscsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0,id=scsi0,bootindex=100: unwanted /dev/sg*
TASK ERROR: start failed: QEMU exited with code 1

while the other VM returns:

Task viewer: VM 101 - Start
kvm: -drive file=iscsi://10.100.100.2/iqn.2003-01.org.linux-iscsi.beast.x8664:sn.0b965daca442/2,if=none,id=drive-scsi0,format=raw,cache=none,aio=io_uring,detect-zeroes=on: iSCSI: Failed to connect to LUN : SENSE KEY:ILLEGAL_REQUEST(5) ASCQ:LOGICAL_UNIT_NOT_SUPPORTED(0x2500)
TASK ERROR: start failed: QEMU exited with code 1
 

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!