Ok, so I managed to get iSCSI setup and running using the most basic of configurations I could find to try and give my windows10 PC additional temporary storage space to do some shuffling around of files and testing.
On the server I managed to setup the iscsi service and get it running, added a zvol under my back end storage array (seperate external jbod array from the server) and create a 6TB drive that the iscsi initiator on the pc could see as a drive automatically, then could be added and formatted etc and worked a treat as a drive over my primary network.
But, I had an issue with the main storage in the server (primary pool made up of 2 groups of 4 disks each, with 1 raid drive in each group of 4).
The main pool was marked as degraded so I rsynched everything to the external and then restarted (whilst hunting around for a spare 3TB SAS drive…)
The system restarted, cleared the errors (I’ll still swap the drive out next week though) and it resilvered the primary storage no probs.
Swapping back to the Win10 PC though, i couldn’t see the O:\ (the iscsi volume) anymore. it had vanished also from the device manager so I was unclear as to what had happened.
In the Win logs I’m getting basically “can’t find the server or volumes on it” type errors and the iscsi service on the Truenas scale server keeps stopping. Even when it’s been running for a few minutes, there is nothing being advertised to the network.
I’ve added specifically the pc’s target id into the iscsi config on the server as a test but no joy.
Last night it just “Appeared as expected” on the PC and I could set it up with no problems. Worked super fast as well, no issues there.
Today, nothing.
I even tried reconfiguring iscsi to use the dedicated direct fixed ip addresses of it’s separated network segment the PC uses for SAMBA (2.5Gbps), but nothing appears as a target to connect to and the PC just reports “Connection failed”.
What should I be checking?
Ta,
STu.