Hello Luis Antonio Orellana Barre,
Welcome to the Microsoft Q&A and thank you for posting your questions here.
Problem
Sequel to your questions, I understand that you are having discrepancy in disk count during execution of Invoke-AzStackHciHardwareValidation in Azure Stack HCI. When running the Invoke-AzStackHciHardwareValidation command, which validates hardware in an Azure Stack HCI environment, only one disk is listed during execution despite the Get-PhysicalDisk command showing 4 disks.
This are the questions I might like to ask for further verification, kindly provide answer to the below:
- Is there a specific error message or output provided during the execution process?
- Are all disks properly recognised and configured within the Azure Stack HCI environment?
- Is there any additional information available regarding the disk configuration or hardware validation process?
Temporary Solution
Based on your question and what I saw from your screenshot image. The probabilities are you're having one physical disk with virtual disks. Either 1 Physical disk and 3 volume disks(partitions) or 2 Physical disks with 2 Virtual disks, and only 1 physical disk that's accessible during execution.
Reasons, while observing your disks 0 and 1 are of the same name and size, if they are different, that's improper disk naming. Also, your disks 2 and 3 are of the same name and size, if they are different, that's improper disk naming. The serialNumber of the disks might be different though almost similar, virtual machine can do that.
Finally
This issue requires a thorough analysis of disk configuration, validation process, and any potential errors or misconfigurations to ensure accurate hardware validation in the Azure Stack HCI environment.
You can provide more error report for further analysis, since your execution report is not reflecting here.
References
Read more about storage space by the right side of this page Documentation.
- Storage Spaces Direct troubleshooting Learn how to troubleshoot your Storage Spaces Direct deployment by confirming the make and model of your SSD, inspecting for faulty drives.......
I hope this is helpful! Do not hesitate to let me know if you have any other questions.
Please remember to "Accept Answer" if answer helped, so that others in the community facing similar issues can easily find the solution.
Best Regards,
Sina Salam