TerraMaster Forum

I recently setup a F4-212(running TOS 5.1) server with 4 4TB HDs. I created an iscsi LUN and Target for my VMWare farm. It took some tinkering to get it running.
First I wasn't able to get both my esxi servers to connect to the target at the same time. I ended up deleting the target/lun recreating it with CHAP enabled and that did the trick.
Once I got it running, I was able to transfer my VMs from my old server to the new Terramaster. I verified VMs could switch from esxi to esxi without issue using the new storage.
However, I logged onto the config page for the F4-212 and it didn't show the iscsi config. THe service was still installed, but thewre was no config. I logged back onto the esxi servers and they still had a valid target and was able to add/remove vms so the F4 still "knew" it was hosting my iscsi store.
I rebooted my F4 today and when it came back up, the iscsi config was gone. The esxi servers no longer see it as a valid target and all my VMs are gone.
I tried to recreate the target/lun in TOS, but it only errors out on me.

I am hoping the old iscsi config and my lun is still on the system, but I have no idea how to find it now.

You can try restarting the application and TOS, and then you can use the following command to view the information: You can make an appointment for a remote technical support through the online customer service on our official website. Our technical support team will check the cause of the abnormality for you.

If I am reading this right, it looks like the LUN is there, but the config files are not there.

[basherw@NASY1 ~]# ll /Volume1/@iSCSIStoragePool/
total 233G
drwxr-xr-x 2 basherw basherw 4.0K Nov 12 08:23 .
drwxr-xr-x 12 basherw basherw 4.0K Nov 15 2025 ..
-rw-r--r-- 1 basherw basherw 2.9T Nov 15 09:25 iscsi-spare-vdisk-thin1762907010
[basherw@NASY1 ~]# ll /Volume1/\@apps/iSCSIManager/configs/iSCSI.conf
/bin/ls: cannot access '/Volume1/@apps/iSCSIManager/configs/iSCSI.conf': No such file or directory

It seems that an engineer is needed to check and fix this issue for you. You can choose a suitable time to make an appointment with us for remote assistance.

After tinkering around by myself I got it working again.
The iSCSI.conf file in /etc/iscsi was corrupted. (Basically blank and incorrectly formatted).
Using my other F4-212 I created a new iSCSI config there, then copied the new iSCSI.conf file to my local system.
The old iSCSI lun was in /Volume1/@iSCSIStoragePool/ as stated above.
I simply altered the "filename" from the 2nd F4-212 to reflect the location/filename from the original F4-212. Then uploaded that.
One reboot later and tada, Bob's your uncle.
Little clean up in VMWare to recongize the LUN and VMs was all that's left.
I will be using a different storage solution for my iSCSI needs in the future.