netboot

As I’ve noted in a recent post, I’ve had a problem with my diskless netbooting hosts sometimes needing several boot attempts to come up again. In this article, I will describe a short setup for virtual machines to debug such a problem. I’ve chosen to do it via virtual machines instead of one of my physical hosts because it makes a lot of things easier. Chief amongst those the fact that with a VM, I’m able to look at the boot process a lot more easily than with a physical host, which are all headless in my setup....

I’ve had a problem for quite a while now. As a reminder, I’m booting eight Raspberry Pi CM4 and one Udoo x86 II completely diskless, using boot partitions on NFS, PXE netboot and the Pi’s netboot feature with root disks being supplied by Ceph RBD volumes. If you’re interested in the details, I’ve got an entire series on the setup, as well as a separate article describing the Udoo boot setup....

I’m currently planning to switch my Homelab to a cluster of eight Raspberry Pi CM4 modules with two Turing Pi 2 boards. That means a full switch to the aarch64/ARM processor architecture. But not all software supports aarch64 yet. So I went looking for a small x86 machine which doesn’t cost too much, doesn’t take too much space, and doesn’t consume too much power. What I found was the Udoo x86 II Ultra....

Finally, the Netboot Raspberry Pi series concludes with this post. I will be going over both, what figuring out the actual netboot and blogging about it was like. If you’ve followed this series, I’m hoping that you’ve learned a lot more than “just” how to produce an image that can netboot a Raspberry Pi 4. For me, the information on the side, like how the initramfs works in the Linux boot process, was more interesting than then netboot itself....

This is the fifth part of my Raspberry Pi netboot series. The introduction with an overview and links to previous articles can be found here. In this post, we will go over the Ansible playbook I use to provision my Pis. This playbook’s intention is not to fully provision the Pi for use, e.g. it will not set up Nomad or Ceph. It will only prepare the image to netboot and set up my normal Ansible user for my main provisioning Ansible playbooks, to be executed after first boot....