On 2021-07-26 23:20, Dusty Mabe wrote:
On 7/26/21 3:17 AM, Philip Rhoades wrote:
> I used the latest LiveUSB:
> and I can install it OK and it created 4 partitions on /dev/sda but I
> can't get it to boot from there. I have the boot order set up with
> first and the live USB second and I always get the live version
odd. What happens if you remove the USB key from the system and try to
I tried installing the workstation F34 first - see below . . but I would
expect that it would move then to the old IDE drive further down the
boot chain that has a Windows setup on it - I am guessing if removed
that too I would get a grub prompt saying "no boot media" . . but I will
see how I go . .
> I do not add the ign switch for the install command thinking that
> minimal install command will work just as well as the LiveUSB (DHCP
> works in live mode)? ie:
> sudo coreos-installer install /dev/sda
Unfortunately that won't be sufficient. The live ISO will drop you to a
bash shell, but an installed system won't do that. In the very least
to create an Ignition config with an SSH key you can use to log in to
But it appears that the the SSD drive is not even being set up to boot
since it is first on the boot list but is skipped . . but I will try the
ign option as well . .
> I am thinking of installing the F34 workstation version just to
> that will boot from sda . . any other suggestions?
Not really. Our disk images should work in either legacy BIOS boot or
boot, but maybe one data point would be to try one or the other and see
you get different behavior.
Well, as expected, the F34 WS LiveUSB booted and installed happily to
/dev/sda and then booted from the SSD no problem. However, the WS
version installed a bootup for a BIOS environment - I am not 100% sure
but I think the CoreOS LiveUSB created a UEFI partitioning . . I will
need to do it again to be sure . .
Please let us know what you find.
Will do . . thanks!
PO Box 896
Cowra NSW 2794