I’ve been running 9.8.0 on RPi 5 and executed the update. It seems to have completed properly and at the end prompted me to restart due to kernel changes. I did so, but since then, it can no longer boot. I can’t SSH into it because the network is not up and is no longer visible in the router, so not getting an IP address. But I can’t even get HDMI signal either. It is connected to a TV due to Kodi, but it now says no signal. Moving it to my monitor, it is occasionally picking up something and showing some fast moving line of text on the screen, but that disappears in less than a second. Most of the time that is also saying there is no signal.
Anyone else having such issues or has ideas what could cause this or how to fix? I already ran into the same problem with the 9.7.0 to 9.8.0 upgrade.
I know, but given I no longer can boot I couldn’t fill in the majority of the template, nor have I any reproduction steps other than running dietpi-update from 9.8.0 to 9.9.0.
I’m booting from a HP 64 GB V30 SD card. Last time this issue happened I ran a validation on the card with H2testw twice before reinstalling from a fresh image, but no issues were found then.
Software stack was: PiVPN (Wireguard), Samba, Kodi, Docker, Docker compose. Additionally, udisks2 was installed to allow for auto-mounting USB drives in Kodi.
The button isn’t stuck. There was an SSD connected via USB, but the issue was the same without it. The ethernet LED I didn’t check.
Since posting I removed the SD card and did another validation on it, but everything seems to be fine. Then flashed a fresh image and enabled automatic restore. This worked and successfully restored a working 9.8.0. With the exception that it didn’t configure the original userdata from the SSD. Gave the update another try and this time it worked without any issues and I’m running on 9.9.0 now. I still don’t have any clue why I’ve run into the same issues both with the 9.8 and 9.9 update, or why the 9.9 worked just fine a second time. Any ideas are welcome.
I have one remaining problem, docker is not working. But I think I’ve encountered this issue once, and it can’t handle when the docker-data folder changes, and now it created a new one in the SD before I reconfigured the userdata to the SSD.