ISCSI not shown after reboot clients / before reboot it was working

[onionsjk]

Hello there,

I am here to get some techincal advice on trueNAS.
Currently, I am building three Virtualbox systems
- one trueNAS for iSCSI, one client1 (window server 2019) and
one client2 (window server 2019) to test faileover functions.

With help of many youtube channels, I managed to start iSCSI service
and iscsi-intiator to connect iSCSI from two client windows.
I used ZVOL to make iSCSI.
Now I can switch online/offline manually from either side of computers.
I thought I am ready to proceed for next steps of test.

But the problem comes after reboot the clients. After reboot, iSCSI disk is
not shown on Disk management tools. Well, sometime it comes online but only to one
of the machines. Even after I got message "succssfully connected to trueNAS" , the disk
remain unvisible.

Could anybody tell me why it happend and how to overcome this ?
Thank you.

TrueNAS : 12.0-U2.1
RAM : 8 GB

VirtualBox : 6.1.18 r142142
Network : Bridged Adapter
Host machine : Window 10 Home 2004


onionsjk

 

[HoneyBadger]

After reboot, iSCSI disk is not shown on Disk management tools. Well, sometime it comes online but only to one of the machines. Even after I got message "succssfully connected to trueNAS" , the disk remain unvisible.

To clarify; you are sharing a single iSCSI LUN (disk) between two virtual machines, and based on your description you are using in-guest iSCSI initiators.

The two VMs need to be "cluster aware" so to speak, otherwise one will not know that it is stepping on the other's toes. The disk will need to be added as a shared volume in a cluster, otherwise the policy of "online only from one host at a time" is correct and is preventing damage to the LUN.

 

[onionsjk]

Thank you.
Then should I put TrueNAS as a member of domain ?
As far as I know, cluster require domain.

 

[HoneyBadger]

No, the TrueNAS machine is only supplying iSCSI storage and is outside the scope of the cluster naming. Its only job is to be the shared disk.

You should build the cluster through the Windows Failover Cluster service, and ensure that the storage/disk component especially is validated prior to forming it.