People,
I used the latest LiveUSB:
fedora-coreos-34.20210626.3.1-live.x86_64.iso
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 sda first and the live USB second and I always get the live version booting . .
I do not add the ign switch for the install command thinking that a bare minimal install command will work just as well as the LiveUSB (DHCP works in live mode)? ie:
sudo coreos-installer install /dev/sda
I am thinking of installing the F34 workstation version just to see if that will boot from sda . . any other suggestions?
Thanks,
Phil.
On 7/26/21 3:17 AM, Philip Rhoades wrote:
People,
Hi Phil,
I used the latest LiveUSB:
fedora-coreos-34.20210626.3.1-live.x86_64.iso
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 sda first and the live USB second and I always get the live version booting
odd. What happens if you remove the USB key from the system and try to boot?
. .
I do not add the ign switch for the install command thinking that a bare 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 you need to create an Ignition config with an SSH key you can use to log in to the machine.
https://docs.fedoraproject.org/en-US/fedora-coreos/authentication/
I am thinking of installing the F34 workstation version just to see if that will boot from sda . . any other suggestions?
Not really. Our disk images should work in either legacy BIOS boot or UEFI boot, but maybe one data point would be to try one or the other and see if you get different behavior.
Good Luck!
Please let us know what you find.
Dusty
Dusty,
On 2021-07-26 23:20, Dusty Mabe wrote:
On 7/26/21 3:17 AM, Philip Rhoades wrote:
People,
Hi Phil,
I used the latest LiveUSB:
fedora-coreos-34.20210626.3.1-live.x86_64.iso
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 sda first and the live USB second and I always get the live version booting
odd. What happens if you remove the USB key from the system and try to boot?
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 a bare 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 you need to create an Ignition config with an SSH key you can use to log in to the machine.
https://docs.fedoraproject.org/en-US/fedora-coreos/authentication/
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 see if that will boot from sda . . any other suggestions?
Not really. Our disk images should work in either legacy BIOS boot or UEFI boot, but maybe one data point would be to try one or the other and see if 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!
P.
On 7/27/21 12:50 PM, Philip Rhoades wrote:
Dusty,
On 2021-07-26 23:20, Dusty Mabe wrote:
On 7/26/21 3:17 AM, Philip Rhoades wrote:
People,
Hi Phil,
I used the latest LiveUSB:
fedora-coreos-34.20210626.3.1-live.x86_64.iso
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 sda first and the live USB second and I always get the live version booting
odd. What happens if you remove the USB key from the system and try to boot?
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 . .
Hmm. Be careful with having more than one OS. FCOS doesn't really consider or handle dual-boot. I think Fedora WS may handle this and maybe that's the difference.
I do not add the ign switch for the install command thinking that a bare 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 you need to create an Ignition config with an SSH key you can use to log in to the machine.
https://docs.fedoraproject.org/en-US/fedora-coreos/authentication/
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 see if that will boot from sda . . any other suggestions?
Not really. Our disk images should work in either legacy BIOS boot or UEFI boot, but maybe one data point would be to try one or the other and see if 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 . .
The disk image that gets written out supports both UEFI and legacy (BIOS) boot at the same time. IIUC it's the same image that gets written out regardless of your environment.
Please let us know what you find.
Will do . . thanks!
P.
Dusty,
On 2021-07-28 02:55, Dusty Mabe wrote:
On 7/27/21 12:50 PM, Philip Rhoades wrote:
. .
I do not add the ign switch for the install command thinking that a bare 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 you need to create an Ignition config with an SSH key you can use to log in to the machine.
https://docs.fedoraproject.org/en-US/fedora-coreos/authentication/
I used the example.bu with my key:
variant: fcos version: 1.3.0 passwd: users: - name: core ssh_authorized_keys: - ssh-rsa AAAAB3Nz. . .
and indeed I was then able to install coreos with the generated ign and it booted happily from /dev/sda then.
However, ssh in is refused and nmap from my F34 WS is showing that port 22 on the CoreOS machine is not open . . I couldn't find anything in the docs that helped . . suggestions?
Thanks again.
Phil.
On 7/31/21 7:41 AM, Philip Rhoades wrote:
I used the example.bu with my key:
variant: fcos version: 1.3.0 passwd: users: - name: core ssh_authorized_keys: - ssh-rsa AAAAB3Nz. . .
and indeed I was then able to install coreos with the generated ign and it booted happily from /dev/sda then.
Good to hear.
However, ssh in is refused and nmap from my F34 WS is showing that port 22 on the CoreOS machine is not open . . I couldn't find anything in the docs that helped . . suggestions?
Hmm. Any chance you are trying to connect to the wrong IP? Maybe execute the process again but this time set a password as well that you can use to log in on the console with to inspect networking.
https://docs.fedoraproject.org/en-US/fedora-coreos/authentication/#_using_pa...
Thanks again.
Phil.
Dusty,
On 2021-08-01 01:11, Dusty Mabe wrote:
On 7/31/21 7:41 AM, Philip Rhoades wrote:
I used the example.bu with my key:
variant: fcos version: 1.3.0 passwd: users: - name: core ssh_authorized_keys: - ssh-rsa AAAAB3Nz. . .
and indeed I was then able to install coreos with the generated ign and it booted happily from /dev/sda then.
Good to hear.
Spoke too soon - the CoreOS server is downstairs and when it was booting and looked like it had installed OK, in my enthusiasm, I rushed upstairs only to find I still could not ssh into the CoreOS machine - then I realised, the CoreOS machine had rebooted on the USB stick . . removing the stick and rebooting indicated the problem still persisted.
So, I went through the BIOS setup yet again and found an option "Boot from UEFI" and enabled that - and boom!, CoreOS then booted! So now I am only confused about why F34 WS installed OK as UEFI and ALSO booted on this machine when this config was still disabled . .
Thanks for you help again!
Regards,
Phil.
coreos@lists.fedoraproject.org
-
Dusty Mabe -
Philip Rhoades