azure stack hci Invoke-AzStackHciHardwareValidation -Verbose fail volume instance count

Luis Antonio Orellana Barre 20 Reputation points
2024-04-03T12:11:29.4733333+00:00

User's image

my doubt is that by executing the

Get-PhysicalDisk command, it lists 4 disks but when I run the execution process it only lists 1, can you help me?

Azure Stack HCI
Azure Stack HCI
A hyperconverged infrastructure operating system delivered as an Azure service that provides security, performance, and feature updates.
356 questions
0 comments No comments
{count} votes

Accepted answer
  1. Sina Salam 11,991 Reputation points
    2024-04-03T13:30:36.97+00:00

    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


5 additional answers

Sort by: Most helpful
  1. Luis Antonio Orellana Barre 20 Reputation points
    2024-04-15T16:36:40.0333333+00:00

    Good afternoon, I have finally been able to solve it, but I don't know if it will work in productive environments.

    The first thing is to thank the people who have answered.

    What I do in environments that have raid is to mount the windows on the raid disk, when I install the windows to select where I will install it what I do is create me a 500 gb disk of one of the disks that are configured as NORAID install the windows and validate as the internal disks of the server are not in RAID validates it.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.