Storage Spaces Disk Failure Notifications

Hi there,
I work with backup & recovery systems on a daily basis & am always seeing disk failures - it comes with the turf, high data turn over means more wear & tear... Now Server 2012 I'm a big fan on & I thought "Why not give Storage Spaces
a chance"... At present I'm facing a critical flaw... notifications of disk failures... I can't see any easy out-of-the-box solution in place.
Is there something I'm missing? All I want is email notifications in the event of a disk failure & also some visible notification when I log into the server to say "Hey... dead hard drive, fix your $"
I don't want to have to rely on the Hot Spares & the manual checks to catch something as critical as disk failures.
Kind Regards,
Si

Thanks Shaon,
Perhaps I was mistaken, but I thought Microsoft was attempting to remove need for Hardware RAID & Reliance on the Hardware for Redundancy. Based on no built in reporting for the Hardware Status, this isn't really a usable product... disappointing. :-(
Kind Regards, 
Si

Similar Messages

  • Storage Spaces disk removal of damaged HDD failing

    Hi, and thanks in advance for any help!
    The general situation: I have a Windows 8.1 Pro machine acting as a home server. The storage spaces volume (singular) consists of a 4-disk array with 2TB drives in Parity mode. It's usage is 70ish% but honestly, maybe 50GB is important to
    recover, the rest are ISO's which I have the physical disks to so no big deal if I lose those. The volume is in a bad place and I need to either get it functional again or get the data off of it and start with a fresh volume.
    What seems to be wrong: One of the drives has failed. When the drive is attached the volume (D:) appears to mount but explorer hangs/crashes when attempting to access D:\. Storage spaces hangs/crashes as soon as you click "Change Settings".
    Task Manager registers 100% I/O usage of the volume at those times. Taking the drive to another machine and running CrystalDiskInfo indicates a few fatal failures. Removal of the drive returns the system to a functional state but D:\ goes away.
    Attempts to fix the issue so far: With the drive attached the storage pool will say 'repairing' and sit at 0% for at least 3 hours (at which point I gave up). All further attempts I've made have been w
    ith the bad drive physically removed. Removal of the drive via the GUI shows this error
    Can't Remove Drive from the pool
    Details: Drive could not be removed because not all data could be reallocated. Add an additional drive to this pool and reattempt this operation
    At first I thought, simple: buy another 2TB drive and rinse-repeat. Did that, same error. This morning I went a step further thinking that maybe the 2TB drive was too small, fine- bought a 4TB drive, added that, same error output. Ok, since I have that 2TB
    drive sitting on my desk, throw that in too, maybe having both the replacement 2TB drive and additional 4TB drive in the pool is good? no dice, same error.
    I work as a systems guy for Linux so command line doesn't scare me, I'm not familiar with PowerShell specifics but I did some reading and tried everything that made sense (after a lot of googling and get-help <command> -full). I can't seem to remove
    the drive from the pool and without it the volume wont mount. A general summary of the situation is below:
    PS C:\WINDOWS\system32> Get-StoragePool
    FriendlyName OperationalStatus HealthStatus IsPrimordial IsReadOnly
    Primordial OK Healthy True False
    Storage pool Degraded Warning False False
    PS C:\WINDOWS\system32> Get-VirtualDisk
    FriendlyName ResiliencySettingNa OperationalStatus HealthStatus IsManualAttach Size
    me
    SafeStorage Parity Detached Unhealthy False 4.8 TB
    PS C:\WINDOWS\system32> Get-PhysicalDisk
    FriendlyName CanPool OperationalStatus HealthStatus Usage Size
    ST4000DM000-1F21... False OK Healthy Auto-Select 3.64 TB
    ST2000DM001-1CH1... False OK Healthy Auto-Select 1.82 TB
    ST2000DM001-1CH1... False OK Healthy Auto-Select 1.82 TB
    ST2000DM001-1CH1... False OK Healthy Auto-Select 1.82 TB
    PhysicalDisk3 False OK Healthy Auto-Select 117.38 GB
    BADBADBAD False Lost Communication Warning Retired 1.82 TB
    ST ST2000DM001-1... False OK Healthy Auto-Select 1.82 TB
    PS C:\WINDOWS\system32> $bd = Get-PhysicalDisk -Friendlyname "BADBADBAD"
    PS C:\WINDOWS\system32> echo $bd
    FriendlyName CanPool OperationalStatus HealthStatus Usage Size
    BADBADBAD False Lost Communication Warning Retired 1.82 TB
    PS C:\WINDOWS\system32> Remove-PhysicalDisk -PhysicalDisks $bd -StoragePoolFriendlyName "Storage pool"
    Confirm
    Are you sure you want to perform this action?
    Removing a physical disk will cause problems with the fault tolerance capabilities of the following storage pool:
    "Storage pool".
    [Y] Yes [A] Yes to All [N] No [L] No to All [S] Suspend [?] Help (default is "Y"):
    Remove-PhysicalDisk : One of the physical disks specified could not be removed because it is still in use.
    At line:1 char:1
    + Remove-PhysicalDisk -PhysicalDisks $bd -StoragePoolFriendlyName "Storage pool"
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : NotSpecified: (StorageWMI:ROOT/Microsoft/..._StorageCmdlets) [Remove-PhysicalDisk], CimE
    xception
    + FullyQualifiedErrorId : StorageWMI 51004,Remove-PhysicalDisk
    PS C:\WINDOWS\system32>
    Any ideas? Again, all I really need is about 50GB of data off this array so if even there is a way to temporarily mount the volume, pull the data, and start of I'm game. Thanks again for your help!

    Hi,
    How did you remove that disk and return the disk?
    Please follow this article to operate for test:
    Storage Spaces in Windows 8 and 8.1
    https://www.winhelp.us/storage-spaces-in-windows-8.html
    Please Note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
    In addition, verify the account to upload the picture or upload the picture to the OneDrive and share the link.
    Karen Hu
    TechNet Community Support

  • Storage Spaces - Disk Removal

    Hello All,
     I have an install of Server 2012 R2. I am running Storage Spaces in a parity with a number of drives.
     I had a drive failing, so I set it to retired, and began a repair job.
     Midway through the repair job, the disk failed.
     I no longer seem to have the ability to bring the Virtual Disk back to healthy.
    Some PS outputs;
    PS C:\Users\Administrator> Get-PhysicalDisk | ? OperationalStatus -ne OK | fl
    ObjectId                         : {1}\\ZEUS\root/Microsoft/Windows/Storage/Providers_v2\SPACES_PhysicalDisk.ObjectId="
                                       {ed8bbb6f-d7b2-11e3-80b5-806e6f6e6963}:PD:{189a158c-fd27-11e3-80c9-806e6f6e6963}"
    PassThroughClass                 :
    PassThroughIds                   :
    PassThroughNamespace             :
    PassThroughServer                :
    UniqueId                         :
    AllocatedSize                    : 239712862208
    BusType                          : Unknown
    CannotPoolReason                 : In a Pool
    CanPool                          : False
    Description                      :
    DeviceId                         :
    EnclosureNumber                  :
    FirmwareVersion                  :
    FriendlyName                     : PhysicalDisk-1
    HealthStatus                     : Warning
    IsIndicationEnabled              :
    IsPartial                        : False
    LogicalSectorSize                : 0
    Manufacturer                     :
    MediaType                        : UnSpecified
    Model                            :
    OperationalStatus                : Lost Communication
    OtherCannotPoolReasonDescription :
    PartNumber                       :
    PhysicalLocation                 :
    PhysicalSectorSize               : 0
    SerialNumber                     :
    Size                             : 499289948160
    SlotNumber                       :
    SoftwareVersion                  :
    SpindleSpeed                     : 0
    SupportedUsages                  : {Auto-Select, Manual-Select, Hot Spare, Retired...}
    Usage                            : Retired
    PSComputerName                   :
    PS C:\Users\Administrator> Get-PhysicalDisk | ? OperationalStatus -ne OK | get-virtualdisk
    FriendlyName        ResiliencySettingNa OperationalStatus   HealthStatus        IsManualAttach                    
    Size
                        me
    Array               Parity              Degraded            Warning            
    True                            12.4 TB
    PS C:\Users\Administrator> get-physicaldisk
    FriendlyName        CanPool             OperationalStatus   HealthStatus        Usage                             
    Size
    PhysicalDisk2       False               OK                  Healthy            
    Auto-Select                     2.73 TB
    PhysicalDisk6       False               OK                  Healthy            
    Auto-Select                   930.25 GB
    PhysicalDisk20      False               OK                  Healthy            
    Auto-Select                      464 GB
    PhysicalDisk21      False               OK                  Healthy            
    Auto-Select                      464 GB
    PhysicalDisk-1      False               Lost Communication  Warning             Retired                         
    465 GB
    PhysicalDisk1       False               OK                  Healthy            
    Auto-Select                     2.73 TB
    PhysicalDisk17      False               OK                  Healthy            
    Auto-Select                   929.75 GB
    PhysicalDisk19      False               OK                  Healthy            
    Auto-Select                   929.75 GB
    PhysicalDisk7       False               OK                  Healthy            
    Auto-Select                   930.25 GB
    PhysicalDisk18      False               OK                  Healthy            
    Auto-Select                   929.75 GB
    PhysicalDisk22      False               OK                  Healthy            
    Auto-Select                   147.25 GB
    PhysicalDisk0       False               OK                  Healthy            
    Auto-Select                     1.82 TB
    PhysicalDisk3       False               OK                  Healthy            
    Auto-Select                     1.82 TB
    PhysicalDisk23      False               OK                  Healthy            
    Auto-Select                   232.25 GB
    PhysicalDisk5       False               OK                  Healthy            
    Auto-Select                   929.75 GB
    PhysicalDisk8       False               OK                  Healthy            
    Auto-Select                   277.75 GB
    PhysicalDisk9       False               OK                  Healthy            
    Auto-Select                   277.75 GB
    PhysicalDisk10      False               OK                  Healthy            
    Auto-Select                   277.75 GB
    PhysicalDisk11      False               OK                  Healthy            
    Auto-Select                   277.75 GB
    PhysicalDisk12      False               OK                  Healthy            
    Auto-Select                   277.75 GB
    PhysicalDisk13      False               OK                  Healthy            
    Auto-Select                   277.75 GB
    PhysicalDisk14      False               OK                  Healthy            
    Auto-Select                   277.75 GB
    PhysicalDisk15      False               OK                  Healthy            
    Auto-Select                   277.75 GB
    PhysicalDisk16      False               OK                  Healthy            
    Auto-Select                   277.75 GB
    PhysicalDisk24      False               OK                  Healthy            
    Auto-Select                   232.25 GB
    PhysicalDisk4       False               OK                  Healthy            
    Auto-Select                   136.12 GB
    My current virtual disk is 12.4 TB, and I have 4.76TB free in the Storage Space.
    Any ideas on how I can remedy this?
    Thanks

    Hi,
    What kind of virtual disk  are you currently using, simple, mirror or parity?
    If it is simple virtual disk you may not able to repair it as it provide no redundance.
    If it is parity or mirror, you need to add a new hard disk for replacing the failed disk before the virtual disk back to work.
    However please run following cmdlet first:
    get-virtualdisk -friendlyname <name> |FC
    Check the NumberOfColumns property. 
    If it is not 1, you need to add more hard disks to get it back to work. See the last QA in this FAQ thread:
    [Forum FAQ] Frequently Asked Questions for Storage Pool issues  
    http://social.technet.microsoft.com/Forums/windowsserver/en-US/77d34855-cbe6-4ea7-b3cf-567a03580049/forum-faq-frequently-asked-questions-for-storage-pool-issues?forum=winserverfiles
    If you have any feedback on our support, please send to [email protected]

  • Storage Spaces - Disk Crash

    Having some issues and hoping someone might be able to chime in and provide me a little guidance.
    Situation:
    Had a 3 Disk, 3tb per disk, storage pool. I created a parity space with 4tb thin. Yesterday I had a drive complete crash.  I purchased a new drive and stuck it in. I added the new drive to the pool BEFORE realizing that I needed to retire the bad drive.
    After adding I did a repair and the space just expanded onto the new drive but did not rebuild. This put the array into a "unknown" health status. I have now realized my mistake and should have "Retired" the broken drive before adding the
    new drive and doing the repair.
    Anyone have any suggestions on how I might get it to rebuild? The new drive shows a usage of 100mb where the 2 old parity drives show 2.2tb out of 2.8tb used.

    Hi,
    As you performed a repair backup retiring the bad drive, repair will only move modified data to the new disk.
    Please try to retire the bad disk now by running "Set-PhysicalDisk PhysicalDisk-1 -Usage Retired" and do a repair again. It will have fix your current issue. 
    If you have any feedback on our support, please send to [email protected]

  • Disk Failure notifications, etc

    Is there a tool to show/email/notify of any hard drive or equipment failures? I setup a new server last week, everything was running fine and today I find that the software mirror'ed Raid, one of the drives had failed. For how long no one knows. Is there a tool I need to use to notify me of this? Am I missing something?
    Thanks

    Interesting...and expensive. I sure wish there were other options to work with. I will keep looking.
    Safe to say that if I cant verify the disk, the disk is toast? It hangs during verify.
    I killed off the raid, which split the drives into two drives, but of course one was screwed, so I am still running, but I will have to power off the machine to pull out the dead drive. Best bet is its dead hey?

  • How to calculate the disk failure level for a 3-way mirror pool?

    On another post in this forum, the following information regarding a 3-way mirroring storage pool is given:
    Pool requires a quorum of 50% plus drives to be present to survive.
    with 3 way mirror - we have a guarantee of surviving 2 disk failure.
    Maintaining the above requirements and providing the guarantee -
    mandates us to have minimum 5 disks in pool. As if we loose 2, we still
    have 3 in the pool (>50%) for pool to maintain it's quorum.
    Just to be sure, I would like Microsoft to confirm that the following calculation applies to any number of disks in a 3-way mirroring pool.
    If the number of disks in a 3-way mirroring pool is n, INT(n/2) disks can fail without data loss.
    Examples:
    With 5 disks, INT(5/2)=INT(2.5)=2 disks can fail.
    With 6 disks, INT(6/2)=INT(3)=3 disks can fail.
    With 9 disks, INT(9/2)=INT(4.5)=4 disks can fail.
    Am I right in this assumption?
    Thanks for your answer.

    Hi,
    >>Am I right in this assumption?
    Based on my understanding, it’s not this case.
    Mirror spaces are designed for increased performance and protect your files from drive failure by keeping more than one copy. Two-way mirror spaces make two copies of your
    files and can tolerate one drive failure, while three-way mirror spaces can tolerate two drive failures.
    Regarding this point, the following thread can be referred to for better understanding.
    Storage Spaces - Disk resiliency
    http://social.technet.microsoft.com/Forums/en-US/8f13ecf3-61c8-4505-90da-e8a01023c62d/storage-spaces-disk-resiliency?forum=winserverfiles
    In addition, regarding storage spaces, the following article can be referred to for more information.
    Storage Spaces Overview
    http://social.technet.microsoft.com/wiki/contents/articles/15198.storage-spaces-overview.aspx
    Best regards,
    Frank Shen

  • Problems with Storage Spaces

    I have a storage space with 10 drives, with over 10GB of free disk space in the pool.   Occasionally, certain of my spaces are inaccessible, presumably because two drives intermittently fail; these two drives total2.5g of physical space.  
    I have retired the two drives, but storage spaces will not let me remove them.  When I click remove it says : "cant remove the drive from the pool", "drive could not be removed because not
    all data could be reallocated. Add an additional drive to this pool and reattempt this operation".  
    How can I address this problem? 

    Hi,
    According to Storage Space FAQ, you could find the reason:
    Why do I have a low capacity warning even though I still have unused pool capacity?
    Storage Spaces provides advance notification of thinly provisioned storage spaces when the storage pool does not have enough capacity spread among a sufficient number of disks to continue to write new data. The default warning point is 70% capacity utilization.
    To learn when Storage Spaces will generate a warning, consider the following example.
    A two column, two-way mirror space that uses thin provisioning in a four disk pool
    Two of the disks have 1TB capacity and two have 2TB capacity. Because a two column, two-way mirror space needs four disks (number_of_disks = NumberOfColumns * NumberOfDataCopies), it will evenly consume all four disks as it writes new data. When capacity
    utilization of the two 1TB disks reaches 70%, Storage Spaces will warn of a low capacity condition. Even though the entire pool has 3.2TB free capacity, the thinly provisioned space will soon not be able to write any more data because the 1TB disks are nearly
    fully consumed.
    You can easily keep individual storage spaces’ low capacity warning synchronized with each other and with the pool by following the guidance in the next section, “How do I increase pool capacity?” from the moment of creating the pool and through all
    subsequent expansions of the pool.
    For more details, please refer to the link below:
    Storage Spaces Frequently Asked Questions (FAQ):
    http://social.technet.microsoft.com/wiki/contents/articles/11382.storage-spaces-frequently-asked-questions-faq.aspx
    Roger Lu
    TechNet Community Support

  • Storage Spaces UI missing disks when a controller reports the same UniqueID for all attached disks (e.g. Supermicro AOC-SASLP-MV8)

    Summary: The Storage Spaces UI has several problems when there are more than 21 physical disks available to Storage Spaces.
    I have 28 SATA disks connected over 6 controllers. 2 are used for an Intel motherboard RAID1 for OS (PhysicalDisk0), so that leaves 26 data disks for Storage Spaces. [The plan is to get to 36 data disks in due course by adding disks (this 36-bay chassis: http://www.supermicro.com/products/chassis/4U/847/SC847A-R1400LP.cfm)]
    Initially, there were 23 data disks (5x 1TB, 1x 640GB, 14x 500GB, 3x 250GB) as PhysicalDisk1-23 (in that order), which I put into a storage pool. I created a parity disk over all 23 disks. It looks like it is working fine, albeit very slowly on writes.
    I've now added 3 more 4TB disks, as PhysicalDisk24-26, and taken them offline, and have now noticed errors in the Storage Pools UI in the Server Manager. For example:
    * No more than 21 disks ever show up in the "Physical Disks" area in the lower right. When the 23 disks are connected, only the first 21 show up in the pool I created. With 26 disks connected, only the first 20 show up in the pool, and only 1 more of the
    new 3 (PhysicalDisk26) shows up in the Primordial group.
    * In the Properties of the parity Virtual Disk created over the 23 disks, the disks are shown incorrectly. Again, only 21 disks are shown, and PhysicalDisk26 is incorrectly shown as part of the virtual disk. See image:
    * Using the New Storage Pool Wizard, I cannot add more than 1 of the new 3 disks to a new Storage Pool (only PhysicalDisk26 is available). And the details incorrectly refer to PhysicalDisk21. See image (a WDC WD2500JD-22H is a 250GB disk, not a 4TB disk).
    Thus I cannot use the new disks in a new storage pool.
    According the blog post at http://blogs.msdn.com/b/b8/archive/2012/01/05/virtualizing-storage-for-scale-resiliency-and-efficiency.aspx:
    Q) What is the minimum number of disks I can use to create a pool? What is the maximum?
    You can create a pool with only one disk. However, such a pool cannot contain any resilient spaces (i.e. mirrored or parity spaces). It can only contain a simple space which does not provide resiliency to failures. We do test pools comprising multiple hundreds
    of disks – such as you might see in a datacenter. There is no architectural limit to the number of disks comprising a pool.
    However, the UI currently does not seem to correctly work with more than 21 physical disks. Please advise.
    Using Server 2012 RC.
    Hardware: Supermicro X8SAX (BIOS v2.0), Intel i7-920 2.67GHz, 6x 2GB DDR3-1333 (certified Crucial CT25664BA1339.16SFD)
    Disk controllers: 2x RAIDCore BC4852 (PCI-X, final 3.3.1 driver) (15 ports used), 2x Supermicro AOC-SASLP-MV8 (PCIe, 4.0.0.1200 Marvell driver to allow >2TB disks) (6 ports used), Sil 3114 (PCI, latest 1.5.20.3 driver) (1 port used), motherboard Intel
    in RAID mode (4 ports used for data, plus 2 for OS RAID1).

    An update. I added 16x SATA disks across 2x Supermicro AOC-SASLP-MV8. All 16 disks report the same UniqueID.
    I have 25 disks in the pool now (23 as parity; 2 as journal added via PowerShell). 10 of these are on the two AOC-SASLP-MV8 controllers. Only the first 16 disks show up in the UI, so 9 are missing from the UI - which is consistent with this UI bug where
    only one disk per UniqueID shows up. PowerShell does work to manage the SS.
    PS C:\Users\administrator.TROUNCE> Get-PhysicalDisk | format-list FriendlyName, UniqueId, ObjectId, BusType
    FriendlyName : PhysicalDisk6
    UniqueId     : 00280000004000004FB116493C169A1A
    ObjectId     : {7ab38e00-ab87-11e1-bbbd-806e6f6e6963}
    BusType      : Fibre Channel
    FriendlyName : PhysicalDisk7
    UniqueId     : 00280000004000001AE48E5088028D0D
    ObjectId     : {7ab38e02-ab87-11e1-bbbd-806e6f6e6963}
    BusType      : Fibre Channel
    FriendlyName : PhysicalDisk8
    UniqueId     : 002800000040000020C9A6680224E32F
    ObjectId     : {7ab38e04-ab87-11e1-bbbd-806e6f6e6963}
    BusType      : Fibre Channel
    FriendlyName : PhysicalDisk9
    UniqueId     : 0028000000400000FDE73E7254A60C4C
    ObjectId     : {7ab38e06-ab87-11e1-bbbd-806e6f6e6963}
    BusType      : Fibre Channel
    FriendlyName : PhysicalDisk23
    UniqueId     : 0050430000000000
    ObjectId     : {7ab38e08-ab87-11e1-bbbd-806e6f6e6963}
    BusType      : RAID
    FriendlyName : PhysicalDisk22
    UniqueId     : 0050430000000000
    ObjectId     : {7ab38e0a-ab87-11e1-bbbd-806e6f6e6963}
    BusType      : RAID
    FriendlyName : PhysicalDisk21
    UniqueId     : 0050430000000000
    ObjectId     : {7ab38e0c-ab87-11e1-bbbd-806e6f6e6963}
    BusType      : RAID
    FriendlyName : PhysicalDisk20
    UniqueId     : 0050430000000000
    ObjectId     : {7ab38e0e-ab87-11e1-bbbd-806e6f6e6963}
    BusType      : RAID
    FriendlyName : PhysicalDisk5
    UniqueId     : 0028000000400000272BA74A52309853
    ObjectId     : {7ab3900f-ab87-11e1-bbbd-002590520253}
    BusType      : Fibre Channel
    FriendlyName : PhysicalDisk19
    UniqueId     : 0050430000000000
    ObjectId     : {7ab38e10-ab87-11e1-bbbd-806e6f6e6963}
    BusType      : RAID
    FriendlyName : PhysicalDisk4
    UniqueId     : 00280000004000009DE164099941430A
    ObjectId     : {7ab39011-ab87-11e1-bbbd-002590520253}
    BusType      : Fibre Channel
    FriendlyName : PhysicalDisk18
    UniqueId     : 0050430000000000
    ObjectId     : {7ab38e12-ab87-11e1-bbbd-806e6f6e6963}
    BusType      : RAID
    FriendlyName : PhysicalDisk11
    UniqueId     : 0028000000400000967EB0559AB4E351
    ObjectId     : {7ab39013-ab87-11e1-bbbd-002590520253}
    BusType      : Fibre Channel
    FriendlyName : PhysicalDisk17
    UniqueId     : 0050430000000000
    ObjectId     : {7ab38e14-ab87-11e1-bbbd-806e6f6e6963}
    BusType      : RAID
    FriendlyName : PhysicalDisk24
    UniqueId     : 0050430000000000
    ObjectId     : {7ab38e16-ab87-11e1-bbbd-806e6f6e6963}
    BusType      : RAID
    FriendlyName : PhysicalDisk10
    UniqueId     : 0028000000400000B22A722C8AD2557B
    ObjectId     : {df23f916-c19f-11e1-bbf5-806e6f6e6963}
    BusType      : Fibre Channel
    FriendlyName : PhysicalDisk16
    UniqueId     : 0028000000400000DA4D24536A847E52
    ObjectId     : {7ab38e19-ab87-11e1-bbbd-806e6f6e6963}
    BusType      : Fibre Channel
    FriendlyName : PhysicalDisk15
    UniqueId     : 00280000004000005DEDFF007783A242
    ObjectId     : {7ab38e1b-ab87-11e1-bbbd-806e6f6e6963}
    BusType      : Fibre Channel
    FriendlyName : PhysicalDisk14
    UniqueId     : 002800000040000018C9CF6EBE605911
    ObjectId     : {7ab38e1d-ab87-11e1-bbbd-806e6f6e6963}
    BusType      : Fibre Channel
    FriendlyName : PhysicalDisk13
    UniqueId     : 0028000000400000B64436290D155A48
    ObjectId     : {7ab38e1f-ab87-11e1-bbbd-806e6f6e6963}
    BusType      : Fibre Channel
    FriendlyName : PhysicalDisk0
    UniqueId     : IDE\DiskOS1.0.00__\4&180adc7b&0&0.0.0:Trounce-Server2
    ObjectId     : {df23f925-c19f-11e1-bbf5-806e6f6e6963}
    BusType      : RAID
    FriendlyName : PhysicalDisk31
    UniqueId     : 0050430000000000
    ObjectId     : {df241daf-c19f-11e1-bbf5-002590520253}
    BusType      : RAID
    FriendlyName : PhysicalDisk32
    UniqueId     : 0050430000000000
    ObjectId     : {df241db2-c19f-11e1-bbf5-002590520253}
    BusType      : RAID
    FriendlyName : PhysicalDisk27
    UniqueId     : 0050430000000000
    ObjectId     : {df241cbe-c19f-11e1-bbf5-002590520253}
    BusType      : RAID
    FriendlyName : PhysicalDisk28
    UniqueId     : 0050430000000000
    ObjectId     : {df241cc1-c19f-11e1-bbf5-002590520253}
    BusType      : RAID
    FriendlyName : PhysicalDisk34
    UniqueId     : 0050430000000000
    ObjectId     : {df241dc4-c19f-11e1-bbf5-002590520253}
    BusType      : RAID
    FriendlyName : PhysicalDisk29
    UniqueId     : 0050430000000000
    ObjectId     : {df241cca-c19f-11e1-bbf5-002590520253}
    BusType      : RAID
    FriendlyName : PhysicalDisk33
    UniqueId     : 0050430000000000
    ObjectId     : {df241dcf-c19f-11e1-bbf5-002590520253}
    BusType      : RAID
    FriendlyName : PhysicalDisk30
    UniqueId     : 0050430000000000
    ObjectId     : {df241cd3-c19f-11e1-bbf5-002590520253}
    BusType      : RAID
    FriendlyName : PhysicalDisk2
    UniqueId     : 002800000040000037638531D4A17419
    ObjectId     : {7ab38df8-ab87-11e1-bbbd-806e6f6e6963}
    BusType      : Fibre Channel
    FriendlyName : PhysicalDisk3
    UniqueId     : 0028000000400000AB7400464090110C
    ObjectId     : {7ab38dfa-ab87-11e1-bbbd-806e6f6e6963}
    BusType      : Fibre Channel
    FriendlyName : PhysicalDisk1
    UniqueId     : IDE\DiskWDC_WD6400AAKS-00A7B2___________________01.03B01\4&180adc7b&0&0.1.0:Trounce-Server2
    ObjectId     : {7ab38dfc-ab87-11e1-bbbd-806e6f6e6963}
    BusType      : RAID
    FriendlyName : PhysicalDisk12
    UniqueId     : 00280000004000005396CC47AA8AD97B
    ObjectId     : {7ab38dfe-ab87-11e1-bbbd-806e6f6e6963}
    BusType      : Fibre Channel

  • I am receiving a notification that says that I am running out of storage space. I backed up time mating to an external hard drive. Can I delete some files to make room?

    I am receiving notifications that I am running out of storage space. I backed up my mac book using an external and time machine. Can I delete some files to make room?
    If so,
    When I want to restore from my time machine, can I pick and choose, say certain songs, photos or documents?

    About TM "Backup Drive is Full"
    Alert TM only deletes older files if they have been deleted from the source and when TM needs space on the backup drive for a new incremental backup. Time Machine "thins" it's backups; hourly backups over 24 hours old, except the first of the day; those "daily" backups over 30 days old, except the first of the week. The weeklies are kept as long as there's room.
    So, how long a backup file remains depends on how long it was on your Mac before being deleted, assuming you do at least one backup per day. If it was there for at least 24 hours, it will be kept for at least a month. If it was there for at least a week, it will be kept as long as there's room.
    Note, that on a Time Capsule the sparsebundle grows in size as needed, but doesn't shrink. Thus, from the user's view of the TC it appears that no space has been freed, although there may be space in the sparsebundle.
    Once TM has found it cannot free up enough space for a new backup it reports the disk is full. You can either erase the backup drive and start your backups anew or replace the drive with a larger drive. You can also use the Time Machine application to selectively remove files, but that may be ineffective if you have to free up GBs of space.

  • Repair-VirtualDisk on Storage Spaces simple volume with retired disk?

    Hello,
    Does anyone know if it's possible to retire a disk from a Storage Space simple volume, and use the Repair-VirtualDisk commandlet to migrate any data off the retired volume? It sounds like this is how it would work for a parity volume, but it's unclear if
    Windows will try to move data off a retired disk of a simple volume. Or is repair actually performing parity recovery?
    i.e. I want to replace disks in a simple volume with larger disks, and remove the old disks, is creating a new volume and migrating data the only way?
    Thank you!

    Hi,
    Simple spaces are not resilient to disk failures, so we cannot add a new physical disk to replace the failed physical disk.
    If you have backed up the files in that virtual disk, you could delete the disk then remove physical disks from the pool.
    For more detailed information, please see:
    Storage Spaces - Remove Physical Disk
    https://social.technet.microsoft.com/Forums/windowsserver/en-US/dbbf317b-80d2-4992-b5a9-20b83526a9c2/storage-spaces-remove-physical-disk?forum=winserver8gen
    Best Regards,
    Mandy 
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

  • Replacing a failed disk in storage space ! unable to remove a retired disk

    Hi Folks 
    Not really asking for much !! we are using windows 2012 R2 storage space ; one disk failed 
    and marked as retired. 
    today we received replacement disk ; added that to storage pool - fine. 
    then I repaired all Virtual Disk - process was very quick and went to 100% like a flash. 
    then I tried to remove faulty disk by using following commands :
    $DeadDisk=Get-PhysicalDisk -FriendlyName PhysicalDisk-1 
    FriendlyName        CanPool             OperationalStatus   HealthStatus        Usage                            
     Size
    PhysicalDisk-1      False               Lost Communication  Warning             Retired                        185.5
    GB
    Remove-PhysicalDisk -PhysicalDisks $deaddisk -StoragePoolFriendlyName storagePool
    this errored out ; basically saying that the above disk is still in-use ! 
    Any suggestions ? does repair job take some time ? it looked very fast ; when I did get-storagejob ; it showed 100 percent completed . 

    Hi,
    Please reboot the server then set the failed disk to "Retired" and remove the retired physical disk.
    You could refer to the thread below to troubleshoot the issue:
    Degraded Storage Spaces Storage Pool after single HDD failure
    http://social.technet.microsoft.com/Forums/en-US/3a7e2a7d-4ad7-48cc-8165-0d6673e37436/degraded-storage-spaces-storage-pool-after-single-hdd-failure
    Regards,
    Mandy
    If you have any feedback on our support, please click
    here .
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Storage Spaces - Remove Physical Disk from Simple layout

    I am running Server 2012 RTM with a single storage pool containing 4 drives - 2.73TB, 1.36TB, 465GB and 148GB. There is a single virtual disk created, with thin provisioning, using the Simple layout, with a current maximum size of 2.73TB, and with 1.32TB
    allocated. I want to remove the 148GB drive and replace it with a 465GB drive. When I right-click the 148GB disk and select Remove, I get a warning that Windows will attempt to rebuild any virtual disks that store data on the disk I'm trying to remove, and
    that in order to succeed, the storage pool must have enough free space to accommodate the data from the disk I'm trying to remove. There is more than enough space in the virtual disk to accommodate whatever files may be stored on the 148GB disk - over 1TB
    unallocated. However, when I confirm that I want to remove the disk from the pool, I get the following message:
    This physical disk is used by one or more virtual disks that use the Simple (no resiliency) layout. To remove this physical disk, delete the following virtual disks: Simple
    Surely the fact that it's a simple volume (rather than mirrored/parity) shouldn't affect the ability to move the data off the disk? It appears that disk removal is implemented as a simulated drive failure, forcing a rebuild of the resiliency data, rather
    than by simply moving the data off the disk onto other available disks.
    Additionally, after I've attempted to remove the disk, it's now been marked as 'Retired'.
    Is there any simple way to remove this disk?

    Same problem here, but I have some workaround for the problem.
    But, even in Windows Home Server with its awesome disk extender (predecessor of Storage Spaces) you had to take the shares (meaning volumes in our case) offline so you could take out the disk from the pool.
    Agree that it would make more sense to be able to remove disk from the pool online and the technology is most likely is already there: online cluster moves with defragmentation API was there for years and ReFS moves clusters online when it detects disk errors.
    Anyway here is the process that may work for you if taking volume offline is an option in your case:
    Try to remove physical disk in Server Manager - it will fail with abovementioned error, but the disk will go into "Retired" state.
    Now provision a new Virtual Disk and a volume of your choice. Most likely you will pick the same disk and volume type as you already had, but this is the chance to change the topology. You should be able to do this since you have a lot of physical disk
    space, especially if you used Thin provisioning.
    It looks like at this point retired physical disk is not included into the new Virtual Disk provisioning, but it is still accessible via existing virtual disk.
    Copy over all files from your old volume to a new volume.
    Now delete old Virtual Disk.
    If you want - change disk name and volume letter of new virtual disk that you created and new volume to what you had before.
    Now in Disk Manager take failing physical disk offline.
    Replace failing disk, initialize new disk and add it to the pool.
    Note: for me sometimes removing disk in via Storage Pool management GUI does not mark it as "Retired". In this case you can open PowerShell as Admin and assuming you want to remove PhysicalDisk2 - run the following command:
    Set-PhysicalDisk -FriendlyName PhysicalDisk2 -Usage Retired
    HTH

  • How to configure local disk on OVM Server as storage space to create VMs

    Hello,
    We have installed OVM Server 3.1.1 on a machine that has 250 GB of Hard disk space [Single disk].
    While installing used an option - Remove all partitions and create a new default partition layout.
    Around 4GB has been used and remaining 246 GB is left as free space.
    From OVM Manager - the server is discovered but didn't discovered the physical disk [i.e. remaining 246 GB raw disk space].
    Can someone help me to understand how to use local disk as storage space for creating and running VM's.
    Thanks
    Srinivas

    You can? You've used every conceivable BIOS out there? You must really be full of yourself. There is absolutely no BIOS that I know of that gives this basic function. BIOSs do not "hard partition" anything. A "BIOS" is not made for such things. Do you even know what "BIOS" stands for?
    I wonder why there is some many wanting to do this and are having problems.... I mean if it is such a straight forward thing to do..... It must be down right "intuitive".
    You maybe speaking of a RAID "BIOS" but you obviously think you're not. Some motherboards have integrated RAID abilities. Intel RST comes to mind... BUT this isn't a feature of a MOTHERBOARD BIOS.
    I've got some $50,000 servers that will not break a single hard drive up into multiple logical drives..... Now, I haven't worked on a "Stinkpad" for many years. Don't want to. However, I have never seen one that would do what you're saying you're doing.
    You maybe trying to help.... but you're leading people down a wrong path.
    Its just as easy to run virtual box and use the virtual box templates for Oracle VM. In fact, its more practical if you want to run Oracle VM on a laptop for testing purposes than blowing everything away and attempting to setup different LUNS on a single hard drive.
    For your review...
    http://www.oracle.com/technetwork/articles/servers-storage-admin/configure-vm-templates-1656261.html
    Although it's more reliable to use a separate location (such as an NFS share) for a storage repository, you can use a local disk of your Oracle VM Server instead, thus taking advantage of the local storage option. Beware, though: Oracle VM Server 3.0 doesn't allow you to utilize the unused space on the physical disk it's installed on. For local storage, you'll need at least one more physical disk. In other words, you'll need a total of two disks at minimum on your Oracle VM Server host if you want to use local storage. In practice, though, local storage is not a primary use case. The major downside to this approach is that local storage, by definition, cannot be shared between different servers.
    Edited by: user12273962 on Dec 10, 2012 10:40 AM

  • Removing disk from a volume storage space 2012 r2

    Hi, I've got a issue, here's my situation, i'm using storage space on a windows server 2012 R2 for my backups. Fisrt I had 14 3tb disk in mirror so there was 19tb usable for date. Now I needed more space so I just added 14 more disk and I extended the virtual
    disk to 38tb. Then when I wnet into windows management -> disk management to extend the partition to use the full 38tb, I got the following error message
    Virtual Disk Service error:
    The volume cannot be extended because the number of clusters will
    exceed the maximum number of clusters supported by the file system
    Then I realized that the cluster size where only at 8k, reading on the Web i understood that I couldn't get more then 32tb.
    Now I would like to remove all of the 14 disk I just added in the pool and create a new pool with 64Ko cluster size so I wont worry about my next size upgrade.
    I'm afraid that even if windows see the added space has a not allocated space, the storage pool is now using the disks. I can't afford to lose any data.
    How can I proceed??
    I saw procedure on this site but they seem's to be for removing 1 disk... since I have 14 disk fully integrated in my pool I am a bit nervous following a one disk procedure
    thank you

    Hi,
    As you have already added the 14 new disks into your existing pool, you will need to check if virtual disk is already extended onto these new physical disks. 
    If not, you should able to remove them from the pool - if virtual disk is already extended onto these new disks, It will ask for replacement to replace them with new hard disks. 
    If a part of hard disks could be removed, maybe you can migrate data onto these hard disks (no need to create a storage pool), delete the existing pool to recreate and migrate files back. 
    If you have any feedback on our support, please send to [email protected]

  • HT201364 Hello ! i have a question about my Hard's Disc storage space. I have Mac book Pro 11" Retina with hard disk 120 GB . I want to make this update but its impossible because of no free space. And now i want to ask. Its 120 GB full space but i dont k

    Hello ! i have a question about my Hard's Disc storage space. I have Mac book Pro 11" Retina with hard disk 120 GB . I want to make this update but its impossible because of no free space. And now i want to ask. Its 120 GB full space but i dont know how.  It tells me lets say i have 30 GB movies but i dont have anything ! Can you help me with any way ? If i can do something to see what movies let's say means !  
    Thank you !!

    Hope this helps.
    1. Empty Trash.
        http://support.apple.com/kb/PH10677
    2. Start up in Safe Mode
        http://support.apple.com/kb/PH11212
    3. Delete "Recovered Messages", if any.
        Hold the option key down and click "Go" menu in the Finder menu bar.
        Select "Library" from the dropdown.
        Library > Mail > V2 > Mailboxes
        Delete "Recovered Messages", if any.
        Empty Trash. Restart.
    4. Repair Disk
        Steps 1 through 7
        http://support.apple.com/kb/PH5836
    5. Disk space / Time Machine ?/ Local Snapshots
       http://support.apple.com/kb/ht4878
    6. Re-index Macintosh HD
       System Preferences > Spotlight > Privacy
       http://support.apple.com/kb/ht2409
    If this does not help, you have to buy an external HD and move your movies photos.etc to
    the external HD.

Maybe you are looking for