Fixed SSD Journal Disks Lost Communication Issues at Storage Space Direct Server

I was doing daily checking for servers as usual. There are two SSD drives happen lost communication at Storage Space Direct Server, this is not good, because those two SSD drives are the cache of Storage Space Direct.

We need to replace those SSD drives after discussed with support Engineer of Server hardware Vendor. Today, I am going to show you how to step by step to replace SSD Journal disks.

1. Open Windows PowerShell, type follow PowerShell cmdlet to check the serial number of Journal Disks.

   
   
   Get-PhysicalDisk
   
   
   
   

2. Type follow PowerShell cmdlet to set the variable for the Lost Communication SSD’s (if you are using S2D cluster, don’t do both at the same time)

   
   
   $PD1 = Get-physicalDisk -SerialNumber "PHYF8335030T1P9DGN"
   
   
   $PD2 = Get-physicalDisk -SerialNumber "PHYF833502SC1P9DGN"
   
   
   
   

3. Type follow PowerShell cmdlet to retire the Lost Communication Drives (if you are using S2D cluster, don’t do both at the same time).

   
   
   Set-PhysicalDisk -inputobject $PD1 -usage retired
   
   
   Set-PhysicalDisk -inputobject $PD2 -usage retired
   
   
   
   

4. Type follow PowerShell cmdlet to make sure SSDs Usage status are Retired.

   
   
   Get-PhysicalDisk
   
   
   
   

5. Physically remove the 2 Retired Drives from Server Chassis and Replace with the new ones.
6. Type follow PowerShell cmdlet to make sure the new SSDs show up as CanPool True.

   
   
   Get-PhysicalDisk -CanPool $true
   
   
   
   

7. Type follow PowerShell cmdlet to add those two new drives as Journal of the storage pool.

   
   
   $PDAdd = Get-physicalDisk -CanPool $true
   
   
    Add-PhysicalDisk -StoragePoolFriendlyName TitanSP01 -PhysicalDisks $PDAdd -Usage Journal
   
   
   
   

8. Use follow PowerShell cmdlet to check the Journal Configuration was Successful.

   
   
   Get-PhysicalDisk | Sort-Object -Property Usage
   
   
   
   

9. On the Server Manage Storage Pools page, select and right-click the lost communication SSDs, select Remove Disk to remove the Retired Drives from the Storage Pool.

   

10. Click Yes on the warning message.

    

11. Click OK on the recommend page.

    

12. On the Server Manager Storage Pools page, the Physical Disks maybe not update right away.

    

13. Use follow PowerShell cmdlet to force update.

    
    
    Update-StorageProviderCache -DiscoverLevel full
    
    
    
    

14. Everything should up and running and back to normal now.

    

Hope you enjoy this post.

Cary Sun

Twitter: @SifuSun

Author: Cary Sun

Cary Sun has a wealth of knowledge and expertise in data center and deployment solutions. As a Principal Consultant, he likely works closely with clients to help them design, implement, and manage their data center infrastructure and deployment strategies.
With his background in data center solutions, Cary Sun may have experience in server and storage virtualization, network design and optimization, backup and disaster recovery planning, and security and compliance management. He holds CISCO CERTIFIED INTERNETWORK EXPERT (CCIE No.4531) from 1999. Cary is also a Microsoft Most Valuable Professional (MVP), Microsoft Azure MVP, Veeam Vanguard and Cisco Champion. He is a published author with several titles, including blogs on Checkyourlogs.net, and the author of many books.
Cary is a very active blogger at checkyourlogs.net and is permanently available online for questions from the community. His passion for technology is contagious, improving everyone around him at what they do.

Blog site: https://www.checkyourlogs.net
Web site: https://carysun.com
Blog site: https://gooddealmart.com
Twitter: @SifuSun
in: https://www.linkedin.com/in/sifusun/
Amazon Author: https://Amazon.com/author/carysun