StarWind Software

I've tried several versions of Starwind, including 2.6.1.
Using MS initiator 1.06 the clients can mount a drive, format it, but no space is shown on the drive and it is inaccessible.

Example:
Create an image file "quorum.img"
Add the image to Starwind
Login to the image from the client
Try to format the drive from the client, it does in fact format fine.
Get properties on the drive and it shows 0bytes for all categories.
The drive also does not ever show up in my computer.

It doesn't matter if the iscsi volume is basic or dynamic disk. Partition size doesn't seem to matter either. The mounted drive simply doesn't show any usable size.

I'm confused. This lab setup is the only time this has not worked for me. Have any of you seen this behavior before?

Thanks,
Brandon

Very strange but I think I've found the problem.

My initiator systems are Win2000 Advance Server.
The volumes work fine, show size, and are accessible from the console. They do NOT work from a terminal session.

Very odd behavior but everything works fine from the console.

Brandon,

Brandon,

It's a very starange behaviour.
It looks like READ_CAPACITY SCSIOP returns wrong data to the initiator.

Is the ImageFile file's size OK?
Maybe there is no free space on the base disk volume, so the image file is of zero size?
Have you tried to mount the image from other initiator machine, or from the same host where StarWind is?

Please tell us more details about the configuration, what are the machines, OSes?

Have you tried the same things with a RamDrive target? Does it work OK in the configuration?

Anonymous wrote:Very strange but I think I've found the problem.

My initiator systems are Win2000 Advance Server.
The volumes work fine, show size, and are accessible from the console. They do NOT work from a terminal session.

Very odd behavior but everything works fine from the console.

Brandon,

Brandon,

Thank you for the details.

So maybe it's some issue of the MS initiator software running on a terminal.

Have you tried our StarPort iSCSI initiator instead of the MS one?
Have it the same problem?

I have that same problem. Show up fine in diskmanager, but through terminal services, can not see the drive letter or access the drive. Works fine directly on the console.

I am using the starport initiator 2.4.2

ehinkle wrote:I have that same problem. Show up fine in diskmanager, but through terminal services, can not see the drive letter or access the drive. Works fine directly on the console.

I am using the starport initiator 2.4.2

Hi,

Thank you for the information.

So it's a "known issue" for now that the MS iSCSI initiator and StarPort work only from the console.
We'll try to solve the issue or to find a work around.

BTW The recent StarPort version is 2.6.1.