Assistance with iSCSI target losing its LUN
Posted: 09 Feb 2022, 23:54
I'm experiencing something very similar to what was in this thread.
viewtopic.php?f=25&t=2043
I've emailed [email protected] twice now and haven't received a response at all. Not even a confirmation that my email was received.
I have a TerraMaster NAS used in a VMware environment via iSCSI.
Today one of the iSCSI targets seems to have lost its LUN. See below with the first IQN, and no LUN assigned.
This target was associated with the RAID 1 volume in Storage 1.
I am unable to get the iSCSI target associated with Storage #1.
I have attempted making a new iSCSI target and pointing it to Storage #1, but that isn't available. Only Storage #2 is available.
One of the questions asked in the thread I linked above was what was done previously on the NAS before this happened. In my case, I had two 500GB drives in bays 3 and 4 set up as a RAID 1 assigned to Storage #2. These were not in use so I deleted Storage #2, removed the drives and added in two replacement 2TB drives pulled from an HPe server. I created another RAID 1 with drives 3 and 4 and then created a iSCSI target of that volume and presented it to my VMware ESXi hosts. That is working fine.
I was also working with installing a new UPS for this NAS and was powering down and turning on the system a few times after this when connected to the new UPS. On one of those power cycles is when Storage #1 LUN disappeared from the ISCSI target.
You are welcome to do a remote connection if you want.
viewtopic.php?f=25&t=2043
I've emailed [email protected] twice now and haven't received a response at all. Not even a confirmation that my email was received.
I have a TerraMaster NAS used in a VMware environment via iSCSI.
Today one of the iSCSI targets seems to have lost its LUN. See below with the first IQN, and no LUN assigned.
This target was associated with the RAID 1 volume in Storage 1.
I am unable to get the iSCSI target associated with Storage #1.
I have attempted making a new iSCSI target and pointing it to Storage #1, but that isn't available. Only Storage #2 is available.
One of the questions asked in the thread I linked above was what was done previously on the NAS before this happened. In my case, I had two 500GB drives in bays 3 and 4 set up as a RAID 1 assigned to Storage #2. These were not in use so I deleted Storage #2, removed the drives and added in two replacement 2TB drives pulled from an HPe server. I created another RAID 1 with drives 3 and 4 and then created a iSCSI target of that volume and presented it to my VMware ESXi hosts. That is working fine.
I was also working with installing a new UPS for this NAS and was powering down and turning on the system a few times after this when connected to the new UPS. On one of those power cycles is when Storage #1 LUN disappeared from the ISCSI target.
You are welcome to do a remote connection if you want.