none
Clustered Storage space degraded and SSD disks "starting"

    Question

  • I've got a really strange problem with a storage space that was working perfectly for about 6 weeks.

    Config summary;
    Two server cluster with LSI SAS controllers
    MPIO SAS backplane on SAS enclosure.
    4 x SAS HDDs
    2x SAS SSDs

    One storage space configured which had been working very well until last week when the two SSDs reported as a warning state, and were stuck "starting".

    get-physicaldisk | FT
    
    FriendlyName        CanPool             OperationalStatus   HealthStatus        Usage                              Size
    ------------        -------             -----------------   ------------        -----                              ----
    PhysicalDisk0       False               OK                  Healthy             Auto-Select                    67.75 GB
    PhysicalDisk1       False               OK                  Healthy             Auto-Select                   930.75 GB
    PhysicalDisk5       False               Starting            Unknown             Auto-Select                     92.5 GB
    PhysicalDisk2       False               OK                  Healthy             Auto-Select                   930.75 GB
    PhysicalDisk4       False               OK                  Healthy             Auto-Select                   930.75 GB
    PhysicalDisk3       False               OK                  Healthy             Auto-Select                   930.75 GB
    PhysicalDisk6       False               Starting            Unknown             Auto-Select                     92.5 GB

    Now, any VDisks configured to use WB Cache with Tiering with the two SSDs are failed.

    Now, the LSI controller reports all the disk are fine, and are operational.

    Device Manger reports the disk as MPIO enabled, and running fine.

     

    Before I send you off on a tangent - is this because I don't have the minimum 4 disks for SSD tiering - as a clustered storage space needs a minimum of 4 disks for a mirror? http://technet.microsoft.com/en-us/library/dn387076.aspx#bkmk_tiers

    Thanks all!

    Monday, December 30, 2013 8:59 AM

