It's not a "defect" it's by design. If you create one target and one LUN - it will be always zero. If you add more LUNs to the same target - their numbers will increment as you go. ON Starwind, while creating a new target, the LUN always is 0 wherever the storage is and how many and wheth...

please tell me where the log file is.

much thank in advance!

Try rescanning it again and make sure you have StarWind log under hands. Zip it and send with your comments to support@starwindsoftware.com so we could tell for sure what's broken. Sorry, I can't find Starwind log file on target machine. Could you please tell me where it is and its name? thanks, ge...

On vSphere 4.0 has iSCSI disk by Starwind. They can work togather well before. But, shut down the target machine accasionally, then shut down WMare host, now, can't rescan iSCSI on the host. vmkping the target well. How can I fix it? after remove and readd targets on both dynamic and static discover...

Hi, After the problem, I meet new one. After added the iSCSI disk successfully, and turned on some VMs, I wrote down Thank to you here. But, when two MSCS nodes rooting or later (I am not sure the really time), can enter both of them. Checked the storage, the iSCSC disk lost. Did the same way to add...

you are great!

Thank you very much!

George

First, when after boot iSCSI service which is on Win7, then vSphere host, the iSCSI disk (VMFS form) often can’t appear on Storage. After adding it, it’s Ok. But, yesterday, deleted a NTFS partition on the physical disk where the iSCSI image file is on another NTFS partition on, which totally had 3 ...

Hi Max, I got the source of the problem. Microsoft said: Cluster setup may not work when you add nodes View products that this article applies to. System Tip This article applies to a different version of Windows than the one you are using. Content in this article may not be relevant to you.Visit th...

Max (staff) wrote:This is kind of a problem which usually misteriously disappears after Windows reinstall, but this is the last option.
I will dig the technet forums for more info on this case, please stay tuned!

I rebooted them 2-3 time.
Thank you for your help!

Max (staff) wrote:Did you doublecheck that the drive is connected to both servers?

Yes, I can write a file down on the disk from both nodes.

Now, I fixed the proble. But, after added second node, got another error message: The quorum disk could not be located by the cluster service.please look the picture 1. I checked the Starwind, the disk created on Clustered. Please looked the Picture 2. and Computer Managerment on Win2003 on both nod...

Start with updating to 5.5 as an initial step. With HA heartbeat Max asked about StarWind HA heartbeat, not MS cluster heartbeat. As h/b was represented with 5.5 and up you can ignore this question. Thanks for your reply. Do you mean 5.5 no this problem? and Starwind has its conception called Starw...

I am sorry, maybe I've got something wrong but in the header you've mentioned a Win7 and 2 2003 boxes. What does HA heartbeat do here? or is this a Node-node cluster heartbeat meant? Yes, Starwind 5.4.0.1579 on Win 7 64bit, 2 nodes on Win2003 SP2 64bit on vSphere 4.0 host. heartbeat between 2 nodes...

Sorry, I also tried public IP address 10.1.1.10 here, got same error message.
thanks!