Moonraker stops working seemingly at random.

[elfin owl]

I've started encountering an issue recently and it's driving me insane. My printer will turn on, boot fine, klipperscreen works, I can access mainsail through the ip, all is well. but then all of a sudden moonraker somehow loses connection and refuses to reconnect. I've gotten it to reconnect on a few occasions by restarting the printer, but it keeps happening. Just recently I was able to startup, access mainsail through browser, get bed preheated for a print, but by the time the file was sliced and I clicked upload to voron, moonraker had crashed and refused to connect again, although it did attempt for a minute unsuccessfully.

The IP hasn't changed, I've checked it through my router, so I have no idea why Its suddenly having this issue. the only change I've made to the printer is adding a little 5v fan to cool the pi, but I don't think that would be the cause.

I've attached the moonraker log if that helps, as I have no idea how to read it

[cinder swift]

i can see OSError: [Errno 28] No space left on device in there which could be quite relevant- can run df -h and/or du -h to see what is taking up file storage

[elfin owl]

That could make sense, been uploading a ton of files in preperation for a large project, but klipper had said i had over 700mb free so i didn't figure.
Will check that when i'm home from work thanks ^^

[elfin owl]

well, it seems most of the data is in /dev/mmcblkop2.
I did remove a bunch of gcode files taking the free space from around 600-700mb to nearly 3gb, but i'm still confused as to how that much space is being taken up, since as i understand it the os should only take up 1-2gb, and everything else like moonraker and other things installed lik can shouldn't add that much on top of that, and i only have about 1.5ish gb of gcode on the sd.

oh wait using the du -h command you mentioned and looking through it says there's 2.3gb in ./printer_data, i wonder what all of that could be

[hallow vapor]

you might find ncdu useful for tracking down where space is being used

you'll have to install it first with

sudo apt update
sudo apt install ncdu

then you can run it with just ncdu

off hand though, 2.3 gig isn't a totally unreasonable amount of gcode to have lying around

[elfin owl]

I'll get that installed and have a look
But that'a that thing du -h had a different list item for gcode that was 1.9gb, so i don't know what that 2.3 could be

[elfin owl]

oop no i stand corrected, the gcodes is the majority of the printer_data
huh, i guess i just have a lot less storage than i had thought

[elfin owl]

well, after deleting a bunch of excess gcodes i was able to have two successful prints before the issue reared up again. I turned my printer back on after turning if off to swap stealthburner printed parts and now it's doing it again