Starting a new HAOS install on a Raspberry pi 5. Raspberry pi 5 known good. SD card known good. SD card reformatted and verified good. Using latest version of Raspberry Pi imager v1.9.6 on Windows 11.
If I select the version for Raspberry pi 4 64-bit, the imager works and verifies. I will then have 2 partitions on the SD card. The first is hassos-boot (D:), 32MB FAT primary partition. Second partition is 119.02 GB unallocated. This is a 128G SD card. This image will boot.
Using same setup. Same imager. This time I select the HAOS 64-bit image for Raspberry Pi 5. Imager works and verifies. This time there are 9 partitions on the SD card. They are listed as 64MB Healthy (EFI System Partition), 24MB Healthy (Primary partition), 256MB Healthy (Primary partition), 24MB Healthy (Primary partition), 256MB Healthy (Primary partition), 8MB Healthy (Primary partition), 96MB Healthy (Primary partition), 1.25GB Healthy (primary partition), 117.09GB Unallocated.
This image will not boot. With ethernet cable connected the socket lights up on the Pi4 image. On the Pi5 image the socket stays dark. Attaching debug serial connection is non responsive.
Hardware is Pi5 16G ram, 128G SD
It looks like the 16.0 Pi4 64-bit image is good but the 16.0 Pi5 64-bit image is hosed up in some manner.
I may try to go with the PI4 image on the Pi5 and see if it works and I can upgrade from there. I haven’t tried it yet I am relatively new to HA.
I saw several posts about people having trouble installing HAOS on an RPi5.
I installed HAOS on my RPi5 in May without any problems.
The RPi manager I was using at the time was version 1.8.5 (I think).
Try this version instead of the latest one. It might work better that way. https://github.com/raspberrypi/rpi-imager/releases/download/v1.8.5/imager-1.8.5.exe
Thanks for the lead Frank. Unfortunately it is still a no-go.
I downloaded and ran version 1.8.5 RPI manager. Installed the HAOSS 64-bit 16.0 PI 5 image. It created the 9 partitions again. I loaded the SD card and it doesnt boot. I am running headless and will have a crash cart tomorrow.
So just as another test I reformatted the same SD card with a standard Raspberry Pi5 64-bit OS. It shows the 2 partitions again. Partition 1 512MB Fat32 Healthy Primary Partition label ‘bootfs’ mounted as D:. Partition 2 is 118.58 GB Healthy Partition. This version booted immediately and within 3 seconds lit up the Ethernet socket lights.
So everything I put on the SD card except HAOSS Pi5 (multiple versions) creates the bootable first FAT 32 partition. I went back to HAOSS version 12.0 for PI5 64-bit and tried 12, 13, 14, 15, 16 and they all create the 9 partitions with the first partition an EFI partition. HAOSS for PI4 64-bit creates 2 partitions bootable. All the standard Raspberry PI OS images format to 2 partitions. So basically there is something with how the HAOSS Pi5 images are created that do not format a SD card properly for me. Actually I was surprised it created an EFI first partition. Everything else I have installed on the SD card has created a MBR bootable first partition.
I will have a bit more detail tomorrow after I get the crash cart but since there is no activity on the status LEDs I suspect the BIOS is going to say it cant find anything bootable.
Frank,
I downloaded and flashed that image on the SD card. It created the EFI partition again and it will not boot. It comes down to why is the HASSOS Pi5 image(s) the only ones that create EFI partitions.
I found this on stackexchange:
The only compatibility quirk is that grub2 may set the EFI flag on the boot partition, and the RPi bootloader will refuse to boot off a partition with an EFI flag set. The flag can be manually cleared by any partition editor, making both RPi bootloader and grub2 recognize the partition correctly.
I am still waiting on the crash cart for further debug. However I think the EFI partition will be the hurdle.
And I dont know why others are able to install a Pi5 image and not have the EFI problem. I have windows 11. I have tried 3 versions of Raspberry Pi Imager. I have tried 6 versions of HASSOS for the Pi5.
I found the ‘Windows On Pi’ project that has a custom EEPROM image to flash onto the Pi but I shouldn’t have to mess with that.
Thanks for everyone’s help. After getting the crash cart installed I found the PI5 image was actually booting. However both wlan0 and end0 ports were disabled for some reason. That was why the network was not lighting up. So using HA command line reference I enabled the networks and now I am online.
I still don’t understand why the PI5 image creates EFI partitions and everything else doesn’t but I am online. I see references to VLAN creation and docker.
