none
Cannot repair virtual disk in SS pool RRS feed

  • Question

  • Brand new installation.

    FriendlyName        CanPool             OperationalStatus   HealthStatus        Usage                  Size
    ------------        -------             -----------------   ------------        -----                              ----
    PhysicalDisk0       False               OK                  Healthy             Auto-Select                    59.63 GB
    PhysicalDisk1       False               OK                  Healthy             Auto-Select                   465.76 GB
    PhysicalDisk2       False               OK                  Healthy             Auto-Select                     1.82 TB
    PhysicalDisk3       False               OK                  Healthy             Auto-Select                   931.51 GB
    PhysicalDisk4       False               OK                  Healthy             Auto-Select                   930.75 GB
    PhysicalDisk5       False               OK                  Healthy             Auto-Select                   930.75 GB
    PhysicalDisk6       False               OK                  Healthy             Auto-Select                   930.75 GB
    PhysicalDisk7       False               OK                  Healthy             Auto-Select                   930.75 GB

    Created a Pool of 4x1GB drives (Drives 4,5,6,7)

    FriendlyName            OperationalStatus       HealthStatus            IsPrimordial            IsReadOnly
    ------------            -----------------       ------------            ------------            ----------
    Data                          OK                      Healthy                 False                   False

    Created a Virtual Disk

    FriendlyName        ResiliencySettingNa OperationalStatus   HealthStatus        IsManualAttach                     Size
                        me
    ------------        ------------------- -----------------   ------------        --------------                     ----
    StorageA            Mirror              Degraded            Warning             True                               3 TB

    PS C:\Users\Administrator> get-virtualdisk -FriendlyName "StorageA" | fl *


    Usage                             : Other
    NameFormat                        :
    OperationalStatus                 : Degraded
    HealthStatus                      : Warning
    ProvisioningType                  : Thin
    ParityLayout                      :
    Access                            : Read/Write
    UniqueIdFormat                    : Vendor Specific
    DetachedReason                    : None
    ObjectId                          : {6af478ea-131c-11e2-93f4-001517e565bd}
    PassThroughClass                  :
    PassThroughIds                    :
    PassThroughNamespace              :
    PassThroughServer                 :
    UniqueId                          : EA78F46A1C13E21193F4001517E565BD
    AllocatedSize                     : 696321572864
    FootprintOnPool                   : 1392643145728
    FriendlyName                      : StorageA
    Interleave                        : 262144
    IsDeduplicationEnabled            : False
    IsEnclosureAware                  : False
    IsManualAttach                    : True
    IsSnapshot                        : False
    LogicalSectorSize                 : 512
    Name                              :
    NumberOfAvailableCopies           : 0
    NumberOfColumns                   : 2
    NumberOfDataCopies                : 2
    OtherOperationalStatusDescription :
    OtherUsageDescription             :
    PhysicalDiskRedundancy            : 1
    PhysicalSectorSize                : 4096
    RequestNoSinglePointOfFailure     : True
    ResiliencySettingName             : Mirror
    Size                              : 3298534883328
    UniqueIdFormatDescription         :
    PSComputerName                    :
    CimClass                          : ROOT/Microsoft/Windows/Storage:MSFT_VirtualDisk
    CimInstanceProperties             : {ObjectId, PassThroughClass, PassThroughIds, PassThroughNamespace...
    CimSystemProperties               : Microsoft.Management.Infrastructure.CimSystemProperties

    The volume on the disk is instead healthy:

    DriveLetter       FileSystemLabel  FileSystem       DriveType        HealthStatus        SizeRemaining             Size
    -----------       ---------------  ----------       ---------        ------------        -------------             ----
    <deleted volumes>
    H                 StorageA Disk    ReFS             Fixed            Healthy                   2.38 TB             3 TB

    Repair from PowerShell does not do anything.

    Repair from GUI shows Repairing 0% for an instant then stops.

    I have check and tested the drives with a SMART utility and they are all fine.

    Can anybody help ?

    Thanks

    Lucio

    Thursday, October 25, 2012 8:04 PM

Answers

  • Hi,

    Please try to upgrade the Sil 3114 SoftRaid 5 Controller driver/firmware to have a try.

    If we want see if there are any more detail storage space related logs, we can open event viewer->Applications and Services logs->Microsoft->StorageSpace-Driver/StorageSpaces-ManagementAgent/StorDiag.

    Regards,


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Friday, October 26, 2012 10:09 AM

All replies

  • Hello Lucio,
     
    Thank you for your question.

    I am currently looking into this issue and will give you an update as soon as possible.
     
    Thank you for your understanding and support.


    TechNet Subscriber Support in forum |If you have any feedback on our support, please contact tnmff@microsoft.com.

    Friday, October 26, 2012 8:24 AM
    Moderator
  • Hi,

    Please run chkdsk /f /r command to have a try.

    Did you create the disk group on a Windows 8 client or a Windows Server 2012 server?

    Regards,


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Friday, October 26, 2012 8:36 AM
  • The server is Win 2012. And I have an Intel S3210SH Motherboard with an Intel Q6600 processor. The four drives in question are on a Sil 3114 SoftRaid 5 Controller, but are in JBOD config. The other drives are on the motherboard SATA using the Standard SATA AHCI controller in Server 2012.

    The only disk error in the logs is from 3 weeks ago:

    Log Name:  System
    Source:        disk
    Date:          10/8/2012 1:15:15 PM
    Event ID:      150
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      WIN-I4TUUG7N4CL
    Description:
    Disk 8 has reached a logical block provisioning permanent resource exhaustion condition.

    It would seem related, but I am not sure if it was before or after I created the pool. In any case there are no disk events since then.

    I have no way to understand what is going on. Are there any additional Storage Space diagnostics ?

    Thanks.

    LP

     

     

    Friday, October 26, 2012 9:30 AM
  • Hi,

    Please try to upgrade the Sil 3114 SoftRaid 5 Controller driver/firmware to have a try.

    If we want see if there are any more detail storage space related logs, we can open event viewer->Applications and Services logs->Microsoft->StorageSpace-Driver/StorageSpaces-ManagementAgent/StorDiag.

    Regards,


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Friday, October 26, 2012 10:09 AM
  • Hi,

    How are things going on your end? Please keep me posted on this issue. I appreciate your time and efforts.

    Regards,


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Tuesday, October 30, 2012 2:49 AM
  • Having the same issue on a Windows 2012 Essentials. This morning one of  the 3 HD in my storage pool was listed as retired and the 3 virtual disks on the pool had a warning. I checked the SMART values on the drive and everything is good, even the Get-Physical disk details show a healthy drive.

    If I manually use the set-physicaldisk -usage autoselect, it stays like that until I try to repair the virtualdisks, at which point, it reverts back to retired. Running repair on the virtualdisks does nothing at all, so I' stuck.

    Any suggestion would be appreciated.

    Wednesday, October 31, 2012 3:53 PM
  • hi guys, I have the same problem in my Server 2012 R2 Standard setup using storage tiering.

    Regarding to my sys. Ive have 3 ssds, one for my OS itself, 2 for the write back caches in OS with two partitions on.

    The background is, that I wanted to have two parity storage tiers with only two SSDs in my system. I realize this using four virtual disks on these two physical SSDs drives. 

    I need to mount these 4 virtual ssds every system boot (doing rarely) + then a short repair and all is fine - usually.

    The problem was, that in my Avoton 12x SATA ASrock board, the marvell sata stuff caused my system to behave weired. Any how, it lost contact to some discs from time to time and i wasnt even able to shut down the Server system normaly.

    I updated to the normal marvel drivers and the discs are all fine in my system (no warning at all... i think i have had green status on both pools and i still have these green status but my second virtual disc on pool 1 is degraded and unable to be repaired.

    Pic below.

    Whatever I try, I cant repair that degraded virtual disk and a "repair" takes 3 sec. 

    I have no idea what I can do there and how my space reacts on a missing disk.


    Thursday, April 17, 2014 6:22 PM
  • Krautmaster1 I'm having exactly the same problem.  I have a JBOD array (Dell MD3060e with 60 x 3TB SAS drives).  I had one of the disks go bad last week.  The disk was listed as retired upon beginning.  I replaced the drive, removed the bad disk from storage spaces, added the new disk to my storage pool, ran the "repair virtual disk" in Storage Spaces GUI (and in powershell), yet the Virtual Disk still shows as Degraded.  Now my free space in my pool was ~50GB or so (I wanted to allocated the largest pool available for my partition).  Thinking that was my problem, I added a number of extra hard disks to get that free space above 2.73 TB threshold (2.95TB free).  However, I still cannot seem to get that Virtual Disk out of a degraded state.    I'd rather not rebuild the whole virtual disk and work through this issue as drive fail again over time.  I'm looking for suggestions.  I'm not finding any events that would tell my the crucial "why" or what I'm doing wrong. 

    Below is the article I was referencing above about having enough "unused capacity" on the other disk.  It's quite possible I misunderstood the meaning of "unused capacity", however I had the extra drives, so I added them to see.  No dice.

    http://social.technet.microsoft.com/wiki/contents/articles/11382.storage-spaces-frequently-asked-questions-faq.aspx#How_do_I_know_repairing_a_storage_space_starts_and_successfully_completes

    The pool has at least as much unused capacity on other disks as the amount of data the old disk hosts. This ensures that the storage spaces can be reconstructed with a replacement disk. If the usage type of the disk is manual, then the storage spaces that depend on the disk must have sufficient unused capacity on other disks in their list of disks they can use. In both cases, the unused capacity must be on disks that do not already host an extent of the same stripe as the old disk. This can be satisfied by first adding the new disk to the pool, and, if applicable, adding it to the storage spaces’ lists of disks that they can use.

    Monday, June 15, 2015 7:37 PM