@MyWereld Welcome to the Rockstor community.
Re:
Exactly; that, so far, is our take-away. We have had this reported and have an issue opened with a work around in that issue here:
And as you see from that issue it works just fine on the potentially idealised UEFI only KVM proof of concept. But this does not appear to affect all systems. Some UEFI systems seem to boot just dandy.
Essentially we rely on our upstream installer builder kiwi-ng for this functionality. And our own kiwi-ng config here:
looks to be good, and as mentioned, we don’t appear to have had many reports of this failure. One of the core Rockstor developers @Flox has a machine that is similarly affected. I have access only to the KVM UEFI where our installers work just fine. All a bit of a mistery that has had similar reports from completely different OS builds in the kiwi-ng upstream repository. But it still may be that we are doing it wrong. For example you could try building your own installer from the rockstor-installer repo and try other settings with for example this:
firmware="efi"
changed to:
firmware="uefi"
Which I think adds secure boot functionality. Again this is all handled by our installer builder and so is in their hands. I also suspect they prove functionality in uefi via the KVM method that works for me too.
Take a look at that issue as the original reporter found a work around of simply re-installing grub before the first reboot at the very end of the installer. The command used was:
grub2-install some-options-depending-on-install-arch-etc
But you may find that no options are actually required.
Let us know how you get on. As stated this is currently a major pain and we have been watching upstream for some time as I suspect there is something more they need to do to cover some hardware quirks. I’ve linked to our own report of this in for example the following issue in their repository:
Debian OEM image is not rebootable · Issue #1991 · OSInside/kiwi · GitHub which was on a debian base of all things. It’s definitely quirky but what else do we expect from uefi, it’s code base is larger than the linux kernel you know!!!
And all manufactururs have their own interpretation on exactly how or if to register/boot/allow-boot of the available options.
Have you tried disabling secure boot by chance. Not always an option but was promised as such in the early days of uefi introduction.
Let us know how you get on with that work around. We are not uefi efi experts and are basically awaiting a fix or work around ourselves. And this may end up being a force re-install at the end of the install or some such hackery. But if it works for some setups (KVM proof in issue) then why not others?
Incidentally we have this in our short-list for “First v4 stable release” of stuff to address in our installer here:
Milestones - rockstor/rockstor-installer · GitHub
We have now reached v4 stable rpm (released yesterday and soon to be promoted to stable repo):
so hopefully we can tend to the remaining issues in the installer repo. But we do need help on how to sort this seemingly system dependant uefi failure.
Hope the above helps. And thanks for a nicely detailed report.