DL380 Gen10 / secondary Logical Drive Not Visible in OS (after windows server install)

[zenny6377]

Hi - I've configured a DL380 Gen 10 with 2 drive cages and 16 drives (P408i controller).  The initial install only utilized the primary drive cage for the OS (Windows server 2016)  I then installed the HP SAS expander, a second drive cage and 8 more HP branded 1.2TB drives.  In system utilities I'm able to see all the 8 new drives and I tried configuring a single RAID 6 array (created a logical volume) an also 2 smaller RAID 6 arrays of 4 drives each (with 2 logical volumes).  In both cases the volumes are not visible in windows in disk management or powershell.   The controller drivers are obviously installed since that was done during OS install (and the controller appears in device manager)  All drives are green and healthy, no errors during boot.  I also tried moving the secondary drive cage to different ports on the SAS expander, that doesn't affect seeing drives/creating logical volumes, it only affects the drive numbering (the drive IDs) in disk utilities during boot.

[support_s · Accepted solution]

System recommended content:

1. HPE ProLaint DL380 Gen10 Server Trusted Maintenance and Service Guide

2. HPE ProLiant DL380 Gen10 Server Trusted User Guide

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".

Thank you for being a HPE valuable community member.

[zenny6377]

Just in case anyone else had this issue - I was running storage spaces direct (S2D) under Windows Server 2016 which automatically "claims" any disks that are added to the system including RAID arrays (even though RAID arrays are not supported or usable by S2D.  I wanted to use this secondary RAID array for simple backups and not have it participate in S2D.  Since the RAID array I created after the OS was installed was grabbed by S2D I couldn't see it in disk management.  I had to do the following to gain access and format it (Powershell below)

get the unique id of the array in question:

get-storagepool -friendlyname <name of pool> |get-physicaldisk |ft friendlyname,canpool,size,serialnumber,operationalstatus,size,uniqueid

Set the volume to "Retired"

set-physicaldisk -uniqueid <uniqueId from previous step> -Usage Retired

Repair the cluster storage volume (this can take a long time)

Repair-VirtualDisk -FriendlyName <Name of CSV>  /* returned via Get-VirtualDisk */

After this step, the disk will appear in the "Primordial Pool" and has to be unclaimed:

Set-ClusterStorageSpacesDirectDisk -CanBeClaimed $false -PhysicalDiskids (<disk id>)

After this last step the disk appeared in disk management and I was able to use it normally as a local disk.

[Sunitha_Mod]

Hello @zenny6377

That's excellent!

We're delighted to hear that you managed to discover the solution, and we're grateful for you taking the time to share it with us.