StarWind Software

Hi,

I'm currently evaluating Starwind iSCSI with a ESXi cluster. Initial setup was easy, I chose to create a deduplicated disk device. After a system freeze of the starwind machine, the fileset is no longer mounted to the target. I've got a yellow exclamation mark on the target and a red one on the disk device. The disk device's status is "non active".

How can I force the device to mount? or reactivate it?

BTW: Windows Server 2008 R2, Starwind iSCSI 6.0.4837

Regards,
Mike

Could you please doublecheck that underlying virtual disk files are OK?

Hi Anatoly,

thanks for your reply. How to check the disk files? There is no function in the management interface to do such a task...

There are three container files files, .dddb, .spdata and .spmetadata. The files .spdata and .spmetadata are can be found in the starwind.cfg file. The file system hosting the container files is intact due to Windows.

Please help me to either extract the files from within the containers or to get them online in starwind. Please help, this is quite urgent!

*bump*

Please keep in mind that this is very urgent...please help!

Please help!!! Anyone???

I want to inform you that we have 3 business days response time on forums, if you`d like to have direct support contact and faster response I`d recommend you to contact sales regarding upgrading your license to commercial.

As about your issue: can I ask you to send your starwind logs to support@starwindsoftware.com (please provide the reference to this topic in the email body).

Thank you

My device config in "starwind.cfg": and: DDDiskEx1 does not work (State: "Non-Active", Lun: "-"), DDDiskEx2 does (State: "Active", Lun: "0").

UPDATE

It looks like the reason of the issue is the odd dot symbol in the names of the virtual disk files. The solution is to delete/destroy files and remole the dot in the names of each file and recreate the target after. I`ll try to illustrate it below. the dot that is need to be removed is underlined.

iSCSI_Host_File.img.spdata -> iSCSI_Host_Fileimg.spdata
iSCSI_Host_File.img.spmetadata -> iSCSI_Host_Fileimg.spmetadata
iSCSI_Host_File.img.dddb -> iSCSI_Host_Fileimg.dddb

The dot?!? Come ON...the dot was there at creation and it worked. So why should that stop working after a system crash?

But okay, I'll give it a try...

...done (console stopped, service stopped, cfg-file edited, service started, console started), and, as expected: No hit, device has still the red exclamation mark.

Have you edited the file name? Not the one in the config file, but the real one?

Guys, c'mon: I'm in IT for about 16 years by now.

YES OF COURS DID I CHANGE THE "#8/%$&)*(" FILENAME. Want a screenshot?

Also, can you confirm that you have re-created the target after changes as I have mentioned previously?

Yes, we would appreciate if you could provide us with the screenshots that illustrates that you have changed the names of VDs and recreated teh target using files with new names.

Thank you