05-31-2023, 06:10 AM
Hi, I'm running the latest moode on rpi3b+. I'm using the built in pi audio. It always works fine after freshly installed.
I've now reinstalled it 4 times. Each time, after around a week, the whatever grinds to a halt and doesn't respond and it becomes impossible to ssh into. Once this happens, a forced reboot doesn't restore it to a working state.
The latest time this occurred, I was still logged in via ssh when it ground to a halt. It didn't immediately respond, but after a few minutes it did. I could see that it isn't running out of disk space. Top showed that it was having unusual cpu peaks of up to 12 times what it should. But the web interface no longer responded, so I rebooted using the reboot command for a clean reboot. Now it won't start, just like when I've previously had to do a forced reboot.
The one difference this time compared to previous times is that before, I was using the sd card to boot, but this time I had been running off usb instead as I wanted to rule out sd card issues. But previously I had examined the un-bootable sd card from another Linux machine and it also did not appear to be running out of space.
Since it has no boot information as the image doesn't have hdmi enabled I cannot tell how far the boot sequence is getting.
Is there any diagnostics I can do to understand what is happening? I tried the generic diagnostics linked to the forum sticky post but they weren't helpful for this problem. I also couldn't find anything related by searching the forum, which puzzles me since I've repeatedly had the same fault, surely someone else has experienced it too?
Thanks
Steve
I've now reinstalled it 4 times. Each time, after around a week, the whatever grinds to a halt and doesn't respond and it becomes impossible to ssh into. Once this happens, a forced reboot doesn't restore it to a working state.
The latest time this occurred, I was still logged in via ssh when it ground to a halt. It didn't immediately respond, but after a few minutes it did. I could see that it isn't running out of disk space. Top showed that it was having unusual cpu peaks of up to 12 times what it should. But the web interface no longer responded, so I rebooted using the reboot command for a clean reboot. Now it won't start, just like when I've previously had to do a forced reboot.
The one difference this time compared to previous times is that before, I was using the sd card to boot, but this time I had been running off usb instead as I wanted to rule out sd card issues. But previously I had examined the un-bootable sd card from another Linux machine and it also did not appear to be running out of space.
Since it has no boot information as the image doesn't have hdmi enabled I cannot tell how far the boot sequence is getting.
Is there any diagnostics I can do to understand what is happening? I tried the generic diagnostics linked to the forum sticky post but they weren't helpful for this problem. I also couldn't find anything related by searching the forum, which puzzles me since I've repeatedly had the same fault, surely someone else has experienced it too?
Thanks
Steve
