Below are a couple of issues I have come across while using the iSCSI target with Microsoft's iSCSI initiator and Windows 2003.
1) Windows occasionally gets confused with the disk signature of the iSCSI target and will mount the wrong volume by accident (even when the partition sizes are different).
2)The iSCSI target becomes mistakenly locked (i.e. device not ready) when Microsoft clustering is installed. This again may be due to Microsoft getting confused about the disk signature / target name.
3) Is there a way to include the volume name in the target definition instead of using "target0, target1...". This would help clarify what volume is being used.
Log in to post a comment.