Incorect LUN size

deYit · Wed Feb 08, 2012 4:20 pm

Hello,

We have installed StarWind 5.7.1807 on Windows Server 2003 R2 SP2 x32 with 2 LUN of 2TB, attached with SAS (IBM DS3512).
Windows disk manager detected disk with size correct, but StarWind not. First disk was detected correctly, second disk was detected incorrectly (~20TB!).
Can You help us with this?

Wed Feb 08, 2012 6:44 pm

How are you trying to map your disk? Thru the disk bridge or putting image file on top of it?

deYit · Thu Feb 09, 2012 5:54 pm

I tried both of these methods

Fri Feb 10, 2012 2:20 pm

Could you please try to do the same with the version 5.8?
You can download it here:
http://www.starwindsoftware.com/download-free-trial
Thank you

deYit · Mon Feb 13, 2012 3:59 pm

I uninstall previous version and install 5.8. Problem still exist, one of disks have incorrect size.

Mon Feb 13, 2012 9:27 pm

I assume it's GUI showing you incorrect size for underlying disk you want to create image on? Could you please provide a screenshot?

deYit wrote:I uninstall previous version and install 5.8. Problem still exist, one of disks have incorrect size.

deYit · Thu Mar 01, 2012 8:50 am

I have configured storage system on 3 volumes on 2TB. Now they are defined correctly. But there was other problem. If to assign to ESX one disk as physical in Starwind he is visible and it is formatted in ESX, but other two volumes in Windows vanish, though to ESX they have no relation. There can be problems hardware compatibility?

Thu Mar 01, 2012 1:32 pm

There are no dependencies on hardware. We're hardware agnostic.

It's absolutely not clear what you did and what you do and as you provide no feedback we ask for (logs & screenshots) it's very difficult to 1) understand what you're doing and 2) help you to solve your issues.

deYit wrote:I have configured storage system on 3 volumes on 2TB. Now they are defined correctly. But there was other problem. If to assign to ESX one disk as physical in Starwind he is visible and it is formatted in ESX, but other two volumes in Windows vanish, though to ESX they have no relation. There can be problems hardware compatibility?