Windows OS Hub
  • Windows Server
    • Windows Server 2016
    • Windows Server 2012 R2
    • Windows Server 2012
    • Windows Server 2008 R2
    • SCCM
  • Active Directory
    • Group Policies
  • Windows Clients
    • Windows 10
    • Windows 8
    • Windows 7
    • MS Office
    • Outlook
  • Virtualization
    • VMWare
    • Hyper-V
  • PowerShell
  • Exchange
  • Home
  • About

Windows OS Hub

  • Windows Server
    • Windows Server 2016
    • Windows Server 2012 R2
    • Windows Server 2012
    • Windows Server 2008 R2
    • SCCM
  • Active Directory
    • Group Policies
  • Windows Clients
    • Windows 10
    • Windows 8
    • Windows 7
    • MS Office
    • Outlook
  • Virtualization
    • VMWare
    • Hyper-V
  • PowerShell
  • Exchange

 Windows OS Hub / Windows Server 2016 / Replacing a Failed Physical Disk in Storage Spaces Direct on Windows Server 2016

August 6, 2018 Windows Server 2016

Replacing a Failed Physical Disk in Storage Spaces Direct on Windows Server 2016

In the last article we told about a new technology of the distributed storage that appeared in Windows Server 2016 – Storage Spaces Direct (S2D). S2D allows to create a network failover distributed virtual data storage on the local disks of cluster servers (see the article). In this article, we’ll show you how to detect and replace a failed physical disk in an S2D cluster.

I remind you that in S2D you can create a Mirror type storage (similar to RAID 1): in a 2-disk configuration (not recommended), this storage can survive a failure of any disk, and if there are 3 or more disks in a pool, 2 disks may fail without any consequences. The second type of the array is Parity (similar to RAID 5). In the configuration consisting of three disks, an array can lose one disk without any consequences, if there are seven disks, 2 of them may fail at a time.

You can check the status of the storage subsystem of an S2D cluster using this command:

Get-StorageSubSystem *Cluster* | Get-StorageJob

You can find a fault with one of the disks in a storage pool using the GUI in the Failover Cluster Manager (Storage ->Storage Pool). As you can see, one of the physical disks in the pool is in the Unhealthy state.

s2d unhealthy failed drive on windows server 2016

You can get the information about the status of the disks in a pool using PowerShell:

Get-StoragePool *S2D* | Get-PhysicalDisk

StoragePool get failed drive

Save the object of the problem disk into a variable, for example, like this:

$Disk = Get-PhysicalDisk |? OperationalStatus -Notlike ok

Get-PhysicalDisk Notlike ok

Prevent further write attempts to this disk:

Set-PhysicalDisk -InputObject $Disk -Usage Retired

deny write to failed disk in Storage Spaces Direct (S2D) cluster

Try to remove the failed disk from the storage pool:

Get-StoragePool *S2D* | Remove-PhysicalDisk –PhysicalDisk $Disk

Soon a warning will appear that this device doesn’t respond.

To make it easier to identify a disk in a server rack, enable LED light of a disk:

Get-PhysicalDisk |? OperationalStatus -Notlike OK | Enable-PhysicalDiskIdentification

Note. Disk identification using LED light appeared in Windows Server 2016, but the support of SCSI Enclosure Storage (SES) is required on the side of a physical server.

Now go to the server room and find a problem disk using the backlight enabled earlier.

LED disk identifying with SES support

Replace a failed disk with a new one.

You can now turn off the backlight:

Get-PhysicalDisk |? OperationalStatus -like OK | Disable-PhysicalDiskIdentification

Make sure that the OS has detected the new disk:

$Disk = Get-PhysicalDisk | ? CanPool –eq True

detect a new disk in cluster

Note. In case of some low-end servers, you have to restart the server to identify the disk correctly.

Add the new disk to a pool:

Get-StoragePool *S2D* | Add-PhysicalDisk –PhysicalDisks $Disk –Verbose

add new disk to the storagepool

This is all, S2D will automatically start the data redistribution between the disks in a cluster (in Windows Server 2012 Storage Spaces, you had to run the command Repair-VirtualDisk manually). The synchronization time depends on the disk capacity and the pool load (it took about 30 minutes in my test stand). After that you can check the pool status again.

0 comment
1
Facebook Twitter Google + Pinterest
previous post
Fixing High CPU Usage and Memory Leak Issue by Svchost.exe (wuauserv)
next post
Windows XP Can’t RDP to Windows 10 / Server 2012R2/2016 RDS

Related Reading

How to Backup Hyper-V Virtual Machines?

December 10, 2019

How to Change a Network Location from Public...

December 9, 2019

Configuring Storage Replica on Windows Server 2016

December 4, 2019

How to Delete Old User Profiles Using GPO...

November 19, 2019

Using RDCMan (Remote Desktop Connection Manager)

November 11, 2019

Leave a Comment Cancel Reply

Categories

  • Active Directory
  • Group Policies
  • Exchange
  • Windows 10
  • Windows 8
  • Windows 7
  • Windows Server 2016
  • Windows Server 2012 R2
  • Windows Server 2008 R2
  • PowerShell
  • VMWare
  • MS Office

Follow us

woshub.com

Recent Posts

  • How to Backup Hyper-V Virtual Machines?

    December 10, 2019
  • How to Change a Network Location from Public to Private on Windows 10/Windows Server 2016?

    December 9, 2019
  • Configuring Storage Replica on Windows Server 2016

    December 4, 2019
  • Windows 10 Install Error 0x80300024

    December 2, 2019
  • Running PowerShell Script (*.PS1) as a Windows Service

    November 27, 2019
  • Creating Multiple Partitions on a USB Drive in Windows 10

    November 26, 2019
  • VMWare vSphere: Failed to Upload Files to Datastore

    November 21, 2019
  • How to Delete Old User Profiles Using GPO and PowerShell?

    November 19, 2019
  • Get-ADUser: Getting Active Directory Users Info via Powershell

    November 18, 2019
  • How to Recover Deleted Files from a TRIM-Enabled SSD?

    November 14, 2019
  • Facebook
  • Twitter
  • RSS
Popular Posts
  • Updating List of Trusted Root Certificates in Windows 10/8.1/7
  • Installing SFTP (SSH FTP) Server on Windows with OpenSSH
  • Licensing Mode for Remote Desktop Session Host is not Configured
  • How to Upgrade Windows Server 2019/2016 Evaluation to Full Version?
  • SMB 1.0 Support in Windows Server 2012 R2 / Windows Server 2016
  • User Profile Disks on Windows Server 2012 R2 / 2016 RDS
  • Managing Printers and Drivers with PowerShell in Windows 10 / Server 2016
Footer Logo

@2014 - 2018 - Windows OS Hub. All about operating systems for sysadmins


Back To Top