Problem adding drives to Windows 2008 R2 Cluster

[hardware]

I have two windows 2008 R2 nodes. Starwind is running on a HP dl320s using a smart array P400. From each node I have made connections to Starwinds using the Starwind iSCSI initiator. The drives are online on one of the server and offline on the other. When I run cluster validation I get the following errors "Disk bus type does not support clustering. Disk partition style is MBR. Disk partition type is BASIC." and "No disks were found on which to perform cluster validation tests".
I have tried using the microsoft initiator. I can connect to the target using the Microsoft initiator but am unable to see the drives in disk manager.

[hardware]

sample from starport.log
4/24 14:16:27.454 CStarPortAPI::GetDevices: Calling STARPORT_IOCTL_TARGET_LIST
4/24 14:16:27.454 CStarPortAPI::GetDevices: Output buffer:
4/24 14:16:27.454 CStarPortAPI::GetDevices: NumberOfTargets = 1
4/24 14:16:27.454 CStarPortAPI::GetDevices: TargetID[0] = 13
4/24 14:16:27.454 CStarPortAPI::GetDevices: Calling STARPORT_IOCTL_TARGET_INFO
4/24 14:16:27.454 CStarPortAPI::GetDevices: TargetId = 13
4/24 14:16:27.454 CStarPortAPI::GetDevices: Output buffer:
4/24 14:16:27.454 CStarPortAPI::GetDevices: TargetId = 13
4/24 14:16:27.454 CStarPortAPI::GetDevices: ServerAddress = #iscsi:x.x.x.x:3999
4/24 14:16:27.454 CStarPortAPI::GetDevices: TargetDescriptionLength = 115
4/24 14:16:27.454 CStarPortAPI::GetDevices: TargetFlags = 1
4/24 14:16:27.454 CStarPortAPI::GetDevices: TargetDescription[0] = InitiatorName=iqn.2003-06.com.starwindsoftware.starport:server2
4/24 14:16:27.454 CStarPortAPI::GetDevices: TargetDescription[1] = TargetName=iqn.2008-08.com.star:backup04
4/24 14:16:27.454 CStarPortAPI::GetDevices: NumberOfUnits = 1
4/24 14:16:27.454 CStarPortAPI::GetDevices: LunInfo[0] = 0
4/24 14:16:27.454 CStarPortAPI::CheckConnectionStatus: TargetId = 13
4/24 14:16:27.454 CStarPortAPI::CheckConnectionStatus: Target 13 status = 2
4/24 14:16:27.813 CMainFrame::PoolingServiceEvents: Event checking failed, status == 2
4/24 14:16:28.219 CMainFrame::PoolingServiceEvents: Event checking failed, status == 2
4/24 14:16:28.624 CMainFrame::PoolingServiceEvents: Event checking failed, status == 2

[anton (staff)]

StarWind iSCSI initiator should not be used for clustering. Use Microsoft iSCSI initiator in legacy mode.

[hardware]

Will legacy mode cause any problems if I am using dell equallogic mpio software?

[anton (staff)]

No. Custom MPIO stacks (DataCore, EQL and LH) work fine.

Will legacy mode cause any problems if I am using dell equallogic mpio software?

[hardware]

Not sure how to set Microsoft iSCSI initiator in legacy mode. Can you point me to any white papers?

[anton (staff)]

Configure MPIO with external layer coming from your target vendor (if available) instead of MS MPIO stack. So if you use Dell EQL hardware use Dell EQL MPIO stack + MS iSCSI initiator on a client. With StarWind used as an iSCSI target DON'T run anything except bare MS iSCSI MPIO stack (sorry I've misread your post in a thread - DON'T run EQL MPIO with StarWind).

Here's a doc how to configure MPIO on a MS iSCSI initiator:

http://technet.microsoft.com/en-us/libr ... 25907.aspx

http://technet.microsoft.com/en-us/libr ... s.10).aspx

Not sure how to set Microsoft iSCSI initiator in legacy mode. Can you point me to any white papers?

[hardware]

I removed the dell eq HIT software. I am now running only microsoft iscsi initiator with no add-ons. I am able to log on to the starwind target using the iscsi initiator but am unable to see any of the starwind drives in disk management.

[anton (staff)]

Did you actually create any before logging in?

I removed the dell eq HIT software. I am now running only microsoft iscsi initiator with no add-ons. I am able to log on to the starwind target using the iscsi initiator but am unable to see any of the starwind drives in disk management.

[hardware]

Yes, I am able to see the drives with the starwind initiator but I can't add them into the cluster.

[Max (staff)]

Forget StarWind iSCSI initiator for this purpose! Can you "see" drives in a MS iSCSI initator log on sessions?

Yes, I am able to see the drives with the starwind initiator but I can't add them into the cluster.

[hardware]

Yes, I can see the drives and they show the status of connected under the targets tab.

[Max (staff)]

OK, good, getting closer When you're trying to add a LUN to a cluster what you see? Can you post a "show stopper" screenshot and also supply StarWind log corresponding to this failed attempt? Thank you!

Yes, I can see the drives and they show the status of connected under the targets tab.

[hardware]

I only see the drives in the iscsi initiator as being connected. Disk management and diskpart don't show the drives as being connected.

[Anatoly (staff)]

OK, so can you provide the screenshots that my colleague requested please?
Also, what version, edition build and device type of StarWind are you using?