Closed raballew closed 3 years ago
Thanks for the report. FCOS is starting ignition-diskful.target
at boot, because it doesn't find /etc/coreos-live-initramfs
indicating this is a live system, because you're booting with an incomplete initramfs, because coreos-installer corrupted the download, because it didn't realize that it shouldn't try to decompress the initramfs image.
There are several bugs here: coreos-installer download
shouldn't try to decompress artifacts that aren't intended to be decompressed, and should properly fail if the compressed stream finishes before the download does. Try downloading without -d
, since none of the PXE artifacts are intended to be decompressed before use.
@bgilbert @dustymabe Thanks for sharing this. I actually have to use an uncompressed kernel artifact as piPXE only supports EFI and this can not handle gzip. Therefore I used -d
. Downloading everything again (without -d
) and only decompressing the kernel fixed the issue. For those interested in more details, I created short documentation here. Not all features of the Raspberry are supported but I managed to get FCOS running on my Raspberry Pi's with iPXE.
Should I raise a separate issue for the bugs mentioned?
I actually have to use an uncompressed kernel artifact as piPXE only supports EFI and this can not handle gzip.
I wonder if you use https://github.com/pftf/RPi4 if you'll have better luck (IIUC supports PXE, but I guess maybe not iPXE).
Oh, interesting. On x86_64, vmlinuz is an EFI application, so no decompression is required. But I see that on aarch64 it's just a gzip-compressed binary. It's unfortunate that the Pi requires the extra decompression step.
No need to file a separate bug; I'll just move this over to coreos-installer.
I wonder if you use https://github.com/pftf/RPi4 if you'll have better luck (IIUC supports PXE, but I guess maybe not iPXE).
The build process of pftf's repository provides some useful insights that I can try include when building piPXE or maybe I can directly chainload iPXE with pftf's build.
The first bug should be fixed by https://github.com/coreos/coreos-installer/pull/639. The fix for the second one is forthcoming.
The fix for the second one is forthcoming.
should we re-open then?
Nah, the second bug isn't directly related to the user-visible issue here. I'm working on a fix and should hopefully get it posted soon.
The second fix is now posted in https://github.com/coreos/coreos-installer/pull/655.
Describe the bug
I am trying to iPXE boot the Raspberry Pi with FCOS. At this stage I was able to successfully kick of the process but it times out waiting for device
/dev/disk/by-label/boot
Reproduction steps
Expected behavior Job
dev-disk-by\x2dlabel-boot.device/start
should not time out.Actual behavior For all details see the attached
journalctl -b
log. But in general, first this issue occurs but it can not be fixed by addingdtparam=sd_poll_once
toconfig.txt
of piPXE as I tried this with my own build of piPXE. The problem with this is, that the CoreOS kernel doesn't have any of the optional DT overlays likesd_poll_once
so adding does nothing.Followed by a timeout of
dev-disk-by\x2dlabel-boot.device/start
.System details
Ignition config
Additional information