HyperV VSA instalation create volume

johnthomson · Fri Sep 08, 2017 12:11 pm

Hi,

Brand new to Starwind here and am trying out the HyperV VSA, I have been following along the guide V1.0 Jan 2017 and am stuck a t step 23 creating a volume, I have tried this on 2 nodes with same result, after selecting "create volume" an error message is returned. Volume Mount Failed. Linux system command error. Its probably a school boy error on my part.... any assistance gratefully receivd

Cheers
John

johnthomson · Fri Sep 08, 2017 12:30 pm

Some more screenshots

Mon Sep 11, 2017 5:47 pm

Hello johnthomson,
Thank you for interest in the StarWind solution.
We will try to reproduce this issue on our site and once we will have the results we will update this thread.
Have a great day!

Jimmy9008 · Thu Sep 28, 2017 8:36 am

I also have this issue. Did we get anywhere on this?
I'm using Hyper-V on Windows 10 Enterprise. I shall also try this on Server 2016 with Hyper-V role too and post back.
But, Windows 10 has the same error as the original post.

Jimmy9008 · Thu Sep 28, 2017 1:01 pm

Hey folks,

I've also tried this with Windows Server 2016 running the Hyper-V role - same issue.

'Volume Mount failed - Linux System Command Error. System command (mount) exited with non-zero status (1).

Any ideas?

I do not have a Hyper-V only server at this time to try on that, but that should not be an issue right?

Jimmy9008 · Thu Sep 28, 2017 1:02 pm

The VSA storage screen does show File System - Unknown.

Jimmy9008 · Thu Sep 28, 2017 1:07 pm

Figured it out. Using VHDX with Fixed Size fails.
Using VHD with Fixed Size is success.

Following this documentation says to use VHDX, however, doesn't work for me.
https://www.starwindsoftware.com/techni ... yper-V.pdf

Should VHDX work here? Or is it me?

Jimmy9008 · Thu Sep 28, 2017 1:42 pm

So, the host name for this shows in DHCP as StarwindVSA and has its IP address.
I have created a second on the same LAN, and in DHCP I can see a second SatwindVSA (Name), but different IP address. Shouldn't the VSA have a different name?

Tue Oct 03, 2017 1:35 pm

Hello guys! Yes, the .vhd drive created instead of .vhdx, solves the issue. You can login with IP, instead of VM name in order to prevent any conflicts. You can assign a static IP address under Configuration tab --> VSA Networking Settings.