All replies

  • Hi,

    Please run this cmdlet in PowerShell and let us know the result:

    Get-VirtualDisk | ft FriendlyName, ResiliencySettingName, NumberOfColumns, NumberOfDatacopies

    If column = 2 and datacopy = 2, you should have 4 SSD instead of 2 as you said for WB cache.


    If you have any feedback on our support, please send to tnfsl@microsoft.com.

    Wednesday, January 01, 2014 6:08 AM
    Moderator
  • Hey mate - yep - understood that one.

    I had manually configured the VDisks with 1 column, resiliency setting as mirror...

    Get-StoragePool Pool1 | New-StorageTier –FriendlyName SSDTier –MediaType SSD
    Get-StoragePool Pool1 | New-StorageTier –FriendlyName HDDTier –MediaType HDD
    
    
    Get-StoragePool Pool1 | Set-ResiliencySetting -Name Mirror -NumberOfColumnsDefault 1
    
    $SSD = Get-StorageTier -FriendlyName SSDTier
    $HDD = Get-StorageTier -FriendlyName HDDTier
    
    Get-StoragePool Pool1 | New-VirtualDisk -FriendlyName VMStorage1 -ResiliencySettingName Mirror -StorageTiers $SSD, $HDD -StorageTierSizes 20GB, 200GB -WriteCacheSize 1GB
    Get-StoragePool Pool1 | New-VirtualDisk -FriendlyName VMStorage2 -ResiliencySettingName Mirror -StorageTiers $SSD, $HDD -StorageTierSizes 20GB, 200GB –WriteCacheSize 1GB
    

    Wednesday, January 01, 2014 11:36 AM
  • Ok quick update on what's happening;

    Remove the Pool - after about 2-3 reboots of each node between removing the individual failed volumes (really strange behaviour).

    Started again.

    Built my new Pool1 and created the tiers (as in the last post).

    Get-PhysicalDisk | Sort Size | FT  -AutoSize
    
    FriendlyName  CanPool OperationalStatus HealthStatus Usage            Size
    ------------  ------- ----------------- ------------ -----            ----
    PhysicalDisk0 False   OK                Healthy      Auto-Select  67.75 GB
    PhysicalDisk6 False   OK                Healthy      Auto-Select   92.5 GB
    PhysicalDisk5 False   OK                Healthy      Auto-Select   92.5 GB
    PhysicalDisk3 False   OK                Healthy      Auto-Select 930.75 GB
    PhysicalDisk2 False   OK                Healthy      Auto-Select 930.75 GB
    PhysicalDisk1 False   OK                Healthy      Auto-Select 930.75 GB
    PhysicalDisk4 False   OK                Healthy      Auto-Select 930.75 GB

    Everything working OK.

    Get-VirtualDisk | FT -AutoSize
    
    FriendlyName ResiliencySettingName OperationalStatus HealthStatus IsManualAttach   Size
    ------------ --------------------- ----------------- ------------ --------------   ----
    VMStorage2   Mirror                OK                Healthy      True           220 GB
    VMStorage1   Mirror                OK                Healthy      True           220 GB

    Created the volume OK;

    Get-VirtualDisk VMStorage1 | Get-Disk | Set-Disk -IsReadOnly 0
    Get-VirtualDisk VMStorage1 | Get-Disk | Set-Disk -IsOffline 0
    Get-VirtualDisk VMStorage1 | Get-Disk | Initialize-Disk -PartitionStyle GPT
    Get-VirtualDisk VMStorage1 | Get-Disk | New-Partition -UseMaximumSize 
    
    Get-VirtualDisk VMStorage2 | Get-Disk | Set-Disk -IsReadOnly 0
    Get-VirtualDisk VMStorage2 | Get-Disk | Set-Disk -IsOffline 0
    Get-VirtualDisk VMStorage2 | Get-Disk | Initialize-Disk -PartitionStyle GPT
    Get-VirtualDisk VMStorage2 | Get-Disk | New-Partition -UseMaximumSize 
    

    Then - failure occurs;

    Get-VirtualDisk | FT -AutoSize
    
    FriendlyName ResiliencySettingName OperationalStatus HealthStatus IsManualAttach   Size
    ------------ --------------------- ----------------- ------------ --------------   ----
    VMStorage2   Mirror                Degraded          Warning      True           220 GB
    VMStorage1   Mirror                Degraded          Warning      True           220 GB
    
    
    
    Get-PhysicalDisk | Sort Size | FT
    
    FriendlyName        CanPool             OperationalStatus   HealthStatus        Usage                              Size
    ------------        -------             -----------------   ------------        -----                              ----
    PhysicalDisk0       False               OK                  Healthy             Auto-Select                    67.75 GB
    PhysicalDisk6       False               Starting            Unknown             Auto-Select                     92.5 GB
    PhysicalDisk5       False               Starting            Unknown             Auto-Select                     92.5 GB
    PhysicalDisk3       False               OK                  Healthy             Auto-Select                   930.75 GB
    PhysicalDisk2       False               OK                  Healthy             Auto-Select                   930.75 GB
    PhysicalDisk1       False               OK                  Healthy             Auto-Select                   930.75 GB
    PhysicalDisk4       False               OK                  Healthy             Auto-Select                   930.75 GB

    What the heck! My two SSDs go into "starting" mode...

    PS C:\Users\administrator.SERVICE> Get-PhysicalDisk | Sort Size | FT  -AutoSize
    
    FriendlyName  CanPool OperationalStatus HealthStatus Usage            Size
    ------------  ------- ----------------- ------------ -----            ----
    PhysicalDisk0 False   OK                Healthy      Auto-Select  67.75 GB
    PhysicalDisk6 False   Starting          Unknown      Auto-Select   92.5 GB
    PhysicalDisk5 False   Starting          Unknown      Auto-Select   92.5 GB
    PhysicalDisk3 False   OK                Healthy      Auto-Select 930.75 GB
    PhysicalDisk2 False   OK                Healthy      Auto-Select 930.75 GB
    PhysicalDisk1 False   OK                Healthy      Auto-Select 930.75 GB
    PhysicalDisk4 False   OK                Healthy      Auto-Select 930.75 GB

    Wednesday, January 01, 2014 11:13 PM
  • Hi Matthew,

    Have you figured what caused the issue ? I am seeing the same problem on a similar configuration.

    Failover cluster, LSI SAS controller

    4 x SAS HDDs (279 Gb)
    2x SAS SSDs(92.5 Gb)

    Have tried with and without MPIO with the same result, a tiered volume will fail after a few days, with SSDs stuck in "starting" state, and reboots required to eventually reattach the virtual disk.

    Could it be a compatibility issue ? SSDs are seagate model ST100FM0002

    will update here if I figure it out

    cheers,

    alex

    Monday, February 03, 2014 10:07 AM
  • Hi Guys,

    maybe this is an Seagate Issue. I am seeing the same in an Customer enviroment. They have the Seagate SAS SSD ST200FM0053. Ceep you informed.


    Grüße/Regards Carsten Rachfahl | MVP Virtual Machine | MCT | MCITP | MCSA | CCA | Husband and Papa | www.hyper-v-server.de | First German Gold Virtualisation Kompetenz Partner ---- If my answer is helpful please mark it as answer or press the green arrow.

    Monday, February 03, 2014 6:20 PM
  • Hey guys,

    Issue still unresolved. Have taken the drives out of the pool, and have dropped back to the 4 NLSAS 7200RPM disks - complete rebuild of the storage space :(.

    I'd say it's one of two things;

    1. Minimum of 4 SSDs are required to match my existing 4 NLSAS HDDs
    2. Genuine firmware/compat issue - But I wouldn't even know how to start to diagnose ....

    If you guys want to compare logs, let me know what you need - I can supply.

    Cheers.

    Monday, February 03, 2014 10:52 PM
  • He Matthew,

    I'm pretty sure it is not the number of the SSDs. They don't have to match the NLSSAS HDDs. It is nice for your column count if you have a lot of SSDs but it is not necessary (you need only two if you wand to mirror).

    I bet on the Firmware.


    Grüße/Regards Carsten Rachfahl | MVP Virtual Machine | MCT | MCITP | MCSA | CCA | Husband and Papa | www.hyper-v-server.de | First German Gold Virtualisation Kompetenz Partner ---- If my answer is helpful please mark it as answer or press the green arrow.

    Monday, February 03, 2014 10:59 PM
  • Hi Carsten - did you ever resolve this for your customer? I still haven't been able to rebuilt this with the SSD tier...

    I might have to contact MS professional services on this.

    Saturday, April 19, 2014 7:11 AM
  • Yes we at least know the problem and a workarround. It seams that the Seagate SSDs have a Problem when certain hotfixes are installed. Seagate is award of that and is working on a fix. So we hope that Firmware 0005 will solve this issue. In the meantime you can look if you have one of the following patches installed: KB2903939, KB2913766 or Windows Server 2012 R2 Update 1. If so remote them and wait for the new Seagate Firmware.

    Grüße/Regards Carsten Rachfahl | MVP Virtual Machine | MCT | MCITP | MCSA | CCA | Husband and Papa | www.hyper-v-server.de | First German Gold Virtualisation Kompetenz Partner ---- If my answer is helpful please mark it as answer or press the green arrow.


    Saturday, April 19, 2014 10:48 AM
  • Ah thanks Carsten.

    I have KB2903939 installed, but not KB2913766. Definitely not Update 1.

    Cheers.
    Saturday, April 19, 2014 11:44 AM
  • Do you know if Seagate has a new firmware in beta yet or anything? I put a ticket with them and they claim they don't know and it should work as expected. Also its a Microsoft problem they are proposing...
    Saturday, May 31, 2014 12:21 AM
  • Yes Seagate has a new Firmware that fixes the problem.

    Grüße/Regards Carsten Rachfahl | MVP Virtual Machine | MCT | MCITP | MCSA | CCA | Husband and Papa | www.hyper-v-server.de | First German Gold Virtualisation Kompetenz Partner ---- If my answer is helpful please mark it as answer or press the green arrow.

    Wednesday, June 04, 2014 5:39 AM
  • Thanks for the reply Carsten. So your customer was using the ST200FM0053 Seagate SSD right? I'm using ST200FM0073 which should be the same firmware you'd think. I used the serial number off this review http://www.storagereview.com/seagate_1200_enterprise_ssd_review which is the 400GB version of 0053 and it's still 0004 as well. Did they by chance get the update via Seagate support? The support people I keep getting in Seagate tell me they have no insight what development is doing and if there is any newer firmware in the pipe. Maybe could you get the firmware uploaded somewhere please :-D from what I'm seeing is it should work based on the 0004 guides. If not no biggie...

    Thanks again for your response.

                             
    Thursday, June 05, 2014 7:47 PM
  • The Firmware Version is: 0A04 as you can see in the screenshot.

    

    Grüße/Regards Carsten Rachfahl | MVP Virtual Machine | MCT | MCITP | MCSA | CCA | Husband and Papa | www.hyper-v-server.de | First German Gold Virtualisation Kompetenz Partner ---- If my answer is helpful please mark it as answer or press the green arrow.

    Thursday, June 05, 2014 10:27 PM
  • Carsten I hate to bug ya again. So talked on the phone with Seagate and they went through engineering and development and said that firmware does not exist. It does not follow there naming scheme the firmware version on the server 2012 r2 certified hardware is Microsoft and email them about the firmware as it may be 3rd party. Do your people happen to have contact? Or maybe are they using dell disks or some other OEM? Thanks again for your help.
    Friday, June 06, 2014 10:48 PM
  • No OEM, no Dell, no nothing. I'm working in a big Datacenter Project where the customer is also a Seagate Distributor and has a lot of Seagate 1200 SSDs. Over the envolvment of the Project we found some flaws in the SSDs and Seagate developed solutions for them that where manifested in the Releases of the different Firmware Versions (0001, 0002, 0003, 0004, 0A04). So this Firmware was give to the customer through seagate. And it is official certified in the Microsoft Server Catalog. Tell the seagate Folks they have to look!

    Cheers Carsten

    

    Grüße/Regards Carsten Rachfahl | MVP Virtual Machine | MCT | MCITP | MCSA | CCA | Husband and Papa | www.hyper-v-server.de | First German Gold Virtualisation Kompetenz Partner ---- If my answer is helpful please mark it as answer or press the green arrow.

    Sunday, June 08, 2014 7:19 AM
  • Hmm I wonder if one of there German teams worked on it within Seagate. Assuming you and your customer are German of course. I opened a new case with them asking to either create a new firmware as I think it has to do with Storage Spaces persistent reservation. Or dig deeper and maybe ask other teams globally as we are not the only people setting this up with there drives.

    Thanks for the help Carsten!

    Sunday, June 08, 2014 2:44 PM
  • No the firmware is from the US! As stated in the Microsoft Windows Server Catalog this is the last tested release on this SSDs! We have it but we are not allowed to share! So keep asking them and tell them that it is there.


    Grüße/Regards Carsten Rachfahl | MVP Virtual Machine | MCT | MCITP | MCSA | CCA | Husband and Papa | www.hyper-v-server.de | First German Gold Virtualisation Kompetenz Partner ---- If my answer is helpful please mark it as answer or press the green arrow.

    Sunday, June 08, 2014 2:53 PM
  • This firmware is as easy to get hold of as the holy grail (0A04 that is). I can't get in contact with anyone at Seagate who can get hold of it.

    Do you have any pointer to how I can get a hold of it?

    Thursday, June 12, 2014 8:12 AM
  • Try to get an Contact vor you. Pleas sen me a mail with your contact Information at c.Rachfahl(at)Rachfahl.de

    Grüße/Regards Carsten Rachfahl | MVP Virtual Machine | MCT | MCITP | MCSA | CCA | Husband and Papa | www.hyper-v-server.de | First German Gold Virtualisation Kompetenz Partner ---- If my answer is helpful please mark it as answer or press the green arrow.

    Thursday, June 12, 2014 8:32 AM
  • I have the exactly same problem with my ST200FM0053 discs. I am currently looking for a firmware update aswell. I made a case with Seagate to see if i can get them that was and i also pointed out that they are certified in their catalog hoping they will be more willing to give me them.

    Monday, June 16, 2014 1:22 PM
  • I also have the exact same problem with 4 ST200FM0053 drives. I made the case with Seagate, and pointed them to this topic and the windows server catalog. I'll hope for the best!
    Monday, June 16, 2014 11:22 PM
  • Same issue here with four ST400FM0053 drives on firmware 0004.  Opened a support case with Seagate today and pointed them to this thread as well as the Windows server catalog listing firmware 0A04.  Let's hope they release it.  I'm on 2012R2 update 1.
    • Proposed as answer by tbiggins Tuesday, June 17, 2014 1:56 PM
    • Unproposed as answer by tbiggins Tuesday, June 17, 2014 1:56 PM
    Tuesday, June 17, 2014 1:34 PM
  • Seagate has provided the firmware!!!  I haven't installed/tested - but here's the text of their email.

    -----------------------------------------------------

    Thank you for contacting Seagate Support.

    After an exhaustive search we were able to locate the source of this firmware and now have it available for customers. I am attaching it to this email.

    For additional assistance, feel free to contact us at: www.seagate.com/about/contact-us/technical-support/

    -----------------------------------------------------

    Quick turn around - I only opened the case this morning.   Good luck to all of you.

    Tuesday, June 17, 2014 1:58 PM
  • The Firmware 0A04 is an interim Version. The official firmware is 0005 and should be availible the next days/weeks. So install 0A04 only if it is absolute necessary otherwise wait for 0005.


    Grüße/Regards Carsten Rachfahl | MVP Virtual Machine | MCT | MCITP | MCSA | CCA | Husband and Papa | www.hyper-v-server.de | First German Gold Virtualisation Kompetenz Partner ---- If my answer is helpful please mark it as answer or press the green arrow.

    Tuesday, June 17, 2014 3:19 PM
  • Seagate has provided the firmware to me too via a google docs link. I know that it's an interim release, but im gonna test and put it in production anyway. Clustered storage spaces is virtually useless without this bug fixed; one of my fileservers even gave a BSOD as a result. I'll keep an eye out for version 0005, thanks for the heads up Carsten.
    Wednesday, June 18, 2014 8:34 AM
  • I also got the firmware from support. I have flashed and tested and it seems to work fine now. No errors till now. :)
    Wednesday, June 18, 2014 2:17 PM
  • Thanks for letting me know it's interim only.  I was unable to update the firmware with the cluster and MPIO enabled.  I had to destroy the cluster, remove MPIO, and then have only one SAS cable to the JBOD to udpate the firmware.  If anyone has another method that works - can you please post it here - I would greatly appreciate it.
    Wednesday, June 18, 2014 7:59 PM
  • I had some issues updating under windows too, so I used an ubuntu live CD on one of my cluster nodes. I took the storage pool offline and updated the firmware from another server connected to the same JBOD enclosure. The storage pool came online without a problem after the firmware update was finished.


    • Edited by joerimul Wednesday, June 18, 2014 11:27 PM
    Wednesday, June 18, 2014 11:26 PM
  • Hi guys, We do the update usaly this Way: 1. Standalone Scenario: only use one Connection to The JBODS (means if you have MPIO unplug the cables unless only one cable is left to every JBOD from The Server) 2. in a Failover Cluster Scenario: shutdown all Servers exzept one and then go like the Standalone Szenario. Warnimg: if you update from a Firmware before 0004 you should not turn off The SSDs and use them for a while.

    Grüße/Regards Carsten Rachfahl | MVP Virtual Machine | MCT | MCITP | MCSA | CCA | Husband and Papa | www.hyper-v-server.de | First German Gold Virtualisation Kompetenz Partner ---- If my answer is helpful please mark it as answer or press the green arrow.

    Thursday, June 19, 2014 6:52 AM
  • I ended up using a 2008 R2 bootable image with my HBA driver to flash my SSD's. That way I didn't have to get to crazy with tearing down things.
    Wednesday, June 25, 2014 5:02 AM
  • Thanks for the heads up Carsten. You have been quite a good resource on this.

    Wednesday, June 25, 2014 5:04 AM
  • Blogged the issue and process to obtain the firmware here: CRITICAL: Seagate 1200 SSD Firmware Update Required for 2012 R2 Storage Spaces

    We are just in the process of bringing down the cluster, shutting down all nodes but one, and flashing the SSDs.

    Hopefully all goes well. :)


    Philip Elder Microsoft Cluster MVP Blog: http://blog.mpecsinc.ca

    Thursday, June 26, 2014 9:01 PM
  • Hay Matthew,

    Did you ever find a fix for this issue? I have the same drives and same issue. I have removed the SSD's from the pool and now everything is ok but no SSD tier. I called seagate and was told no firmware update available for this drive. I have 6 of them just going to waste. Let me know.

    Thanks,

    Rodney

    Thursday, September 17, 2015 10:26 PM
  • Hey Rodney,

    the issue is the firmware. You have to have at least version 0005 (the actual one is 0007). Please read the rest of the post.


    Grüße/Regards Carsten Rachfahl | MVP Virtual Machine | MCT | MCITP | MCSA | CCA | Husband and Papa | www.hyper-v-server.de | First German Gold Virtualisation Kompetenz Partner ---- If my answer is helpful please mark it as answer or press the green arrow.

    Friday, September 18, 2015 6:41 AM
  • Hey Rodney,

    the issue is the firmware. You have to have at least version 0005 (the actual one is 0007). Please read the rest of the post.


    Grüße/Regards Carsten Rachfahl | MVP Virtual Machine | MCT | MCITP | MCSA | CCA | Husband and Papa | www.hyper-v-server.de | First German Gold Virtualisation Kompetenz Partner ---- If my answer is helpful please mark it as answer or press the green arrow.

    As I recall there are still issues even with the newest firmware. UNMAP/TRIM in a Storage Spaces setting.

    We had a set go into a Quanta enclosure and after the firmware update we still experienced issues. We dropped Seagate SAS SSDs after that and will stick with HGST. That's not a fix for the problems obviously, but IMNSHO somewhere along the lines these drives should never have been put on the Storage Spaces approved list. That's what bit us with the prior to 0005 firmware.


    Philip Elder Microsoft Cluster MVP Blog: http://blog.mpecsinc.ca

    Monday, September 21, 2015 5:27 PM
  • Carsten,

    Thank you for replying. I did read the entire post. The reason I asked Matthew was that he is using the same drives as me, the ST100FM0002. This thread kind of ran off onto other drives that are running later firmware. I spoke with seagate and was told that I am on the current firmware for this drive D003. And was told that there are no newer versions. When I asked about the 0005 I was told that it is not for this drive.

    Thanks,

    Rodney

    Monday, September 21, 2015 7:50 PM
  • I would assume that the pulsars were never supported. I never saw Matthew get an "ok" its fixed with the 0005 update for his Pulsars. Most of the references I can find are for the 1200 series instead. Which I struggled with on my 1200 series drives to get the firmware. Which later I got the beta firmware and they did release 0005 for my 1200 series SSD drive. If you look here the pulsar doesn't have 2012 support.

    Sorry mate.



    Wednesday, September 23, 2015 6:49 AM
  • Thanks Adam,

    So anyone want to buy 6 ST100FM0002 Pulsar SAS SSD's? I would like to say this will be the last Seagate product I ever buy. I will at least try to find another drive producer before spending any more with Seagate.

    Wednesday, September 23, 2015 9:29 PM
  • So I might have found a solution to this, and I wanted to post it for the other people who may google this issue.

    Get-PhysicalDisk

    Clear-Disk

    Reset-PhysicalDisk

    My issue was 3xWD Red NAS 3TB drives wouldn't move from one install of Windows to a new one on the same PC.

    My process was to look at the drives in a second machine, using a "stupid" SATA III to USB 3.0 interface. When I did, the disk didn't show up in explorer, but I did find it in disk management, with a partition size of ... 16TB. Dunno what happened, but it was borked. I spent the next 20 minutes trying to delete the partition, with little success. I then looked to powershell - I literally just started a course on it, and my boss had huge praise for it, so I said "Why not!" - Here are the results, with Serials omitted.

    PS C:\WINDOWS\system32> Get-PhysicalDisk
    
    FriendlyName            SerialNumber   MediaType   CanPool OperationalStatus HealthStatus Usage         Size
    ------------            ------------   ---------   ------- ----------------- ------------ -----         ----
    WDC WD30 EFRX-REDACTED  REDACTED       Unspecified False   OK                Healthy      Auto-Select   2.73 TB

    Finding the partitions:

    PS C:\WINDOWS\system32> Get-Partition
    
       DiskPath:
    \\?\usbstor#disk&ven_wdc_wd30&REDACTED&rev_82.0#REDACTED#{REDACTED}
    
    PartitionNumber  DriveLetter Offset             Size Type
    ---------------  ----------- ------             ---- ----
    1                            4096               16 TB Unknown

    Note the crazy size.

    PS C:\WINDOWS\system32> Get-Disk
    
    Number Friendly Name            Serial Number           HealthStatus         OperationalStatus      Total Size Partition
                                                                                                                                                                    Style
    ------ -------------            -------------           ------------         -----------------      ---------- ----------
    5      WDC WD30 EFRX-REDACTED   REDACTED                Healthy              Online                    2.73 TB MBR
    

    Then to Clear it:

    PS C:\WINDOWS\system32> Clear-Disk
    
    cmdlet Clear-Disk at command pipeline position 1
    Supply values for the following parameters:
    Number[0]: 5
    Number[1]:
    
    Confirm
    Are you sure you want to perform this action?
    This will erase all data on disk 5 "WDC WD30 EFRX-REDACTED".
    [Y] Yes  [A] Yes to All  [N] No  [L] No to All  [S] Suspend  [?] Help (default is "Y"): Y

    Then Reset and Check!

    PS C:\WINDOWS\system32> Reset-PhysicalDisk
    
    cmdlet Reset-PhysicalDisk at command pipeline position 1
    Supply values for the following parameters:
    FriendlyName: WDC WD30 EFRX-REDACTED
    PS C:\WINDOWS\system32> Get-PhysicalDisk
    
    FriendlyName              SerialNumber MediaType   CanPool OperationalStatus HealthStatus Usage         Size
    ------------              ------------ ---------   ------- ----------------- ------------ -----         ----
    WDC WD30 EFRX-REDACTED    REDACTED     Unspecified True    OK                Healthy      Auto-Select   2.73 TB

    IT WAS SERIOUSLY ANNOYING.

    Microsoft, please make a "Force Destroy" Option for disk storage spaces.

    • Proposed as answer by Felix_the_Fox Saturday, December 09, 2017 4:37 AM
    Saturday, December 09, 2017 4:34 AM