Connecting State

Initiator (iSCSI, FCoE, AoE, iSER and NVMe over Fabrics), iSCSI accelerator and RAM disk

Moderators: anton (staff), art (staff), Max (staff), Anatoly (staff)

Post Reply
hwong
Posts: 1
Joined: Wed Oct 27, 2010 10:18 pm

Wed Oct 27, 2010 10:22 pm

We are running Win2003 R2 Standard x64 edition. We are having a problem with our StarPort Pro edition version 4.2 build 0x20090702. This was working until recently. The AoE device was showing in a "connecting" state. I could not get it to connect. This had happen in the past, and I would delete the device and add it back in. But this time, after I deleted the device, StarPort can''t find the AoE device (Coraid). I have another server that is using the same array and same software and has no problems. I tried to upgrade to the current version which I was told is the AoE Initiator version 5.5 build 0x20100903. It still won''t see the device. I''ve checked all the networking, and it all looks to be ok.
User avatar
Max (staff)
Staff
Posts: 533
Joined: Tue Apr 20, 2010 9:03 am

Fri Oct 29, 2010 9:50 am

Do the following:

1. Uninstall the Aoe Initiator from the machine
2. Remove the StarPort and StarWind AoE folders from the machine
3. Remove the starport.sys, staraoe.sys files from the \windows\system32\drivers\ folder
4. Install the AoE initiator from a scratch.

It appears that StarPort driver has caused this error and locked up the device.
Max Kolomyeytsev
StarWind Software
Post Reply