Creating a bug report/issue
I have searched the existing open and closed issues
Required Information
- DietPi version |
cat /boot/dietpi/.version- G_DIETPI_VERSION_CORE=10
G_DIETPI_VERSION_SUB=0
G_DIETPI_VERSION_RC=1
G_GITBRANCH=‘master’
G_GITOWNER=‘MichaIng’
- G_DIETPI_VERSION_CORE=10
- Distro version |
echo $G_DISTRO_NAME $G_RASPBIANtrixie
- Kernel version |
uname --allLinux R5BP 6.1.115-vendor-rk35xx #1 SMP Wed Dec 24 10:54:39 UTC 2025 aarch64 GNU/Linux
- Architecture |
dpkg --print-architecturearm64
- SBC model |
echo $G_HW_MODEL_NAMEor (EG: RPi3)ROCK 5B (aarch64)- It’s actually a Rock 5B +
- Power supply used | (EG: 5V 1A RAVpower)
- Radxa Power PD 30W - 9V / 2A, 12V / 2.5A
- SD card used | (EG: SanDisk ultra)
- SanDisk ImageMate 64GB
Additional Information (if applicable)
- Can this issue be replicated on a fresh installation of DietPi?
- Yes
- Bug report ID |
echo $G_HW_UUIDee71bfae-d00d-4bb6-b536-6568f1989cac
Steps to reproduce
After a successfull write of the Radxa 5B image to the SD using Balena Etcher, on first boot, the GPT table is corrupt on the SD card.
- Flash the SD card with the Radxa 5B image using Balena Etcher
- Customize the setup files:
dietpi.txtdietpi-wifi.txtdietpiEnv.txtfdtfile=rockchip/rk3588-rock-5b.dtb→fdtfile=rockchip/rk3588-rock-5b-plus.dtb
- Put SD into board and wait for the setup to complete
- login and run
fdisk -l - Error is shown for the boot partition
Expected behaviour
- No errors with the GPT partitions.
Actual behaviour
The boot partition is corrupt, but the backup is OK.
-
Disk /dev/mtdblock0: 16 MiB, 16777216 bytes, 32768 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 7B7A6FDE-8147-4712-A91F-524B1DDF8D33 The primary GPT table is corrupt, but the backup appears OK, so that will be used.
Extra details
Everything works fine, no issues while using the system whatsoever.
I’m building a RAID 1 with the board so that’s why I found this error. First I thought it was the cheap SD card I was using, so I bought a brand new SanDisk, but the error remains.
I flashed the SD cards multiple times, both of them, but the error is consistent, every single time I flash the image to the card and boot them.