The volume GUID may unexpectedly change after a volume is extended on a Windows Server 2008 failover cluster node

Symptoms

Consider the following scenario:

  • On a node in a Windows Server 2008 failover cluster, you add a new disk.

  • This new disk contains some highly available resources.

  • You move the disk resource to another node, and then, on this other node, you extend a volume on the disk.

In this scenario, the volume GUID for the disk changes, and then the applications that use the disk cannot access the shared volume data.

For example, if you use Microsoft System Center Virtual Machine Manager (SCVMM) to manage the virtual machines on the disk, you receive the following error message:

Unsupported Cluster Configuration
Warning (13924)
Highly available virtual machine <name> is not supported by VMM because the VM uses non-clustered Storage.
Recommended Action
Ensure that all the files and pass-though disks belonging to the VM reside on highly available storage.
"unsupported cluster"

Cause

This issue occurs because the cluster volume GUID is updated when a disk resource is moved to another node, and then, on this other node, a volume on the disk is extended.

Resolution

Hotfix information

Important Windows Vista and Windows Server 2008 hotfixes are included in the same packages. However, only one of these products may be listed on the “Hotfix Request” page. To request the hotfix package that applies to both Windows Vista and Windows Server 2008, just select the product that is listed on the page.

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=supportNote The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

No prerequisites are required. You can apply this hotfix on a computer that is running Windows Server 2008 or Windows Server 2008 Service Pack 2 (SP2).

Restart requirement

If the computer is already a member of a cluster, you must restart the computer after you apply this hotfix. However, if the computer is not a member of a cluster yet, you do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The Global version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Vista and Windows Server 2008 file information notes
  • The files that apply to a specific product, SR_Level (RTM,SPn), and service branch (LDR, GDR) can be identified by examining the fileversion numbers as shown in the following table.

    Version

    Product

    SR_Level

    Service branch

    6.0.6000.16xxx

    Windows Vista

    RTM

    GDR

    6.0.6000.20xxx

    Windows Vista

    RTM

    LDR

    6.0.6001.18xxx

    Windows Vista and Windows Server 2008

    SP1

    GDR

    6.0.6001.22xxx

    Windows Vista and Windows Server 2008

    SP1

    LDR

    6.0.6002.18xxx

    Windows Vista and Windows Server 2008

    SP2

    GDR

    6.0.6002.22xxx

    Windows Vista and Windows Server 2008

    SP2

    LDR

  • Service Pack 1 is integrated into the original release of Windows Server 2008.

  • The MANIFEST files (.manifest) and the MUM files (.mum)that are installed for each environment are listed separately. MUM and MANIFEST files, andthe associated security catalog (.cat) files, are critical to maintaining thestate of the updated component. The security catalog files (attributes notlisted) are signed with a Microsoft digital signature.

For all supported x86-based versions of Windows Server 2008

File name

File version

File size

Date

Time

Platform

Clusres.dll

6.0.6001.22438

915,968

27-May-2009

11:49

x86

For all supported x86-based versions of Windows Server 2008 SP2

File name

File version

File size

Date

Time

Platform

Clusres.dll

6.0.6002.22140

915,968

27-May-2009

11:44

x86

For all supported Itanium-based versions of Windows Server 2008

File name

File version

File size

Date

Time

Platform

Clusres.dll

6.0.6001.22438

1,921,024

27-May-2009

11:50

IA-64

For all supported Itanium-based versions of Windows Server 2008 SP2

File name

File version

File size

Date

Time

Platform

Clusres.dll

6.0.6002.22140

1,921,024

27-May-2009

11:38

IA-64

For all supported x64-based versions of Windows Server 2008

File name

File version

File size

Date

Time

Platform

Clusres.dll

6.0.6001.22438

1,151,488

27-May-2009

12:17

x64

For all supported x64-based versions of Windows Server 2008 SP2

File name

File version

File size

Date

Time

Platform

Clusres.dll

6.0.6002.22140

1,151,488

27-May-2009

11:42

x64

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Workaround

To work around this problem, move the disk resource back to the node where the volume was originally added to the cluster, and then extend the volume.

If you do not know which node is the node where the volume was originally added to the cluster, you can determine this by following these steps:

  1. In Failover Manager Microsoft Management Console (MMC) snap-in, click the General tab in the properties of the cluster disk resource, and then find the cluster volume GUID.

  2. From an elevated command prompt on the owning node, run Mounvol.exe, and then check whether the same cluster volume GUID is returned.

  3. If a match is found, then this is the node where the volume was originally added. If no match is found, repeat these steps on the remaining nodes until a match is found.

If before you apply this hotfix, you experience the problem described in this article, the following solutions may help you recover and help you keep the new volume GUID:

  • In any affected application, use the new volume GUID to update the volume GUID in the drive path.

  • If virtual machines are affected, re-create the virtual machines by using the existing virtual hard disks and the new volume GUID.

More Information

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional file information for Windows Server 2008 and for Windows Vista

Additional files for all supported x86-based versions of Windows Server 2008 and of Windows Vista

File name

File version

File size

Date

Time

Platform

Package_for_kb970529_sc_0~31bf3856ad364e35~x86~~6.0.1.0.mum

Not Applicable

1,409

28-May-2009

10:16

Not Applicable

Package_for_kb970529_sc_1~31bf3856ad364e35~x86~~6.0.1.0.mum

Not Applicable

1,527

28-May-2009

10:16

Not Applicable

Package_for_kb970529_sc~31bf3856ad364e35~x86~~6.0.1.0.mum

Not Applicable

1,701

28-May-2009

10:16

Not Applicable

Package_for_kb970529_server_0~31bf3856ad364e35~x86~~6.0.1.0.mum

Not Applicable

1,419

28-May-2009

10:16

Not Applicable

Package_for_kb970529_server_1~31bf3856ad364e35~x86~~6.0.1.0.mum

Not Applicable

1,531

28-May-2009

10:16

Not Applicable

Package_for_kb970529_server~31bf3856ad364e35~x86~~6.0.1.0.mum

Not Applicable

1,712

28-May-2009

10:16

Not Applicable

X86_microsoft-windows-f..overcluster-clusres_31bf3856ad364e35_6.0.6001.22438_none_c14bd434b629fed2.manifest

Not Applicable

10,641

27-May-2009

13:33

Not Applicable

X86_microsoft-windows-f..overcluster-clusres_31bf3856ad364e35_6.0.6002.22140_none_c31f73e0b35fa52f.manifest

Not Applicable

10,641

27-May-2009

13:13

Not Applicable

Additional files for all supported x64-based versions of Windows Server 2008 and of Windows Vista

File name

File version

File size

Date

Time

Platform

Amd64_microsoft-windows-f..overcluster-clusres_31bf3856ad364e35_6.0.6001.22438_none_1d6a6fb86e877008.manifest

Not Applicable

10,693

27-May-2009

13:58

Not Applicable

Amd64_microsoft-windows-f..overcluster-clusres_31bf3856ad364e35_6.0.6002.22140_none_1f3e0f646bbd1665.manifest

Not Applicable

10,693

27-May-2009

13:06

Not Applicable

Package_for_kb970529_sc_0~31bf3856ad364e35~amd64~~6.0.1.0.mum

Not Applicable

1,417

28-May-2009

10:16

Not Applicable

Package_for_kb970529_sc_1~31bf3856ad364e35~amd64~~6.0.1.0.mum

Not Applicable

1,537

28-May-2009

10:16

Not Applicable

Package_for_kb970529_sc~31bf3856ad364e35~amd64~~6.0.1.0.mum

Not Applicable

1,711

28-May-2009

10:16

Not Applicable

Package_for_kb970529_server_0~31bf3856ad364e35~amd64~~6.0.1.0.mum

Not Applicable

1,427

28-May-2009

10:16

Not Applicable

Package_for_kb970529_server_1~31bf3856ad364e35~amd64~~6.0.1.0.mum

Not Applicable

1,541

28-May-2009

10:16

Not Applicable

Package_for_kb970529_server~31bf3856ad364e35~amd64~~6.0.1.0.mum

Not Applicable

1,722

28-May-2009

10:16

Not Applicable

Additional files for all supported Itanium-based versions of Windows Server 2008

File name

File version

File size

Date

Time

Platform

Ia64_microsoft-windows-f..overcluster-clusres_31bf3856ad364e35_6.0.6001.22438_none_c14d782ab62807ce.manifest

Not Applicable

10,667

27-May-2009

13:18

Not Applicable

Ia64_microsoft-windows-f..overcluster-clusres_31bf3856ad364e35_6.0.6002.22140_none_c32117d6b35dae2b.manifest

Not Applicable

10,667

27-May-2009

12:49

Not Applicable

Package_for_kb970529_server_0~31bf3856ad364e35~ia64~~6.0.1.0.mum

Not Applicable

1,423

28-May-2009

10:16

Not Applicable

Package_for_kb970529_server_1~31bf3856ad364e35~ia64~~6.0.1.0.mum

Not Applicable

1,370

28-May-2009

10:16

Not Applicable

Package_for_kb970529_server~31bf3856ad364e35~ia64~~6.0.1.0.mum

Not Applicable

1,716

28-May-2009

10:16

Not Applicable

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

Thank you for your feedback!

Thank you for your feedback! It sounds like it might be helpful to connect you to one of our Office support agents.

×