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

Hi Luis Antonio Orellana Barre

So sorry, this is taking longer than expected.

It's market monopoly issues, I guess.

ABOUT RAID 0:

If you have four virtual disks configured as RAID 0, with two disks having 450GB each and another set of two disks with 1.7TB each, it means that each pair of disks is operating as a single large disk with the combined capacity of the individual disks.

For the pair of disks with 450GB each, the RAID 0 configuration would result in a single virtual disk with approximately 900GB of usable space, as the capacity of RAID 0 is the sum of the capacities of the individual disks.

Similarly, for the pair of disks with 1.7TB each, the RAID 0 configuration would result in a single virtual disk with approximately 3.4TB of usable space.

However, it's important to note that RAID 0 offers no redundancy or fault tolerance. If one disk in either pair fails, all data on that pair of disks would be lost. This makes RAID 0 unsuitable for applications requiring high data availability or reliability.

For use with Azure Stack HCI, which requires individual disk initialization rather than RAID configurations, you would need to reconfigure these virtual disks to operate as separate, individual disks rather than in a RAID 0 configuration.

RAID 0 does not provide any faulty tolerance or parity checker.

I saw in a document; you have to configure everything on your Dell Server.

However, could you spare time to review these documents: https://www.delltechnologies.com/asset/en-us/products/converged-infrastructure/technical-support/h17977-azure-stack-hci-deployment.pdf.

And

https://www.dell.com/support/kbdoc/en-in/000134243/how-to-setup-and-manage-your-idrac-or-cmc-for-dell-poweredge-servers-and-blades.

BIOS Configuration:

• Virtualization Technology: Enabled
• x2APIC Mode: Enabled
• NUMA Nodes Per Socket: 4 (for AX-6515 and AX-7525)
• SR-IOV Global Enable: Enabled
• Systems Profile: Performance (DAPC)
• TPM Security: On
• AC Power Recovery: On
• AC Power Recovery Delay: Random
• Secure Boot: Enabled
• Kernel DMA Protection: Enabled
• Secure Memory Encryption: Enabled
• TPM PPI Bypass Provision: Enabled
• TPM PPI Bypass Clear: Enabled
• TPM2 Algorithm Selection: SHA256
• Intel TXT/AMD DRTM: On
• SMM Security Mitigation: Enabled

iDRAC Configuration:

• Enable NIC: Enable
• NIC Selection: Dedicated
• Enable IPMI Over LAN: Enable
• Redundancy Policy: Input Power Redundant
• Enable Hot Spare: Enabled (if using SCVMM-based management)

Any of these missing might caused the issues, could you send the error in the comment?

Good Success.

I have configured according to the specifications given in BIOS and IDRAC and still giving the error I have been told this but I do not know if it will be feasible and not if it will be possible to do so. :::::::: You need to change the PowerShell Module that is providing the “Invoke-AzStackHciHardwareValidation” function and modify the Disk-Check part of the module.

For this the Signature of the Module File needs to be removed and the Execution Policy needs to be changed as well.

@Luis Antonio Orellana Barre

You mean if it will be possible to do below?

You need to change the PowerShell Module that is providing the “Invoke-AzStackHciHardwareValidation” function and modify the Disk-Check part of the module. For this the Signature of the Module File needs to be removed and the Execution Policy needs to be changed as well.

Yes, it's possible to modify a PowerShell module as described. Here's how you could approach it:

1. Locate the Module: Find the PowerShell module that contains the "Invoke-AzStackHciHardwareValidation" function. You'll need to know where it's located on your system.
2. Remove Signature: Remove the signature of the module file. This can typically be done by right-clicking the file, selecting Properties, and then unblocking the file if there's an option for it. Alternatively, you can use the Unblock-File cmdlet in PowerShell.
3. Change Execution Policy: Adjust the execution policy if necessary to allow the modified module to run. You can use the Set-ExecutionPolicy cmdlet to change the execution policy.
4. Modify Disk-Check Part: Open the module file in a text editor and locate the section related to the Disk-Check part. Make the necessary modifications to this section according to your requirements.
5. Save Changes: After modifying the Disk-Check part, save the changes to the module file.
6. Test: Test the modified module to ensure that the changes made to the Disk-Check part work as expected.

NOTE: Remember to exercise caution when modifying PowerShell modules, especially if they are used in production environments. It's a good practice to test thoroughly before deploying any changes.

Below is an example PowerShell code that demonstrates the steps mentioned above:

# Step 1: Locate the Module
$modulePath = "C:\Path\To\Your\Module.psm1"
# Step 2: Remove Signature
Unblock-File -Path $modulePath
# Step 3: Change Execution Policy (if needed)
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope Process
# Step 4: Modify Disk-Check Part
# Open the module file in a text editor and locate the section related to Disk-Check part.
# Make necessary modifications.
# Step 5: Save Changes (no PowerShell code for this step)
# Step 6: Test (example command)
Invoke-AzStackHciHardwareValidation -Parameter1 Value1 -Parameter2 Value2

Replace "C:\Path\To\Your\Module.psm1" with the actual path to your PowerShell module file. Ensure you have appropriate permissions to modify the file and change the execution policy.

For Step 4, you'll need to manually open the module file in a text editor (like Notepad) and make the required modifications to the Disk-Check part.

After completing these steps, you can test the modified module using the Invoke-AzStackHciHardwareValidation function with appropriate parameters.

Cheers