Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. Issues when a physical disk encounters an error in a Windows Server 2012-based environment

Issues when a physical disk encounters an error in a Windows Server 2012-based environment

View products that this article applies to.

Symptoms

Consider the following scenarios.

Scenario 1
  • You create a virtual hard disk on a storage pool in a Windows Server 2012-based cluster environment.
  • The owner node of the virtual hard disk is a different node from the owner node of the storage pool.
  • One of the physical disks in the storage pool encounters an error.
In this scenario, the virtual disks cannot be repaired.

Scenario 2
  • A physical disk encounters an error in a Windows Server 2012-based storage pool.
  • You run the Get-PhysicalDisk cmdlet.
In this scenario, the cmdlet may return an error, or may not return the complete list of physical disks.

↑ Back to the top

Cause

Scenario 1
This issue occurs because the storage pool owner node reads space configuration incorrectly.

Scenario 2
This issue occurs because data enumeration stops immediately when an error is detected.

↑ Back to the top

Resolution

Update information

To resolve these issues, install update rollup 2889784. For more information about how to obtain this update rollup package, click the following article number to go to the article in the Microsoft Knowledge Base:
2889784 Windows RT, Windows 8, and Windows Server 2012 update rollup: November 2013

↑ Back to the top

Hotfix information
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 this specific problem.

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, submit a request to 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 website:
http://support.microsoft.com/contactus/?ws=support
Note 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

To apply this hotfix, you must be running Windows Server 2012.

Registry information

To apply this hotfix, you do not have to make any changes to the registry.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows Server 2012 file information notes
Important Windows 8 hotfixes and Windows Server 2012 hotfixes are included in the same packages. However, only "Windows 8" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
    VersionProductMilestoneService branch
    6.2.920 0.16 xxxWindows Server 2012RTMGDR
    6.2.920 0.20 xxxWindows Server 2012RTMLDR
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2012" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2012
File nameFile versionFile sizeDateTimePlatform
Spaceport.sys6.2.9200.16731285,01605-Oct-201306:10x64
Spaceport.sys6.2.9200.20842285,01605-Oct-201306:01x64

↑ Back to the top

Additional file information

Additional file information for Windows Server 2012

Additional files for all supported x64-based versions of Windows Server 2012
File propertyValue
File nameAmd64_spaceport.inf_31bf3856ad364e35_6.2.9200.16731_none_6ed47ed5e017abab.manifest
File versionNot applicable
File size2,120
Date (UTC)05-Oct-2013
Time (UTC)06:14
PlatformNot applicable
File nameAmd64_spaceport.inf_31bf3856ad364e35_6.2.9200.20842_none_6f544bfef93c80bd.manifest
File versionNot applicable
File size2,120
Date (UTC)05-Oct-2013
Time (UTC)06:26
PlatformNot applicable
File namePackage_1_for_kb2896650_bf~31bf3856ad364e35~amd64~~6.2.1.0.mum
File versionNot applicable
File size1,823
Date (UTC)05-Oct-2013
Time (UTC)14:49
PlatformNot applicable
File namePackage_1_for_kb2896650~31bf3856ad364e35~amd64~~6.2.1.0.mum
File versionNot applicable
File size2,571
Date (UTC)05-Oct-2013
Time (UTC)14:49
PlatformNot applicable
File namePackage_2_for_kb2896650_bf~31bf3856ad364e35~amd64~~6.2.1.0.mum
File versionNot applicable
File size2,039
Date (UTC)05-Oct-2013
Time (UTC)14:49
PlatformNot applicable
File namePackage_2_for_kb2896650~31bf3856ad364e35~amd64~~6.2.1.0.mum
File versionNot applicable
File size2,791
Date (UTC)05-Oct-2013
Time (UTC)14:49
PlatformNot applicable
File namePackage_3_for_kb2896650_bf~31bf3856ad364e35~amd64~~6.2.1.0.mum
File versionNot applicable
File size1,815
Date (UTC)05-Oct-2013
Time (UTC)14:49
PlatformNot applicable
File namePackage_3_for_kb2896650~31bf3856ad364e35~amd64~~6.2.1.0.mum
File versionNot applicable
File size2,563
Date (UTC)05-Oct-2013
Time (UTC)14:49
PlatformNot applicable
File namePackage_for_kb2896650_rtm_bf~31bf3856ad364e35~amd64~~6.2.1.0.mum
File versionNot applicable
File size2,391
Date (UTC)05-Oct-2013
Time (UTC)14:49
PlatformNot applicable
File namePackage_for_kb2896650_rtm~31bf3856ad364e35~amd64~~6.2.1.0.mum
File versionNot applicable
File size2,442
Date (UTC)05-Oct-2013
Time (UTC)14:49
PlatformNot applicable
File nameUpdate-bf.mum
File versionNot applicable
File size1,991
Date (UTC)05-Oct-2013
Time (UTC)14:49
PlatformNot applicable

↑ Back to the top

Status

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

↑ Back to the top

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

↑ Back to the top

Keywords: kb, kbqfe, kbhotfixserver, kbfix, kbexpertiseadvanced, kbsurveynew, kbautohotfix

↑ Back to the top

Article Info
Article ID : 2896650
Revision : 1
Created on : 1/7/2017
Published on : 11/13/2013
Exists online : False
Views : 165