Does your Raspberry Pi have special firmware?
Here the data from my Raspberry Pi:
vcgencmd version
2025/12/08 19:29:54
Copyright (c) 2012 Broadcom
version 2226a853 (release) (embedded)
rpi-eeprom-update
BOOTLOADER: up to date
CURRENT: Mo 8. Dez 19:29:54 UTC 2025 (1765222194)
LATEST: Mo 8. Dez 19:29:54 UTC 2025 (1765222194)
RELEASE: default
(/usr/lib/firmware/raspberrypi/bootloader-2712/default)
Am 11.03.26 um 19:30 schrieb Hank Barta:
I'm aware of this and have used the pre-cloud images for some time,
particularly for 64 bit capable.
It took me a while to figure out I needed to unpack the image first. I
suppose that's on me.
It's also strange that I can't mount the image as a loop device after
unpacking it.
sudo mount -o loop disk.raw /mnt/sdb2
mount: /mnt/sdb2: wrong filesystem type, invalid options, superblock of
/dev/loop2 is corrupted, missing encoding page, or some other error.
dmesg(1) may have more information after failed mount system call.
When I write the unpacked image to the SD card, fdisk or gdisk then
recognizes a hybrid GPT.
gdisk -l /dev/sdb
GPT fdisk (gdisk) version 1.0.10
Partition table scan:
MBR: hybrid
BSD: not present
APM: not present
GPT: present
Found valid GPT with hybrid MBR; using GPT.
Disk /dev/sdb: 30228480 sectors, 14.4 GiB
Model: MassStorageClass
Sector size (logical/physical): 512/512 bytes
Disk identifier (GUID): 539753EF-62BA-4835-BC9C-2A7804DB86E6
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 2048, last usable sector is 30228446
Partitions will be aligned on 2048-sector boundaries
Total free space is 23318495 sectors (11.1 GiB)
Number Start (sector) End (sector) Size Code Name
1 1048576 6909951 2.8 GiB 8305
15 2048 1048575 511.0 MiB EF00
lsblk /dev/sdb
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sdb 8:16 1 14,4G 0 disk
├─sdb1 8:17 1 2,8G 0 part
└─sdb15 8:31 1 511M 0 part
Mounting the two partitions created also does not work:
mount /dev/sdb1 /mnt/sdb1
mount: /mnt/sdb1: wrong filesystem type, invalid options, superblock of
/dev/sdb1 is damaged, missing encoding page, or some other error.
dmesg(1) may have more information after failed mount system call.
dmesg: no info
mount /dev/sdb15 /mnt/sdb15
mount: /mnt/sdb15: wrong filesystem type, invalid options, superblock of
/dev/sdb15 is damaged, missing encoding page, or some other error.
dmesg(1) may have more information after failed mount system call.
dmesg
[247574.881554] FAT-fs (sdb15): invalid media value (0xa9)
[247574.881575] FAT-fs (sdb15): Can't find a valid FAT filesystem
Does your SD card also follow this pattern and still boot?
To rule out hardware problems, a test was also carried out with other
distributions: -> A test SD card created with Raspberry Pi OS (64-bit) /
Release date: December 4, 2025 / Based on Debian Trixie release and an
SD card with DietPi v10.1 boot without any problems on the Raspberry Pi
4 and 5.
> IIRC I tried it on a Pi 3B and it booted but I didn't see/get the on-
> boarding stuff. I don;t recall if this was
> using an SD card or USB/SSD. I also copied an image to an SD card and
> booted a Pi 5. I knew to look
> for the on-boarding messages and saw them but did not have time to test
> further. I have not tested a
> Pi 4. Given time, I could test on a CM4.
Heiko
