Found a bug when installing 3.0 RC2. The machine has an SSD for system/boot and 12 2TB drives for a ZoL-based NAS running along with Proxmox. Have been running this config with 2.3 for a while and the ZFS integration was done after installing proxmox so this bug may exist in 2.0 as well.
Severity: Nuance.
Condition: attempting to install using the 3.0 RC2 ISO installer with the install target selected is anything other than /dev/sd0a.
Bug: installer correctly partitions and installs on the selected drive but attempts to install the bootloader on the drive it identified as /dev/sd0a, which is incorrect.
Effect: if /dev/sd0a is an un-partitioned drive the install fails with "could not instal bootloader". If /dev/sd0a is partitioned the bootloader is installed on the wrong drive and boot time results are inconsistent.
Workaround: remove other drives at install time so that install target drive is recognized as /dev/sd0a, install proxmox and re-attach remaining drives after installation is complete.
Severity: Nuance.
Condition: attempting to install using the 3.0 RC2 ISO installer with the install target selected is anything other than /dev/sd0a.
Bug: installer correctly partitions and installs on the selected drive but attempts to install the bootloader on the drive it identified as /dev/sd0a, which is incorrect.
Effect: if /dev/sd0a is an un-partitioned drive the install fails with "could not instal bootloader". If /dev/sd0a is partitioned the bootloader is installed on the wrong drive and boot time results are inconsistent.
Workaround: remove other drives at install time so that install target drive is recognized as /dev/sd0a, install proxmox and re-attach remaining drives after installation is complete.