Help. My OctoPi(OS not the Pi) destroyed itself

Get Help
1

I was printing, then suddenly OctoPrint acces just wasnt possible anymore, i hooked up a hdmi to my Pi, and see there: OS was broken and non readable anymore. 2 minutes before it worked.

I did nothing, because i dont want this to happen again and eventually destroy my SD Card, which happened to me before on my Pi with a other OS(broken version though, idk why)

RaspberryPi 4B 1GB RAM, Ender 3 with Marlin bugfix 2.1.x(old firmware was broken, so i flashed a new one on it), newest OctoPi that is available in the RPi-Imager, 64GB Sandisk SD

2

SD cards have a reputation for corrupting themselves. This occurs more often if the RPi is turned off without shutting down the OS. The best defense against this is to clone the SD card, see https://community.octoprint.org/t/backing-up-the-pi-sd-card/56857 for details.

Another possibility is to use a USB flash drive for the OS instead of a microSD card. See https://community.octoprint.org/t/runnin-octopi-from-a-ssd/25187 for details.

3

oh thx, but it happened while printing, and not while i wanted to shut the Pi off.

4

Probably filled the file system with logs. What size SD card are you using?

5

Filling up this with logs is a little more unlikely, but definitely possible with noisy broadcom error messages.

6

@mcs615-2
But having the requested systeminfo bundle would be of great help here.

7

There is a difference between when the corruption occured and when the corruption is detected.

I leave my RPi turned on all the time. The power consumed is minimal and I find having a Linux system available is useful.

8

How when OctoPi is broken end doesnt start anymore?

1 Like
9

Oops, you are correct. :pensive:

1 Like
10

If you are having challenges with log files filling up the sd card:
sudo journalctl --vacuum-time=3d

I only keep 3 days worth of logs. I run mine on rc.local.