Assistance with iSCSI target losing its LUN

[gtproject]

I just realized that the file linked to download is referred to as "4.1.18". However the link has "4.1.03" in it.

The link for "4.1.18".

http://dl.terra-master.com/cn/TOS_S2.0_ ... 03_294.bz2

I tried updating the link to have 4.1.18 instead of 4.1.03 however, that doesn't work either.

[TMnorah]

Thank you for your report! we will correct the mistake soon.
For your information, 4.1.03 can be directly upgraded to 4.1.27, just go ahead and follow the instruction to update your TOS gradually.

[gtproject]

As an update, I updated:

4.1.27
no changes
4.1.30
no changes
4.2.09
lost access to the iSCSI lun that was connected. reinstalled iSCSI app on TerraMaster NAS and got connectivity to the LUN back on one of my ESXi hosts.
4.2.28
lost access to the iSCSI lun again. installed the iSCSI pro beta app on the TerraMaster NAS. was not able to get connectivity back. tried enabling multiple connections, but no change. Status says Good now instead of Connected on the iSCSI target list.

However, during the process the missing LUN now somewhat in the storage pool, by having a value. Its the wrong value and appears to think the pool is empty.

2022-02-13 10_42_17-Desktop - TOS.png

[TMSupport]

After creating the iSCSI Target and iSCSI LUN, you need to mount the iSCSI LUN through the iSCSI initiator on the server. For example: Go to Control Panel > Storage Management > Virtual Disk to create a virtual disk. The memory occupied by the iSCSI LUN needs to check the volume where the LUN is located.