iSCSi won't reconnect

---

mdgm wrote:

What about if you instead use a thick LUN with bitrot protection and sync writes both disabled?

 

What is the capacity of your data volume and how full is this?

---

I'll have to wait for the weekend to try it with a completely different LUN configuration.  The overall data volume is something like 6 or 8 TB, but it's only around 50% full.  (So, I do have the room to make this LUN thick.)  

Mdgm, are these suggestions along the lines of "likely solutions", or more like "trying different things to see what might work"?  

The reason I'm asking is that I'm suspecting, based on other threads on here of a similar nature, that the problem I'm seeing is related to the iSCSI software on the NAS not releasing the connection when the Windows Server reboots.  If that's the case, then the target might be refusing the connection after a reboot as it thinks that the initiator is ALREADY connected.  Is there some way, from SSH, to see what's going on from the NAS point of view?  (ie: for example, something that might show "current list of connections" on the target?)  

Ideally, even if I work around the problem by using a thick LUN (assuming that works around the problem), I'd still like to understand WHY I'm having the problem to begin with so that, perhaps, netgear can fix it (or I can report the issue to Microsoft if it's with their initiator.)

Gary