I have a Pironman 5 with an Inland QN450 NVMe SSD running the latest Debian Trixie release with the Pironman utilities installed. Running fans all the time, not just in performance mode.
Regardless of applications running or not, after several hours and up to a couple of days, the system will fail. The desktop may not be visible when I switch back to it. I can ping it remotely, but I cannot ssh from another host. One time I caught it failing, but the desktop was still alive, I tried to look at the file system and it was gone. Could not run commands as files were not found. An “ls” would show nothing when I knew that to be untrue.
The system needs to have its power removed and left off for a while. I’ve re-imaged it once because it would not reboot after a couple days of attempts.
This leads me to believe it is centered around the SSD in some fashion. But what else should I be looking at to troubleshoot?
I restarted using the SD card and ran the firmware update (rpi-update).Then rebooted from the SSD.
It ran about 4 hours then hung in the same way. This time the desktop was frozen; no mouse or keyboard input taken. I could get ping responses, but no ssh connection. And the 34001 web service is unresponsive.
I figured running the firmware update did not matter as to whether it was from the SSD or SD card.
Have you try to install and run OS on SD card only. Maybe the issue came from your SSD, I don’t know this brand. Maybe it get overheating or consume too much power. You better take a SSD from the compatible list :
I saw Inland is listed on both lists, depending which type…
But just to be sure, if you run OS only on SD card, is it stable?
Also you can test your SSD with Gsmartcontrol app.
I was able to run gsmartcontrol and it said the basic functionality was present and working.
It did complain about some ungraceful shutdowns, and one category of error I now cannot remember.
I wanted to copy the results here, but it decided to die one piece at a time (keyboard stopped working, could not launch a new terminal, then hangs completely) before I could even copy the output into gmail.
Is there a particular counter or piece of data that should concern me looking at the test results?
I’ll run the system with just the sdcard to see if it makes it a couple of days without dying.
I’ll buy a new M.2 and wait for it to come in before I try anything more with this drive.
If this is indeed an incompatibility, it would be nice to have a test for it rather than just “wait to see if Rpi dies”.
I’m assuming that the drive is failing but do not know what logs to view to validate it. Or if the failure is even persisted to a log file. Or to know if something unmounted the drive as a reaction to something.
What specifications does your current power adapter have?
Insufficient power supply could also cause similar issues.
We recommend using the official Raspberry Pi 27W power adapter or a third-party 5V/5A power supply to provide power to the chassis.
Is our configured 4-pin connector properly connected to both the NVMe PIP module and the USB-HDMI adapter?
The purpose of this connection is to provide an additional 5V power supply to the NVMe PIP module, ensuring it receives sufficient power to properly recognize and run the SSD.
Additionally, as mentioned, try using an SD card to boot the system and run it for an extended period. Observe whether the same system crash issues that occur with the SSD still persist.