Raspberry Pi 5, DietPi v9.17.2, USB NVME stopping working

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=9
G_DIETPI_VERSION_SUB=17
G_DIETPI_VERSION_RC=2
G_GITBRANCH=‘master’
G_GITOWNER=‘MichaIng’
G_LIVE_PATCH_STATUS[0]=‘applied’

  • Distro version | echo $G_DISTRO_NAME $G_RASPBIAN

trixie 0

  • Kernel version | uname --all

Linux casa-pi5 6.12.47+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.12.47-1+rpt1 (2025-09-16) aarch64 GNU/Linux

  • Architecture | dpkg --print-architecture

arm64

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

RPi 5 Model B (aarch64)

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

5.1V=5.0A

  • SD card used | (EG: SanDisk ultra)

USB case Ugreen with NVME Netac

Additional Information (if applicable)

  • Software title | (EG: Nextcloud)

  • Was the software title installed freshly or updated/migrated?

  • Can this issue be replicated on a fresh installation of DietPi?

    I am not sure.
    ← If you sent a “dietpi-bugreport”, please paste the ID here →

  • Bug report ID | echo $G_HW_UUID

Steps to reproduce

  1. I have installed dietpi on a USB case with NVME and boot it, it start working fine.
  2. After some hours, it is like the network stop work correctly.
  3. If i try access it with ssh, it respond, but give message of wrong password. Beside all network service hosted on the Pi, stops respond as well.
  4. Everything come back after restart (turning off the power and bringing back on).
  5. On Journalctl, the dietpi stop register logs too when the freezing happens. But, again, i still getting some answer when i try connect it with ssh dureing the “freezing“.

Expected behaviour

  • Not stopping respond.

Actual behaviour

  • I think it should be some kernel panic, but it is not registered on log.

Extra details

  • I have disable the wifi, because of some bug on firmware with USB boot (IA suggestion).
  • I notice the last log registered is always:
out 12 07:54:59 casa-pi5 ifup\[485\]: DHCPOFFER of 192.168.1.6 from 192.168.1.1 
out 12 07:54:59 casa-pi5 ifup\[485\]: DHCPREQUEST for 192.168.1.6 on eth0 to 255.255.255.255 port 67 
out 12 07:54:59 casa-pi5 dhclient\[485\]: DHCPREQUEST for 192.168.1.6 on eth0 to 255.255.255.255 port 67 
out 12 07:54:59 casa-pi5 dhclient\[485\]: DHCPACK of 192.168.1.6 from 192.168.1.1 out 12 07:54:59 casa-pi5 ifup\[485\]: DHCPACK of 192.168.1.6 from 192.168.1.1 
out 12 07:54:59 casa-pi5 systemd\[1\]: Stopping systemd-timesyncd.service - Network Time Synchronization... 
out 12 07:54:59 casa-pi5 systemd\[1\]: systemd-timesyncd.service: Deactivated successfully. 
out 12 07:54:59 casa-pi5 systemd\[1\]: Stopped systemd-timesyncd.service - Network Time Synchronization. out 12 07:54:59 casa-pi5 systemd\[1\]: Starting systemd-timesyncd.service - Network Time Synchronization... 
out 12 07:54:59 casa-pi5 systemd\[1\]: Started systemd-timesyncd.service - Network Time Synchronization. out 12 09:36:35 casa-pi5 systemd-timesyncd\[552\]: Contacted time server 192.168.1.1:123 (192.168.1.1).

Sounds like the symptoms of a powering issue.
Does the USB case have it’s own power supply?

Powering issues should also be logged, but the logs get lost if you lose power and do not have full logging enabled.

Does the USB case have it’s own power supply?

No, it doesn’t.
I have the full loggin enabled, but i don’t recieve any information about power supply.
Runnig vcgencmd get_throttled, the answer is throttled=0x0.
The log shows some warnings and errors on bluetooth and wifi. But last week i disabled both of them.

pls try using a powered USB hub to verify if the issue persists.

I don’t have one. I’m gonna do some others tests and is it didn’t solve, i will come back do microsd.
I found this issues Raspberry Pi 5 fails to boot or loses connection with Realtek RTL9210 NVMe adapters (Ugreen / SSK, firmware 20.01) · Issue #7080 · raspberrypi/linux · GitHub, and looks like my problem. I will give it a try the solution.

1 Like