Running Windows Server 2012 R2 Datacenter with Hyper V role installed. I have created a RAID 5 with six 2TB hard drives for total of 8.95TB usable. I am using Windows Storage Spaces to configure my storage infrastructure. I created a storage pool that is 8.95TB and then created a virtual disk with size of 4TB and assigned it a drive letter E. I configured this on two physical servers with identical hardware.
When I try to create a Windows failover cluster and begin the validation process my virtual disk is detached and validation fails.
Cannot get past this step and not sure if I am missing a step or doing something wrong.
Would appreciate some ideas on how to resolve this issue.
VirtualizationWindows Server 2012Storage
Last Comment
gustavomor
8/22/2022 - Mon
Cliff Galiher
1) Don't use RAID and storage spaces together. Pick one or the other.
2) a hyper-V cluster requires shared storage. You can't create/validate a cluster if you only have servers with locally attached disks, even if they are configured the same,
gustavomor
ASKER
I am using Starwind VSAN software to create the shared storage.
How would I expose the JBOD to Windows Server 2012?
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Have you presented the Starwind vSAN iSCSI IP Address to both nodes ?
Experts Exchange is like having an extremely knowledgeable team sitting and waiting for your call. Couldn't do my job half as well as I do without it!
James Murphy
gustavomor
ASKER
Yes
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
then you should be able to re-scan, and see the iSCSI disks?
gustavomor
ASKER
I do see the iscsi disks, but the drive where I save the Starwind Images and LSFS files disappears when I do cluster validation on Windows 2012 box.
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
2) a hyper-V cluster requires shared storage. You can't create/validate a cluster if you only have servers with locally attached disks, even if they are configured the same,