Hi!
Not sure if this is vendor or Hypervisor related but our semi-automatic deploy with a customized ks_cust.cfg and ESXi 703 doesn't work as it used to when shifting from Dell R730/R740 to the newer XR12 with Perc H755 and NVMe disks.
We have two virtual disks on each server setup in a specific order for OS-VD first and VM-VD as second.
Also, legacy boot selection within the RAID ctrl setup to boot from the first VD (yes we're still using legacy bios boot).
With that setup it worked perfectly on the R730/R740 with the following lines in ks_cust.cfg to select which disk to deploy ESXi on;
clearpart --firstdisk --overwritevmfs
install --firstdisk --overwritevmfs
However, when shifting to the new XR12 platform with the new Perc H755/NVMEe RAID ctrl the issue appears to be with the order that ESXi enumerates the disks. Now the ESXi-install takes place on the second VD(!) - is there a reason for that?
We've tried recreating the VDs without any change. It's just the opposite behavior compared to earlier hardware.
Also, it's not possible to find any useful persistent device links to the first VD to put in the ks_cust.cfg either - only those changing naa.xxxxxxxxxxxxxxxxxxxx device paths.
(Frustrated)
/Per
