I've done a test or two to verify why initially the boot-loader failed to install (not Virtualbox) on a real system where SATA has been disabled in the bios and only-USB was used.

Two USB sticks were used, one for the installer which was plugged in the first usb port, and another USB which was empty meant to be used for the installation.

Apparently without warning or prompts, the installer automatically writes the boot-loader to what it perceives as "/dev/sda", which is installer usb.  Later rebooting the installer no longer worked but the "boot loader" running from it can start up the new system.

An easy solution to prevent this, is of course to always assume the install drive to be "/dev/sda"...but for the majority of distro installers out in the wild are able to prompt or give an option to view/change the bootloader during its installation.

The big problem I'm seeing with this, is the installer is not checking where "/" is being applied nor is it aware of its own install media, .. if the bootloader by default is set to the drive where "/" is getting mapped I believe it could remedy it.

thanks


Reproducible: 

Steps to Reproduce: