none
No clustered disks available

    Question

  • We just finished up putting together a windows 2012 cluster using a single shared volume.  I went today to build the SQL cluster and got an error stating that "No clustered disks available" when doing the install.  We have a single volume that shows as a CSVFS disk in the failover cluster manager but SQL server is unable to find the volume.  The other odd thing is the disk shows offline in disk management and will not allow me to place it online.  Any suggestions would be greatly appreciated.

    Thanks.

    Saturday, November 09, 2013 12:34 AM

Answers

  • >What is the best practice for this?  Should we create multiple volumes? 

    That varies by SAN and by your expectations for performance.  

    At a minimum you should store your SQL Server backups somewhere that is very unlikely to be affected by an problems that might affect the storage location where your databases are. 

    Beyond that having a single LUN for databases, logs and TempDb will work fine, but might not meet your performance expectations.  There's no guarantee that using seperate LUNS for TempDb or Logs will actually perform better, however.  That really depends on your SAN and its configuration.

    David


    David http://blogs.msdn.com/b/dbrowne/

    • Marked as answer by nickswoca Wednesday, November 13, 2013 2:41 PM
    Tuesday, November 12, 2013 11:56 PM

All replies

  • Hello,

    Please try to open the cluster validation wizard to test the underlying hardware and software configuration of the Cluster and review the validation report to find the cause of the issue.
    You can also check the event log for the Failover Cluster for more infromation.

    Reference:
    Cluster Validation Wizard
    View Events and Logs for a Failover Cluster

    Regards,
    Fanny Liu


    Fanny Liu
    TechNet Community Support

    Monday, November 11, 2013 9:34 AM
    Moderator
  • Hi,

    Please see: http://technet.microsoft.com/en-us/library/jj612868.aspx

    CSV does not support the Microsoft SQL Server clustered workload in SQL Server 2012 and earlier versions of SQL Server.


    Thanks, Andrew
    My blog...

    Monday, November 11, 2013 9:59 AM
  • Hello

    It won't support in SQL Server 2012 version.

    Please go through below link.

    http://www.learnmsexchange.com/windows-servers/windows-server-2012/633-cluster-shared-volumes-csv-v2-in-windows-2012

    ----------------

     Ramu A



    • Edited by RamuAnnamalai Monday, November 11, 2013 10:54 AM more information
    Monday, November 11, 2013 10:35 AM
  • Can you please provide me validation report .. and conform with nodes connected shared disks in iSCSI initiators. connected drive verify with Drive letter on both nodes.

    Thanks & Regard's

    ---------------------------

    Ramu A

    Monday, November 11, 2013 10:40 AM
  • I have read that in other articles but I have seen other posts where users have created a shared volume for SQL.  What would be the alternative for a hyper-v cluster with a iSCSi connection to the SAN.
    Tuesday, November 12, 2013 2:02 PM

  • Attached is the results of the validation for the storage.  The report returned all green.

    Microsoft Home *

    Failover Cluster Validation Report

    Node:
    SC1
    Validated
    Node:
    SC2
    Validated
    Node:
    SC3
    Validated
    Node:
    SC4
    Validated
    Started
    11/8/2013 1:40:42 PM
    Completed
    11/8/2013 1:43:34 PM
    The Validate a Configuration Wizard must be run after any change
    is made to the configuration of the cluster or hardware. For more information,
    see http://go.microsoft.com/fwlink/p/?LinkId=226879.


    Results by Category

    Name Result Summary Description
    Storage <result></result> <description>Success</description>




    Storage

    Name Result Description
    <id>List
    Disks
    </id>
    <result></result> <description>Success</description>
    <id>List
    Potential Cluster Disks
    </id>
    <result></result> <description>Success</description>
    <id>Validate
    CSV Network Bindings
    </id>
    <result></result> <description>Success</description>
    <id>Validate
    CSV Settings
    </id>
    <result></result> <description>Success</description>
    <id>Validate Disk Access
    Latency
    </id>
    <result></result> <description>Success</description>
    <id>Validate Disk Arbitration</id> <result></result> <description>Success</description>
    <id>Validate Disk Failover</id> <result></result> <description>Success</description>
    <id>Validate File System</id> <result></result> <description>Success</description>
    <id>Validate Microsoft MPIO-based
    disks
    </id>
    <result></result> <description>Success</description>
    <id>Validate Multiple
    Arbitration
    </id>
    <result></result> <description>Success</description>
    <id>Validate SCSI device Vital Product Data
    (VPD)
    </id>
    <result></result> <description>Success</description>
    <id>Validate SCSI-3 Persistent
    Reservation
    </id>
    <result></result> <description>Success</description>
    <id>Validate Simultaneous
    Failover
    </id>
    <result></result> <description>Success</description>
    <id>Validate Storage Spaces Persistent
    Reservation
    </id>
    <result></result> <description>Success</description>




    Overall Result


      Testing has completed for the tests you selected. To confirm
      that your cluster solution is supported, you must run all tests. A cluster
      solution is supported by Microsoft only if it passes all cluster validation
      tests.






    List Disks


      Description: List all disks visible to one or more nodes. If a
      subset of disks is specified for validation, list only disks in the
      subset.
      Start: 11/8/2013 1:40:45 PM.
      Prepare storage for testing.
      Begin to build matrix: 11/8/2013 1:40:49 PM.
      Begin to build candidate disk list: 11/8/2013 1:40:49 PM.
      Dump disk collection to report: 11/8/2013 1:40:50 PM.


      SC1

      Row Disk Number Disk Signature VPD Page 83h Identifier VPD Serial Number Model Bus Type Stack Type SCSI Address Adapter Eligible for Validation Disk Characteristics
      0 0 277c596d <Unknown> <Unknown> Virtual HD ATA Device ATA SCSI Port 0:0:0:0 IDE Channel False Disk is a boot volume. Disk is a system volume. Disk is used for paging
      files. Disk is used for memory dump files. Disk bus type does not support
      clustering. Disk is on the system bus. Disk partition style is MBR. Disk type is
      BASIC.
      1 1 4783148 6090A048608DC78744275545A701808C 6090A048608DC78744275545A701808C EQLOGIC 100E-00 Multi-Path Disk Device iSCSI Stor Port 3:0:0:0 Microsoft Multi-Path Bus Driver False Disk is already clustered. Disk partition style is MBR. Disk type is BASIC.
      Clustered Disk is online. Disk uses Microsoft Multipath I/O (MPIO).
      2 2 {e4aa2f35-62c9-4145-9bf9-0bb7245aeb20} 6090A048608DE7CC4427851CAB01002B 6090A048608DE7CC4427851CAB01002B EQLOGIC 100E-00 Multi-Path Disk Device iSCSI Stor Port 3:0:7:0 Microsoft Multi-Path Bus Driver True Disk is already clustered. Disk partition style is GPT. Disk type is BASIC.
      Disk uses Microsoft Multipath I/O (MPIO).
      3 3 <No signature> 6090A028905009AF99A8A40000002021 6090A028905009AF99A8A40000002021 EQLOGIC 100E-00 Multi-Path Disk Device iSCSI Stor Port 3:0:2:0 Microsoft Multi-Path Bus Driver False No disk partition style defined. Disk is RAW. RAW disks cannot be clustered.
      Disk uses Microsoft Multipath I/O (MPIO).




      SC2

      Row Disk Number Disk Signature VPD Page 83h Identifier VPD Serial Number Model Bus Type Stack Type SCSI Address Adapter Eligible for Validation Disk Characteristics
      0 0 277c596d <Unknown> <Unknown> Virtual HD ATA Device ATA SCSI Port 0:0:0:0 IDE Channel False Disk is a boot volume. Disk is a system volume. Disk is used for paging
      files. Disk is used for memory dump files. Disk bus type does not support
      clustering. Disk is on the system bus. Disk partition style is MBR. Disk type is
      BASIC.
      1 1 4783148 6090A048608DC78744275545A701808C 6090A048608DC78744275545A701808C EQLOGIC 100E-00 Multi-Path Disk Device iSCSI Stor Port 3:0:2:0 Microsoft Multi-Path Bus Driver True Disk is already clustered. Disk partition style is MBR. Disk type is BASIC.
      Disk uses Microsoft Multipath I/O (MPIO).
      2 2 {e4aa2f35-62c9-4145-9bf9-0bb7245aeb20} 6090A048608DE7CC4427851CAB01002B 6090A048608DE7CC4427851CAB01002B EQLOGIC 100E-00 Multi-Path Disk Device iSCSI Stor Port 3:0:4:0 Microsoft Multi-Path Bus Driver True Disk is already clustered. Disk partition style is GPT. Disk type is BASIC.
      Disk uses Microsoft Multipath I/O (MPIO).
      3 3 <No signature> 6090A028905009AF99A8A40000002021 6090A028905009AF99A8A40000002021 EQLOGIC 100E-00 Multi-Path Disk Device iSCSI Stor Port 3:0:3:0 Microsoft Multi-Path Bus Driver False No disk partition style defined. Disk is RAW. RAW disks cannot be clustered.
      Disk uses Microsoft Multipath I/O (MPIO).




      SC3

      Row Disk Number Disk Signature VPD Page 83h Identifier VPD Serial Number Model Bus Type Stack Type SCSI Address Adapter Eligible for Validation Disk Characteristics
      0 0 277c596d <Unknown> <Unknown> Virtual HD ATA Device ATA SCSI Port 0:0:0:0 IDE Channel False Disk is a boot volume. Disk is a system volume. Disk is used for paging
      files. Disk is used for memory dump files. Disk bus type does not support
      clustering. Disk is on the system bus. Disk partition style is MBR. Disk type is
      BASIC.
      1 1 4783148 6090A048608DC78744275545A701808C 6090A048608DC78744275545A701808C EQLOGIC 100E-00 Multi-Path Disk Device iSCSI Stor Port 3:0:2:0 Microsoft Multi-Path Bus Driver True Disk is already clustered. Disk partition style is MBR. Disk type is BASIC.
      Disk uses Microsoft Multipath I/O (MPIO).
      2 2 {e4aa2f35-62c9-4145-9bf9-0bb7245aeb20} 6090A048608DE7CC4427851CAB01002B 6090A048608DE7CC4427851CAB01002B EQLOGIC 100E-00 Multi-Path Disk Device iSCSI Stor Port 3:0:5:0 Microsoft Multi-Path Bus Driver True Disk is already clustered. Disk partition style is GPT. Disk type is BASIC.
      Disk uses Microsoft Multipath I/O (MPIO).
      3 3 <No signature> 6090A028905009AF99A8A40000002021 6090A028905009AF99A8A40000002021 EQLOGIC 100E-00 Multi-Path Disk Device iSCSI Stor Port 3:0:8:0 Microsoft Multi-Path Bus Driver False No disk partition style defined. Disk is RAW. RAW disks cannot be clustered.
      Disk uses Microsoft Multipath I/O (MPIO).




      SC4

      Row Disk Number Disk Signature VPD Page 83h Identifier VPD Serial Number Model Bus Type Stack Type SCSI Address Adapter Eligible for Validation Disk Characteristics
      0 0 277c596d <Unknown> <Unknown> Virtual HD ATA Device ATA SCSI Port 0:0:0:0 IDE Channel False Disk is a boot volume. Disk is a system volume. Disk is used for paging
      files. Disk is used for memory dump files. Disk bus type does not support
      clustering. Disk is on the system bus. Disk partition style is MBR. Disk type is
      BASIC.
      1 1 4783148 6090A048608DC78744275545A701808C 6090A048608DC78744275545A701808C EQLOGIC 100E-00 Multi-Path Disk Device iSCSI Stor Port 3:0:1:0 Microsoft Multi-Path Bus Driver True Disk is already clustered. Disk partition style is MBR. Disk type is BASIC.
      Disk uses Microsoft Multipath I/O (MPIO).
      2 2 {e4aa2f35-62c9-4145-9bf9-0bb7245aeb20} 6090A048608DE7CC4427851CAB01002B 6090A048608DE7CC4427851CAB01002B EQLOGIC 100E-00 Multi-Path Disk Device iSCSI Stor Port 3:0:8:0 Microsoft Multi-Path Bus Driver True Disk is already clustered. Disk partition style is GPT. Disk type is BASIC.
      Disk uses Microsoft Multipath I/O (MPIO).
      3 3 <No signature> 6090A028905009AF99A8A40000002021 6090A028905009AF99A8A40000002021 EQLOGIC 100E-00 Multi-Path Disk Device iSCSI Stor Port 3:0:2:0 Microsoft Multi-Path Bus Driver False No disk partition style defined. Disk is RAW. RAW disks cannot be clustered.
      Disk uses Microsoft Multipath I/O (MPIO).
      S" #6">Back to Summary
      Back to Top





      List Potential Cluster Disks


        Description: List disks that will be validated for cluster
        compatibility. Clustered disks which are online at any node will be
        excluded.
        Start: 11/8/2013 1:40:50 PM.
        Disks eligible for cluster validation: Disk Signature VPD Page 83h Identifier VPD Serial Number
        Test Disk 0 {e4aa2f35-62c9-4145-9bf9-0bb7245aeb20} 6090A048608DE7CC4427851CAB01002B 6090A048608DE7CC4427851CAB01002B
        S" #6">Back to Summary
        Back to Top





        Validate CSV Network Bindings


          Description: Validate that network bindings required by Cluster
          Shared Volumes are present.
          Start: 11/8/2013 1:40:51 PM.
          Validating File and Print Sharing network binding on node
          SC1.
          Validating File and Print Sharing network binding on node
          SC2.
          Validating File and Print Sharing network binding on node
          SC3.
          Validating File and Print Sharing network binding on node
          SC4.
          S" #6">Back to Summary
          Back to Top





          Validate CSV Settings


            Description: Validate that settings and configuration required by
            Cluster Shared Volumes are present. This test can only be run with an
            administrative account, and it only tests servers that are cluster nodes.
            Start: 11/8/2013 1:40:51 PM.
            Validating Server Message Block (SMB) share access through the
            IP address of the fault tolerant network driver for failover clustering (NetFT),
            and connecting with the user account associated with validation.
            Begin Cluster Shared Volumes support testing on node
            SC1.
            Begin Cluster Shared Volumes support testing on node
            SC2.
            Begin Cluster Shared Volumes support testing on node
            SC3.
            Begin Cluster Shared Volumes support testing on node
            SC4.
            Validating Server Message Block (SMB) share access through the
            IP address of the fault tolerant network driver for failover clustering (NetFT),
            and connecting with the Cluster Shared Volumes test user account.
            Validating access using Server Message Block (SMB) protocol from
            node SC1to a share on node SC2.
            For the new Server Message Block (SMB) share, a connection was
            successfully made by using the Cluster Shared Volumes test user account, from
            node SC1to the share on node SC2.
            Validating access using Server Message Block (SMB) protocol from
            node SC2 to a share on node SC3.
            For the new Server Message Block (SMB) share, a connection was
            successfully made by using the Cluster Shared Volumes test user account, from
            node SC2 to the share on node SC3.
            Validating access using Server Message Block (SMB) protocol from
            node SC3to a share on node SC4.
            For the new Server Message Block (SMB) share, a connection was
            successfully made by using the Cluster Shared Volumes test user account, from
            node SC3to the share on node SC4.
            Validating access using Server Message Block (SMB) protocol from
            node SC4to a share on node SC1.
            For the new Server Message Block (SMB) share, a connection was
            successfully made by using the Cluster Shared Volumes test user account, from
            node SC4to the share on node SC1.
            S" #6">Back to Summary
            Back to Top





            Validate Disk Access Latency


              Description: Validate acceptable latency for disk read and write
              operations.
              Start: 11/8/2013 1:40:52 PM.
              Validating read latency of Test Disks.
              Validating write latency of Test Disks.
              S" #6">Back to Summary
              Back to Top





              Validate Disk Arbitration


                Description: Validate that a node that owns a disk retains ownership
                after disk arbitration.
                Start: 11/8/2013 1:41:20 PM.
                Arbitration testing completed successfully on all disks.
                S" #6">Back to Summary
                Back to Top





                Validate Disk Failover


                  Description: Validate that a disk can fail over successfully with
                  data intact.
                  Start: 11/8/2013 1:41:58 PM.
                  Failover testing completed successfully on all disks.
                  S" #6">Back to Summary
                  Back to Top





                  Validate File System


                    Description: Validate that the file system on disks in shared
                    storage is supported by failover clusters.
                    Start: 11/8/2013 1:42:16 PM.
                    File System type on Test Disk 0 partition table entry 2 is
                    NTFS.
                    S" #6">Back to Summary
                    Back to Top





                    Validate Microsoft MPIO-based disks


                      Description: Validate that disks that use Microsoft Multipath I/O
                      (MPIO) have been configured correctly.
                      Start: 11/8/2013 1:40:52 PM.
                      Test Disk 0 uses Microsoft Multipath I/O (MPIO).
                      Test Disk 0 from node SC1 has 6 usable
                      path(s) to storage target.
                      Test Disk 0 from node SC2has 6 usable
                      path(s) to storage target.
                      Test Disk 0 from node SC3 has 6 usable
                      path(s) to storage target.
                      Test Disk 0 from node SC4 has 6 usable
                      path(s) to storage target.
                      Getting information about registered device-specific modules
                      (DSMs) from node SC1 .


                      SC1

                      Device-specific module (DSM) Name Major Version Minor Version Product Build QFE Number
                      Dell EqualLogic Multi-Path Device Specific Module 4 5 0 6409
                      Microsoft DSM 6 2 9200 16465
                      Getting information about registered device-specific modules
                      (DSMs) from node SC2

                      SC2

                      Device-specific module (DSM) Name Major Version Minor Version Product Build QFE Number
                      Dell EqualLogic Multi-Path Device Specific Module 4 5 0 6409
                      Microsoft DSM 6 2 9200 16465
                      Getting information about registered device-specific modules
                      (DSMs) from node SC3.


                      SC3

                      Device-specific module (DSM) Name Major Version Minor Version Product Build QFE Number
                      Dell EqualLogic Multi-Path Device Specific Module 4 5 0 6409
                      Microsoft DSM 6 2 9200 16465
                      Getting information about registered device-specific modules
                      (DSMs) from node SC4.


                      SC4

                      Device-specific module (DSM) Name Major Version Minor Version Product Build QFE Number
                      Dell EqualLogic Multi-Path Device Specific Module 4 5 0 6409
                      Microsoft DSM 6 2 9200 16465
                      S" #6">Back to Summary
                      Back to Top





                      Validate Multiple Arbitration


                        Description: Validate that in a multiple-node arbitration process,
                        only one node obtains control.
                        Start: 11/8/2013 1:41:51 PM.
                        Successfully arbitrated for Test Disk 0 from node
                        SC4.
                        S" #6">Back to Summary
                        Back to Top





                        Validate SCSI device Vital Product Data (VPD)


                          Description: Validate uniqueness of inquiry data (SCSI page 83h VPD
                          descriptors).
                          Start: 11/8/2013 1:40:55 PM.
                          SCSI page 83h VPD descriptor verification completed without
                          errors.
                          S" #6">Back to Summary
                          Back to Top





                          Validate SCSI-3 Persistent Reservation


                            Description: Validate that storage supports the SCSI-3 Persistent
                            Reservation commands.
                            Start: 11/8/2013 1:40:56 PM.
                            Test Disk 0 supports Persistent Reservation.
                            S" #6">Back to Summary
                            Back to Top





                            Validate Simultaneous Failover


                              Description: Validate that disks can fail over simultaneously with
                              data intact.
                              Validate Simultaneous Failover
                              Start: 11/8/2013 1:42:20 PM.
                              Failover testing completed successfully on all disks.
                              S" #6">Back to Summary
                              Back to Top





                              Validate Storage Spaces Persistent Reservation


                                Description: Validate that storage supports the SCSI-3 Persistent
                                Reservation commands used by clustered Storage Pools.
                                Start: 11/8/2013 1:41:04 PM.
                                Test Disk 0 supports SCSI-3 Persistent Reservation commands
                                needed to support clustered Storage Pools.
                                S" #6">Back to Summary
                                Back to Top
    Tuesday, November 12, 2013 2:10 PM
  • >What would be the alternative for a hyper-v cluster

    Is this a Hyper-V cluster, or are you trying to build a SQL Cluster?

    If this is a Hyper-V cluster, just create a SQL VM with the VHDX on the CSV.

    David


    David http://blogs.msdn.com/b/dbrowne/

    Tuesday, November 12, 2013 4:22 PM
  • It is a HV cluster with 4 VMs. 

    That is pretty much what we did.  We carved a 1 TB volume on the SAN and was hoping to present this to the other nodes in the cluster. 

    This is the error that is located in the SQL install logs

    (12) 2013-11-12 11:20:28 Slp: System Error: 1005 trying to find mount points at path \\?\Volume{0facc919-4e23-405d-a1ab-cc0aae6e45ec}\
    (12) 2013-11-12 11:20:28 Slp:     The volume does not contain a recognized file system.
    Please make sure that all required file system drivers are loaded and that the volume is not corrupted.
    (12) 2013-11-12 11:20:28 Slp: Mount point status for disk 'Cluster Disk 2' could not be determined.  Reason: 'The search for mount points failed.  Error: The volume does not contain a recognized file system.
    Please make sure that all required file system drivers are loaded and that the volume is not corrupted.'

    Tuesday, November 12, 2013 4:42 PM
  • Are you trying to install SQL Server on the Hyper-V host, or in a VM?  On a Hyper-V cluster, you should not install SQL Server on the hosts.

    David


    David http://blogs.msdn.com/b/dbrowne/

    Tuesday, November 12, 2013 4:49 PM
  • On the VM.  For example, the host is HV1 and the VM's are server1 - server4 and I'm working on server1 and during the SQL install, I chose create new failover cluster.
    Tuesday, November 12, 2013 4:56 PM
  • First, just putting a VM on a Hyper-V cluster will give you basic High Availibility.  If you add guest clustering you get faster failover and low downtime patching of the guest OS and SQL Server.

    If you want to create a guest cluster and use a Failover Cluster Instance then you need shared storage for the guest VMs.  You can use iSCSI, Virtual Fiber Channel, SMB 3.0 or in Windows Server 2012 R2 the new Shared VHD feature to provide shared storage to the VMs.

    David


    David http://blogs.msdn.com/b/dbrowne/

    Tuesday, November 12, 2013 7:10 PM
  • Thanks for all the advice.  Sorry, for the lack of knowledge. 

    Since the last post we added shared storage but it appears that the disks aren't configured correctly for the cluster.  I guess I am having a hard time understanding how the disk must be presented for SQL.  Under disks it shows as 1 large Clustered Share Volume but SQL can't see it.  In disk management, it shows as CLuster Volumn.  The error in the logs states that it can find the mount point.  Does the volume have to have a drive letter configured?

    Tuesday, November 12, 2013 8:12 PM
  • The guest VM cluster shouldn't have a Clustered Shared Volume.  The host cluster has a CSV, but SQL 2012 doesn't support CSV (SQL 2014 will). 

    You should present a the same disk to each VM in the guest cluster, if using iSCSI or Virtual Fiber Channel.

    David


    David http://blogs.msdn.com/b/dbrowne/

    Tuesday, November 12, 2013 8:42 PM
  • Ok.  That  makes sense.  One last question :)

    As I mentioned, we have one 3 tb SAN volume that was planned for storing all SQL stuff.  I have read numerous articles (and past experience) that there should be at least 2 to 3 disks.  What is the best practice for this?  Should we create multiple volumes?  Or just use 1?   

    Tuesday, November 12, 2013 9:27 PM
  • >What is the best practice for this?  Should we create multiple volumes? 

    That varies by SAN and by your expectations for performance.  

    At a minimum you should store your SQL Server backups somewhere that is very unlikely to be affected by an problems that might affect the storage location where your databases are. 

    Beyond that having a single LUN for databases, logs and TempDb will work fine, but might not meet your performance expectations.  There's no guarantee that using seperate LUNS for TempDb or Logs will actually perform better, however.  That really depends on your SAN and its configuration.

    David


    David http://blogs.msdn.com/b/dbrowne/

    • Marked as answer by nickswoca Wednesday, November 13, 2013 2:41 PM
    Tuesday, November 12, 2013 11:56 PM
  • We ended up doing a fresh install of Windows 2012 R2 and are trying to use the shared vhdx option for the sql install but it errored out on the data directories tab.  It states that the volume that contains the sql server data does not belong to the cluster group, this is correct...  What are missing here?  Thanks.

    Tuesday, November 26, 2013 9:01 PM