When you use Storage Spaces on a computer that is running Windows 8 or Windows Server 2012, you experience the following issues:
Assume that you mark a drive as retired, and the spare capacity in the storage pool is insufficient for reallocation. In this situation, the storage space cannot be repaired.
Note When you try to retire a drive and then repair a storage space, the system marks all extents of the storage space that reside on the drive for reallocation.
When Storage Spaces is configured to use enclosure awareness, and a Just a Bunch of Disks (JBOD) failure occurs, the disks are marked as retired incorrectly.
This issue occurs because the enclosure information is not used correctly.
This issue causes a rebuild operation to start on the storage spaces that are associated with the retired drives, which significantly increases I/O buffer on the computer. Additionally, user data is at risk because the storage spaces that are associated with the retired drives are in degraded mode. If another drive failure occurs, data will be lost.
To resolve this issue, install the Windows RT, Windows 8, and Windows Server 2012 update rollup 2845533, or install the hotfix that is described in this article.
For more information about how to obtain this update rollup package, click the following article number to view the article in the Microsoft Knowledge Base:
2845533 Windows RT, Windows 8, and Windows Server 2012 update rollup: June 2013
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:
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.
To apply this hotfix, you must be running Windows 8 or Windows Server 2012.
To use the hotfix in this package, you do not have to make any changes to the registry.
You must restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
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 8 and 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:
6.2.920 0.20 xxx
Windows 8 and Windows Server 2012
The MANIFEST (.manifest) files and the MUM (.mum) files that are installed for each environment are listed separately in the "Additional file information for Windows 8 and 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 x86-based versions of Windows 8
For all supported x64-based versions of Windows 8 and of Windows Server 2012
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about Storage Spaces, go to the following Microsoft website: