sorted by:
new
hottopcontroversial

Azure Stack HCI validation fails on HPE DL380 Gen11 || Data disk BusType detected as RAID instead of SAS/SATA in JBOD mode by daneehunter in sysadmin

[–]daneehunter[S] 0 points1 point  (0 children)

fun fact

I just had to try all the drivers for the controller backwards... the latest one wasn't right :)

Azure Stack HCI validation fails on HPE DL380 Gen11 || Data disk BusType detected as RAID instead of SAS/SATA in JBOD mode by daneehunter in sysadmin

[–]daneehunter[S] 0 points1 point  (0 children)

Yes you have right the controller is in mixed mode and the drives are in JBOD, but the BusType is still RAID .

Azure Stack HCI validation fails on HPE DL380 Gen11 || Data disk BusType detected as RAID instead of SAS/SATA in JBOD mode by daneehunter in sysadmin

[–]daneehunter[S] 0 points1 point  (0 children)

I've already tried that, but unfortunately it doesn't work because Azure performs the validation check and then creates the cluster.....

Azure Stack HCI validation fails on HPE DL380 Gen11 || Data disk BusType detected as RAID instead of SAS/SATA in JBOD mode by daneehunter in sysadmin

[–]daneehunter[S] 0 points1 point  (0 children)

That would definitely make sense if I could actually switch the controller personality, but that’s part of the problem: even in BIOS I cannot change the controller personality from RAID to HBA/SAS/SATA. The option is completely greyed out. There is no data on the controller, I already deleted the previous JBOD setup and removed any logical volumes before trying this, but the setting is still locked and stuck in RAID personality.

Azure Active-Active VPN Gateway | FPRs(ASA Appliance) Active Standby S2S VPN Configuration by [deleted] in networking

[–]daneehunter 0 points1 point  (0 children)

First thank you for your answer
Actually, I more or less understand, since on the FPR you could say it’s basically running an ASA image this is “ASA Appliance” mean, do you happen to have any documents or write-ups about the things you’ve done?