#449 UEFI/EFI install failure, EFI booting GPT image failure, ZFS install issue
I observed some bugs/errors when playing around with the recent BETA of XigmaNAS and I hope my observations will help making this fine piece of software being available as stable version very soon:
a) Downloading the latest XigmaNAS 13.1.0.5 Live GPT image for amd64 and trying this image to boot off on a UEFI-only configured HP EliteDesk 800 G1 (Firmware 2.78, the latest available) results in a "no boot device/no boot partition error" from the firmware. Switching on CMS support (in HP jargon, this is "legacy support", being found in the security menu) booting is all right.
b) Having boot off the GPT live image with CMS support and trying to install an embedded/EFI variant, the installer fails complaining being not able to install bootcode/bootloader (sorry for the diffuse data, have not the error message memorized). The console pops up with a command "gpart-i..." and if this is the log of the "real" command issued, then it seems that there is no space between gpart and the option -i which could cause the problems.
c) If one have tried to install a ZFS installation on a media and then get second thoughts and decide to perform an embedded/EFI or embedded/GPT installation (this is the subset I tried! So it potentially does not reflect the whole issue, but only a small subset, same is for b)), then the installer fails complaining about not being able to perform the necessary tasks on the "ZFS infested" device (in my case a USB flash drive). Gleancing the device on another box running some magic "dd" procedures (simply writing the first couple ob kilobytes) solves the problem - not zfspool label deletion necessary.
The above problems can be circumvented by booting off the latest official sable 12.3 release of XigmaNAS, performing all the initial steps necessary and desired, then booting off the newly XigmaNAS 13.1 GPT live drive and performing an upgrade as offered by the menu - so far the upgrade procedure takes a few seconds, the underlying 12.3 system seems not to be of any harm.
Kind regards
oh
Thanks for reporting, we will fix this before 3th beta release coming within days
problem fixed, new beta releases out today rev 9284