New Windows server VM can't map drive via Disk Manager to the FreeNAS iSCI target

[Matt Seppeler]

I migrated a Windows 2012 Server VM to new hardware. I successfully initiated via the ISCI Connector to the FreeNAS and the Disk Manager adds the Disk. It sees it as a healthy partition. I select the partition to be Online. However, it does not provide a drive mappings. I get the same results via a Window 2008 server as well as Windows 10 Workstation. From the old server VM, this SCSI LUN was already formatted and files added. I no longer have access to the old server. The other servers are in the same domain as the old server. Is there a way that I can still access the files and folders from this ISCI Target that is being hosted on the FreeNAS device?

 

[darkwarrior]

Hi there,

so when you are initializing the disks everything is OK ? The partition (with the right size appears ) ?
Did you try to create a drive mapping ? (Right-click on the partition -> Change dirve letters and paths)

 

[Matt Seppeler]

Yep, everything is ok with it initializing and the right size does appear. Where I have the problem is that it does not let me create the drive mapping (Right-click on the partition -> Change dirve letters and paths). One thing to add is that I was able to get access back to the original server that had the mapping. The mapping and initialization was removed. I was able to reinitialize but like with the other servers, I can perform no perform the drive mapping.

 

[darkwarrior]

Now that's weird ...
You're not getting any error message of any kind, when trying to perform the drive letter assignment ?
Did you look at the 'System' eventlogs ?

Edit: Typos

 

[Matt Seppeler]

I get two event log messages:

Error: Connection to the target was lost. The initiator will attempt to retry the connection.

Information: A connection to the target was lost, but Initiator successfully reconnected to the target. Dump data contains the target name.

 

[darkwarrior]

I get two event log messages:

Error: Connection to the target was lost. The initiator will attempt to retry the connection.

Information: A connection to the target was lost, but Initiator successfully reconnected to the target. Dump data contains the target name.

And on the FreeNAS side ? Do you see errors in /var/logs/messages ?

 

[Matt Seppeler]

Do you view the log files from the GUI. Can't find them.

 

[darkwarrior]

A good way to display them is to connect via SSH and run the command below:
tail -n 50 /var/log/messages

 

[Matt Seppeler]

Having difficulty getting SSH to work so I ran it under the Shell tool. You can see that I clear the initiator for the 10.1.10.8 and 10.1.10.9 windows servers and logged in with the initiator from the 10.1.10.6 server.

 

[Jonathan Hughes]

Curious if you ever had this resolved. I am facing the same issue.