Issues with HP Microserver RAID?

[autobahn97]

I can't seem to serve up an iSCSI disk to my VMware server from this small HP Proliant Microserver that I'm using from the BIOS/Software RAID1+0 set that Windows 2008 R2 can see as 3TB of usable storage. Windows seems to access it fine and I can read/write to regular file shares so I know the disk and drivers are working but StarWind (latest version just downloaded) doesn't seem to allow ESX to format the partition after mounting the iSCSI LUN using VMware software initiator. I am using basic image file and have also tried with advanced image file - both fail. It works fine if I put the starwind device file on the servers C drive where the OS is loaded (regular single disk - not 4 physical disk RAID built in BIOS) so it suggest something with the way the micro server implements RAID using AMD storage chipset. it feels like the VMware server doesn't have rights to access or do anything with the storage though settings are all teh same for the iSCSI lun that work on the single disk. Any suggestions that would help get starwind iSCSI working would be appreciated, otherwise I will try use Windows NFS server.

VMware error when attempting to format is "Call "HostDatastoreSystem.CreateVmfsDatastore" for object "datastoreSystem-9" on vCenter Server "vcenter2.autosys.local" failed."

[anton (staff)]

Would be nice if you'd manage to provide support with StarWind logs.

[autobahn97]

Thank you for responding and sorry I failed to upload the Starwind logs. I was able to get Windows NFS working from a share on this RAID set so it seems specific to Starwind. The most recent target is 'new1' but logs indicate several failed attempts starting with the first target I attempted to create. The ones which worked were all on a local single disk and not on the RAID set.

[Anatoly (staff)]

First thing that I`ve mentioned from your logs is string

License not found

so I guess you need to insert the license first and after we will gladly continue to assist you.

[autobahn97]

Perhaps at the top of the log however the free Starwind license was added and iSCSI targets can be successfully served up and used when the image file is located on the C drive which is a single drive so I'm assuming that confirms that the license is correctly installed. In the Starwind console 'Free Edition' is indicated in the License Type Field which I assume indicates successful installation of the license. It seems to only be an issue when the image file is located on the RAID set. I was wondering if NTFS perms may affect this howver whenI checked NTFS perm were the same on the image file which worked and the image file which was not working.

[Anatoly (staff)]

May I wonder what is stripe size used on your RAID and what is the block size on your NTFS?
Also, what disks are you using please?