Upgrading storage - best way?

Software-based VM-centric and flash-friendly VM storage + free version

Moderators: anton (staff), art (staff), Max (staff), Anatoly (staff)

User avatar
mooseracing
Posts: 91
Joined: Mon Oct 11, 2010 11:55 am

Thu Feb 28, 2013 4:08 pm

Bah didn't see that, we've had odd issues like this before on that Core box. It didn't save the network settings until I rebooted.

So now that they are correct, I step through and create with the following settings:
New Partner Host : 192.168.12.3
New Partner Management Port : 3261
New Partner Authentication : Use default credentials
New Partner Username : root
Second target name : iqn.2008-08.com.starwindsoftware:192.168.12.3-cluster20328secondnode
Mark as non-optimized path for ALUA : No
Partner Image : My Computer\F\clusterdisk1.img
Create new : No
Cache mode : wb
Cache size : 7168


Then get:
Add partner node failed!

Failed: operation cannot be completed.

I tried a few different settings and didn't get anywhere so I deleted the unsynched device (secondary node - primary node still has device and target), and tried to create a new one through this same set of options and I get the same error.

The only thing that stand out in the logs:
2/28 10:40:00.215 1690 Sw: *** MountTarget: Failed to log in to target(iqn.2008-08.com.starwindsoftware:192.168.12.3-cluster20328secondnode). Error message: Failed to log in to target. Status: Target not found(515)
.

If I created a target on the second server with that name then I can't step through the wizard as it says the target already exists. So the error doesn't seem really helpful.


edit again:
2/28 10:51:15.033 b14 HA: CHADevice::AddPartner: unable to process command. AddPartner_i() failed with error code 87.

This code mean anything?
User avatar
Anatoly (staff)
Staff
Posts: 1675
Joined: Tue Mar 01, 2011 8:28 am
Contact:

Fri Mar 01, 2013 3:20 pm

I saw something similar recently.
It looks like problem is related to the fact that you are using 4KB logical disk size (do not mix up with file system sector) instead of 512B. To get the issue solved the value should be changed to 512B. Here are some links that might be helpful:
http://www.starwindsoftware.com/forums/ ... t3078.html
http://msdn.microsoft.com/en-us/library ... 85%29.aspx
by the way we have this mentioned in our system requirements.

JFYI And here is the explanation of Advanced formats : http://en.wikipedia.org/wiki/Advanced_Format
Best regards,
Anatoly Vilchinsky
Global Engineering and Support Manager
www.starwind.com
av@starwind.com
User avatar
mooseracing
Posts: 91
Joined: Mon Oct 11, 2010 11:55 am

Fri Mar 01, 2013 8:31 pm

I guess I am slightly confused at which size - in the first thread you reference it says RAID array. On all of mine the stripe size is 64KB, drives are 512 B.

Using fsutil in the MS Article I get
C:\Windows\system32>fsutil fsinfo ntfsinfo f:
NTFS Volume Serial Number : 0xee8a63d18a6394bd
Version : 3.1
Number Sectors : 0x0000000045b7e7ff
Total Clusters : 0x0000000008b6fcff
Free Clusters : 0x0000000000de95cc
Total Reserved : 0x0000000000000000
Bytes Per Sector : 512
Bytes Per Physical Sector : <Not Supported>
Bytes Per Cluster : 4096
Bytes Per FileRecord Segment : 1024
Clusters Per FileRecord Segment : 0
Mft Valid Data Length : 0x0000000000040000
Mft Start Lcn : 0x00000000000c0000
Mft2 Start Lcn : 0x0000000000000002
Mft Zone Start : 0x00000000000c0040
Mft Zone End : 0x00000000000cc820
User avatar
Anatoly (staff)
Staff
Posts: 1675
Joined: Tue Mar 01, 2011 8:28 am
Contact:

Mon Mar 04, 2013 11:22 am

Hm... OK, can I ask you to sens the logs on the time of the issue from both nodes to support@starwindsoftware.com? We need service logs and console logs.
Use following adresses to find:
Service logs: C:\Program Files\StarWind Software\StarWind\logs
Console logs: C:\Users\%currentusername%\AppData\Roaming\StarWind\5\Console\Logs

Thank you

P.S. Please specify link to this topic in the subject of the email.
Best regards,
Anatoly Vilchinsky
Global Engineering and Support Manager
www.starwind.com
av@starwind.com
Post Reply