StarWind Software

Hi,

I'm seeing a "funny" error on a new StarWind installation.
I have created an imagefile on 3 striped SSD files, that works with out any issues.
But I cannot get my image files to work on the regular HDDs.

OS: Windows Server 2012 R2 Core
HDDs is part of a storage pool (8 x 4TB disks)
In the storage pool I have tried the mirror / stripe and the parity configuration for the Virtual Disks.

I see some errors in the log, but google did not point me toward an solution
The log file is available in my dropbox: https://dl.dropboxusercontent.com/u/271 ... indLog.txt
If on of the "gurus" has an idea it would be much appreciated

Update:
If I map the disks as regular disks it works, it is just when they are part of a storage pool they do not work.
That puzzles me since the SSD disks work as a part of a storage pool.

Thank you in advance

Hi!

I think upgrading to the v8 and using 4096 bytes sector size during creating of SW image(see below) should so the job.

Hello,

I tried to simulate clean planned shutdown of one Starwind node in 2-node cluster. After node SW2 has restarted and starwind service started up again I see HA image file is in Non-active state. Replication is broken and interfaces are missing. See screenshot.

My config: Starwind v8 (build 7145) @ Windows server 2012 R2, single HA thick volume, connected from ESXi servers.

Please, how to re-connect non-active image and perform clean shutdown in a future? Thank you.

Pavel.

Hi

First of all, here are the instructions of what you should do in case when the StarWind went out of sync:
http://www.starwindsoftware.com/starwind-faq#q_11

As about the issue itself, may I ask you to provide me with next information:
· StarWind service logs from all problematic SAN boxes
· Windows Application and System logs (in *.csv format) from all problematic SAN boxes
· Detailed network diagram of SAN system
· Description of the actions that were performed before/at the time of the issue
· Approximate time frames when the issue happened
 
I`d appreciate if you`ll separate the logs from different servers into the different folders, upload them to some file hosting service and share the link with us.


Thank you

Hi Anatoly,

thanks for tip and guide for future, I'll send logs and schema on next test as you wrote. But a few more notes about this case:

• first of all: device reconnection was impossible in any way, I tried both methods from Q&A you recommended, but I always failed. I had to completely remove devices and targets
• I configured two node sync without cluster wizard, I used guide from thefinsker user, http://www.starwindsoftware.com/forums/ ... f=5&t=3762, reason is L1 and L2 requirement for HA device, it's only way (as far as I know) how to create HA device with L2 cache. I suspect this non-standard (?) of creation caused my problems on reboot.
• node #2 lost networking settings at all
• option "Synchronization" and "Mark as synchronized" was grayed on functional node

I'm going to perform same test again, but with standard cluster device for now.

Regards

Pavel.

Hi Pavel,
Did you have a chance to perform the second test?
What was the outcome?

Hello Max,

second test is still looking OK, no problems with nodes restart. I changed some configuration based on hints:

• I created cluster with wizard instead of manual creation, L1 cache size has been set manually by direct edit of .swdsk files
• I used thick disk instead of thin

So it seams OK now. Unfortunatelly I haven't L2 cache. Wizard doesn't allow specify it while cluster is created.

Pavel.

Hi! I`d dived deeper in the logs, but it looks like the one that you dropped initially is from v6, which is kind of confusing, Is there any chance you can drop more relevant one please?