Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Metal-bios and Metal-uefi images do not boot after install #22

Closed
yuqi-zhang opened this issue Apr 5, 2019 · 5 comments
Closed

Metal-bios and Metal-uefi images do not boot after install #22

yuqi-zhang opened this issue Apr 5, 2019 · 5 comments

Comments

@yuqi-zhang
Copy link
Contributor

Using the iso + bios/uefi image from https://ci.centos.org/artifacts/fedora-coreos/prod/builds/latest/ and following: https://github.com/coreos/coreos-installer#using-the-installer-on-fcos-or-rhcos, the installed FCOS does not seem to boot correctly. More specifically, the install to disk seems to happen correctly, and then upon reboot, shows the bootmenu, and then hangs shortly thereafter with no messages etc.

Ignition conf:

{"ignition":{"config":{},"security":{"tls":{}},"timeouts":{},"version":"3.0.0"},"networkd":{},"passwd":{"users":[{"groups":["sudo"],"name":"core","sshAuthorizedKeys":["ssh-rsa ...]}]},"storage":{},"systemd":{}}

Note that I've seen similar issue with ignition v2s3 in RHCOS before as well, the ova and ami still work correctly, but an iso installed image does not. (Not sure if this is an actual error with the installer or somewhere else.)

@jlebon
Copy link
Member

jlebon commented Apr 8, 2019

Hmm, did you check if the serial console showed any error message? I tried this locally (though just the bios image) and it worked but I essentially hit coreos/coreos-assembler#339. I.e. I had to add ignition.platform.id=metal so that Ignition didn't die.

@yuqi-zhang
Copy link
Contributor Author

Can confirm coreos/coreos-assembler#339 fixes the issue, closing

@jcordes73
Copy link

jcordes73 commented Apr 10, 2019

I was playing around with the console kernel boot parameters, changing

console=ttyS0,115200n8

to

console=ttyS0 console=tty0

and then logs appeared on the console.

Unfortunately I have to do this change after every install, as there is not way I can set the kernel parameters for the next boot. But I have seen that https://github.com/coreos/coreos-installer/issues/13 has been opened for this.

@jlebon
Copy link
Member

jlebon commented Apr 10, 2019

@jcordes73
Copy link

Tested with 29.936 and it is working, i.e. I get log output on the console.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants