No boot device found after installation

I’m at a complete loss and have tried everything, but for some reason I just cannot get Rockstor installed on this PC.

I have searched the internet and the forums but also did not find anything related to this.

The installation finished successfully, but after reboot I get the error “No bootable device found”
If I select BIOS boot options and specify the installation disk, then it boots, but obviously this is not ideal.

I have tried:

  • With legacy and UEFI installations
  • I have even removed all the hardware and disks to only have the installation disk present
  • I have switched SATA cables and places on the motherboard, no dice
  • I have cleared the CMOS multiple times by now

It is almost like GRUB is not fully installed.

Could anyone assist me with some more troubleshooting tips please?

Installation media: Rockstor Leap 15.3 Generic

Some more info:
Intel DP67BA motherboard
120GB Patriot Burst Elite SSD

@MyWereld Welcome to the Rockstor community.

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:


changed to:


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: 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:

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.

1 Like

Just a quick update, unfortunately not a happy one.

I could not get the installed to correctly install GRUB, and I’m quite miffed at this since I really love Rockstor.

I now unfortunately have to let it be for a while, maybe wait for a new release to come out and then try again. In the mean time I’ll have to use a competitor…

Sorry to hear that!
Quick question, did you remove the install media after completion. I did run into a similar issue when I rebooted with the ISB stick still plugged into the system

The USB installation media is unplugged each time.

I would not fret about it too much, the hardware I’m trying to install it on is one of the very first Intel 1155 EFI motherboards I use for a SOHO solution. I have searched for a BIOS update but unfortunately Intel does not support the board any more and I cannot find an archive of the motherboard’s BIOS anywhere. Maybe there was a BIOS fix to make the board play nice with EFI installation media, I will never know…