Failover Cluster Pool Windows Server 2016

Ive uploaded pics of mny clustr entwork, the nodes, the disks shown in dis mgmt and the Storage Pool I created in Server mgr.
cluster-Network.jpg
Nodes.jpg
diskmgmt.jpg
ServerMgr-Storage-Poolk.jpg

I went into Failover Cluster Management-Clustername-Storage-Pools-  I right click POOL and chose New Storage Pool, named the pool and from the selected disks it shows my 23GB Virtual disk I created.  I selected that and it it showed as completed. but I do not see it in POOLS.  When I go to create it again and name it Pool1 it says that name is already in use?  When I click ADD Storage Pool it says "no storage pool suitable for cluster was found"

Is my question in the right place?

As far as I remember you should not select the storage during the fail-over cluster creation, only after. You get that message because it was created as part of the cluster

Whats the FoC going to be used for?  I ask because the cluster node names would appear to indicate that the FoC is for hosting a database engine?  (DB12, DB14)

The implementation (and answer) depends on what role the nodes and FoC will support... file services, SQL Server, Hyper-V, etc.

Dan

Option that I am referring to is "Use all available storage"

The role will be SQL Server.  We did not select the Pool/Storage during the failover cluster creation.

So with that how do I get a Pool created?

1. What version SQL Server?
2. Will SQL Server be clustered or not?
3. Will you be using Availability Groups?

Dan

The reason for the questions:

If you are building a clustered instance of SQL Server (Active/Passive cluster), the pools and disks need to be clustered resources.  You should create the pools and disks resources thru FoC Manager.  Then mark them as Cluster Shared Volumes.

If you are building a SQL Server cluster utilizing Availability Groups, there is no shared storage, SQL Server is not a clustered service.  The FoC is just to manage the AG listener (IP Address) resource.  The clustering of the databases happens in SQL Server and is managed by SQL Server.  A SQL AG is a fancy way of saying you are mirroring databases.

Dan

Not really... just clarify the question.

I stated the 2 scenarios in my last post.

Dan

Ok I have 2 physical servers and a SAN.  I wanted to use the SAN drives to create a Windows 2016 New Storage Pool.  When I go to do so it only sees 1 drive and none of the others.  I was told by  Cliff that it is bc Win 2016 doesnt accept RAID they need basically be JBOD and show as SAS and not RAID to Windows.

"Cliff Galiher
ID: 420621581dComment Utility:
Storage pools CANNOT be created on RAID arrays. Your second image, near the far right. Where disk type is "RAID."  That's your problem. The enclosure and HBA you use MUST both support presenting SAS disks directly to the OS. When that column says "SAS" you should good to go."

I guess my question now is why does it see one of the drives but it is RAID?  Why would Windows stop accepting RAID drives and only accept JBOD?  Doesn't that remove  the layer of redundancy and dismiss the entire point of having RAID.  with SAS disks using JBOD what happens when a disk fails?

Basically is there anyway to use the current Storage I have with Windows 2016 Failover Cluster Manager?

*HPE MSA 2040 SAS (contains 16 600GB drives)
* 2 physical HPE DL360 Gen 9 Servers
*Windows 2016 Standard X64

I looked at your screen shot from my phone and notice you only have a the default primordial pool. I may be think of something else but thought you needed to create a new pool outside of the default since this is when all unassigned disk go to first... May be way off thoug

https://blogs.technet.microsoft.com/yungchou/2013/04/11/windows-server-2012-storage-virtualization-explained/