StarWind virtual disks atop Microsoft Storage Pool Virtual Disk - fails?
Posted: Sat Jan 23, 2016 7:20 pm
Hi,
I have a StarWind v8 build 8730 system here. The system has 2 * 250Gb SSD's in I'd like to pool with Windows Storage Pools and create a 'Simple' virtual disk atop of those (Simple = RAID0) - and then create one large StarWind virtual disk atop of that - but it fails.
Install WS2012 R2 - install StarWind. Create a Windows Storage pool out of the two 250Gb SSD's - and create a Virtual Disk atop of that in 'Simple' (RAID0) mode - and finally (phew) create a Windows Volume on that virtual disk, for the entire ~460Gb exposed. This results in D:\ - which is then formatted as NTFS.
Fine so far - but in StarWind if I create a device on D:\ - I get the following error log in the server logs:
1/23 17:34:24.736 50c IMG: SscPort_Create: Opening device 'imagefile1', image file 'My Computer\D\SSD-Storage\SSD-Storage.img', buffering=0, async=1, readonly=0.
1/23 17:34:24.736 50c IMG: SscPort_Create: Device queue flags (0) are complemented with plugin queue flags (1).
1/23 17:34:24.736 50c Ssc: *** SscScsi_GetVolumeProperties: \\.\D:: StorageDeviceSeekPenaltyProperty failed (error 1).
1/23 17:34:24.736 50c IMG: *** ImageFile_BuildInquiry: D:: Incompatible logical volume sector size (4096 > 512)!
The file created isn't read only (i.e. Windows can quite happily copy it, rename it etc.) - I'm guessing the line "4096 >512!" is the culprit. I'd guess Windows Storage Pool has created a virtual disk with a logical sector size of 4k which StarWind doesn't like?
Looks like I can create it if I opt for 4096 byte sector size in StarWind - but the rub is our client (Xen) can't use 4k block size
Obviously de-pooling the disks - and creating them as individual 250Gb volumes 'works' - but I need to create one volume spanning both disks...
Any magic fixes I can use?
-Kp
I have a StarWind v8 build 8730 system here. The system has 2 * 250Gb SSD's in I'd like to pool with Windows Storage Pools and create a 'Simple' virtual disk atop of those (Simple = RAID0) - and then create one large StarWind virtual disk atop of that - but it fails.
Install WS2012 R2 - install StarWind. Create a Windows Storage pool out of the two 250Gb SSD's - and create a Virtual Disk atop of that in 'Simple' (RAID0) mode - and finally (phew) create a Windows Volume on that virtual disk, for the entire ~460Gb exposed. This results in D:\ - which is then formatted as NTFS.
Fine so far - but in StarWind if I create a device on D:\ - I get the following error log in the server logs:
1/23 17:34:24.736 50c IMG: SscPort_Create: Opening device 'imagefile1', image file 'My Computer\D\SSD-Storage\SSD-Storage.img', buffering=0, async=1, readonly=0.
1/23 17:34:24.736 50c IMG: SscPort_Create: Device queue flags (0) are complemented with plugin queue flags (1).
1/23 17:34:24.736 50c Ssc: *** SscScsi_GetVolumeProperties: \\.\D:: StorageDeviceSeekPenaltyProperty failed (error 1).
1/23 17:34:24.736 50c IMG: *** ImageFile_BuildInquiry: D:: Incompatible logical volume sector size (4096 > 512)!
The file created isn't read only (i.e. Windows can quite happily copy it, rename it etc.) - I'm guessing the line "4096 >512!" is the culprit. I'd guess Windows Storage Pool has created a virtual disk with a logical sector size of 4k which StarWind doesn't like?
Looks like I can create it if I opt for 4096 byte sector size in StarWind - but the rub is our client (Xen) can't use 4k block size

Obviously de-pooling the disks - and creating them as individual 250Gb volumes 'works' - but I need to create one volume spanning both disks...
Any magic fixes I can use?
-Kp