Bdtyktl

Whenever I reboot, the iSCSI drives are not connected, and I see "reconnecting" in the Microsoft iSCSI initiator, if I try to disconnect I get an error, but after restarting the iSCSI service (at this point I've written a short powershell script and put it on my desktop), the iSCSI drives reconnect.

Someone recommended removing all the portals and adding them without using "quick connect" this did not seem to help.

The iSCSI server is a FreeNAS device and it has 1 portal with 1 target and 2 extents. It used to have 2 targets with one extent each, but I combined the 2 targets into one.

I've thought about just creating a scheduled task to restart the iSCSI service when I login, but I feel like I will probably still have to recreate the Steam Library on the drive every time.

The following bits of the story are much less relevant, but may hold clues:

I have a Windows 10 gaming PC with zero hard drives and several SATA SSDs (I can break it down if this matters, but the bottom line is I'm out of SATA ports on my motherboard)

Instead of installing hard drives for "slow storage", or using SMB (which is quite slow), I have 2 iSCSI drives (same target/portal, 2 different extents) coming from my NAS.

For awhile this "just worked", I got a 1TB m.2 SATA SSD and an adapter on Black Friday 2018 and that filled up my last SATA port.

The problems started more recently when I got a built-in USB3 hub that goes into the 5.25in bay... after installing it, both my new 1TB SSD and my iSCSI drives suddenly stopped working. I worked through this. The PCIe to M.2 adapter had come loose and the screw holding it in place was not working, so I replaced the screw, and ran chkdsk, etc. and all was well. But... somehow this messed up iSCSI? it's not clear, but it happened at the same time. Unless the game "The Talos Principal" (installed on the 1TB SSD), could have messed it up. (I had a fun crash when the SSD came loose, but again, not super relevant to the iSCSI problems)

I changed the iSCSI settings on my NAS to have 1 portal + 1 target with 2 extents instead of 1 portal with 2 targets (one extent on each target). This confused the hell out of Windows, I mostly did it because it seemed cleaner, but I was able to turn off the iSCSI service, uninstall the driver, nuke the iSCSI settings from the registry, and re-add everything, and everything seemed good.