Uhh, yes! This should actually be fixed with the "weight" volume that should be created automatically. This keeps the iSCSI target alive on the TrueNAS side. TrueNAS will turn off it's portal advertising when there's no volume being shared. So the plug is supposed to create a "weight" volume that is always alive to prevent that from happening. Let me know if you see that volume, if not, I will look into why it's not being created.
Yes! That's actually in the works at the moment. I'm updating the storage configuration tool to go step-by-step to pick the pool, create a dataset that's optimal for your setup (or put in manual settings), and then enable iSCSI/NVMe blah blah blah. That way it's basically as easy as configuring pools and then creating an API key in TrueNAS, then from that point on there isn't much of a reason to actually log into TrueNAS any more unless you're needing to do some really manual work.
Hmm, are you saying there's orphaned iSCSI targets that are trying to be logged into?
This should be the only thing you need to do in TrueNAS after setting up the dataset you want:
View attachment 92756
Once the target is created with the Portal Group ID and Initiator ID configured, the plugin should take care of the rest. If not, let me know.
And Alpha branch has the latest and greatest, the beta one will have a more stable updates to it. For now I would use the alpha branch while troubleshooting.
That's interesting you are getting some somewhat okay performance on the writes. Do you have sync=off on your dataset?