Latest version 20/04/2026 - Broken?

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=3
G_DIETPI_VERSION_RC=3
G_GITBRANCH=‘master’
G_GITOWNER=‘MichaIng’
G_LIVE_PATCH_STATUS[0]=‘applied’
G_LIVE_PATCH_STATUS[1]=‘applied’

  • Distro version | echo $G_DISTRO_NAME $G_RASPBIAN

trixie 0

  • Kernel version | uname --all

Linux DietPi 6.12.75+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.12.75-1+rpt1 (2026-03-11) aarch64 GNU/Linux

  • Architecture | dpkg --print-architecture

arm64

  • SBC model | echo $G_HW_MODEL_NAME or (EG: RPi3)

RPi 3 Model B (aarch64)

  • Power supply used | (EG: 5V 1A RAVpower)

It’s a 65W 6 port USB power supply with 2 RPIs on it for now

  • SD card used | (EG: SanDisk ultra) SanDisj Ultra 16Gb
  • SanDisk 32GB Ultra Fit USB 3.2 Flash Drive Up to 130 MB/s Read
  • or Seagate 2TB USB Disk
  • or Western Digital 2TB USB Disk

Additional Information (if applicable)

  • Software title | Operating system
  • Was the software title installed freshly or updated/migrated? Brand new install from fresh download
  • Can this issue be replicated on a fresh installation of DietPi?
    ← If you sent a “dietpi-bugreport”, please paste the ID here → Don’t know what this means
  • Bug report ID | echo $G_HW_UUID

Steps to reproduce

  1. Download fresh image (RPI 2/3/4 in this case) released 2026-04-20
  2. Burn to SD Card
  3. Install - minimal installation as I want to recover from a backup… hopefully
  4. Insert a USB disk, I have tried 2 USB HDDs and one USB SSD - All fail in the exact same way
  5. Use Dietpi-drive_manager to select the drive or partition you want to move the rootfs to
  6. Let it complete
  7. Reboot

Expected behaviour

  • The system should restart using the USB drive as the rootfs

Actual behaviour

  • 68110] Kernel panic not syncing: UFS: Unable to mount root fs on unknown-block(0,0)
    69457] CPU: 2 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.12.75+rpt-rpi-08 #1 Debian 1:6.12.75-1+rpt1
    170825] Hardware name: Raspberry Pi 3 Model B Rev 1.2 (DT)
    172194] Call trace:
    173531] dump_backtrace.part.0+0xe0/0x100
    174873] show_stack+0x20/0x40
    176188] dump_stack_lul+0x60/0x80
    177505] dump_stack+0x18/0x28
    1788121 panic+0x170/0x370
    180109] mount_root_generic+0x200/0x2c0
    181415] mount_root+0x210/0x258
    182714] prepare_namespace+0x1e0/0x250
    184002] kernel_init_freeable+0x270/0x2a0
    1852671 kernel_init+0x28/0x150
    186510] ret_from_fork+0x10/0x20
    187743] SMP: stopping secondary CPUs
    1889641 Kernel Offset: 0x1db2c00000 from Oxffffffc080000000
    190181] PHYS_OFFSET: 0x0
    191398] CPU features: 0x00,00000000, 00200000,0200421b
    192631] Memory Limit: none
    193860] [ end Kernel panic not syncing: UFS: Unable to mount root fs on unknown-block(0,0) ]

Extra details

  • until recently, I have been using a USB HDD to run the rootfs. This has worked for a few months until I rebooted today after a patch/fix/update.
    I have tried 2 USB disks and 1 brand new USB SSD stick and they all fail in the same way - with a kernel panic. I have tried both Armv8 and Armv7 builds and notice they were both released yesterday which was when I did the update