共用方式為

the volume that contains the sql server data directory does not belong to the cluster group

  • 發行項

When you install a failover cluster, then try and add SQL to one of the nodes, you might be told on the selection screen that the volume that contains the sql server data directory <volume> does not belong to the cluster group. This had me scratching my head for a few minutes.
Turns out that you need shared storage, but don't add it to the cluster yet.
In my case I had three drives. A witness, a CSV, and a drive sitting in available storage. None of them would work. So I removed the available storage from the cluster and pointed the install at that drive and it worked. It took a few minutes while the wizard validated the storage selection but it did eventually work.
EDIT: I did this again and put the disk in maintenance mode and that also worked.

Comments

  • Anonymous
    September 01, 2015
    Hi,
    You pointed the installation to which drive?
    " So I removed the available storage from the cluster and pointed the install at that drive ..."

    Thanks,
    Tanja
  • Anonymous
    September 01, 2015
    Hi,

    Our problem was that the main mount point was used by a failed installation (by a fictional Full Text service that obviously didn't exist as this was a new instalation).

    Example: we have M: mount point, with 6 mounted points underneath M:, like M:SQL_Data, M:SQL_Log, M:SQL_temp, etc... M: resource was used by fictional "MS SQL Full Text..." service. The other resources were perfectly OK. At the installation screen, we were prompted with all 6 resources, except for M: itself.

    Solution: We re-created the mount point resource for M: only, re-ran the installation, picked only M:(there was no need to pick other 6 mount points, Installer did that itself) and it worked.

    Tanja
  • Anonymous
    September 01, 2015
    Hi,

    Our problem was that the main mount point was used by a failed installation (by a fictional Full Text service that obviously didn't exist as this was a new instalation).

    Example: we have M: mount point, with 6 mounted points underneath M:, like M:SQL_Data, M:SQL_Log, M:SQL_temp, etc... M: resource was used by fictional "MS SQL Full Text..." service. The other resources were perfectly OK. At the installation screen, we were prompted with all 6 resources, except for M: itself.

    Solution: We re-created the mount point resource for M: only, re-ran the installation, picked only M:(there was no need to pick other 6 mount points, Installer did that itself) and it worked.

    Tanja