Forum Discussion
Solved
MSLab Azure Stack HCI: Waiting until SBL Disks are surfaced.
Hi everyone, Still trying to get an Azure Stack HCI Lab run on my rig. Came far thanks to MSLabs and sorts. Scenario: Azure Stack HCI 22N2 using nested virtualization. Parent OS Windows ...
- after the error from the cluster validation, I believe this would be the thing to replace the disks. ChatGPT found the same.
https://www.thewindowsclub.com/disk-signature-collision-problem
tried to start over and use Server Manager or Cluster Mgmt to create a pool.
Same issue only 4 of 8 are added to the pool. different errors though
Cluster Check (Legacy)
The device identifier '60022480E59430916B97D170A1372CA6' matches multiple disks on node(s) vazhci02-22h22n.onprem.chynet.de, vazhci01-22h22n.onprem.chynet.de. The disk identifier is not unique. The hardware is not compatible with Storage Spaces Direct (S2D). Contact the hardware vendor to verify support for Device Identification VPD page 83h SCSI inquiry data.
PowerShell
Drives now listed as "Starting".
after the error from the cluster validation, I believe this would be the thing to replace the disks. ChatGPT found the same.
https://www.thewindowsclub.com/disk-signature-collision-problem
https://www.thewindowsclub.com/disk-signature-collision-problem