v2.4 SD card full

[TitusADuxass]

So my v2.4 decide to throw a hissy this morning and refused to print anything else.

I tried updating things through SSH but soon came to realise that the SD Card (8gb) is full and now I cannot get to mainsail via a browser - 404 Not Found.

I can still SSH into the CB1.

df -h gives me this:

Is there any way that I can delete some files or clear out temporary log files, etc?

I am relucant to flash a new SD card because I don't want to break the CANBus set up.

[TitusADuxass]

@mvdveer I don't have a /home/pi/printer_data.

But I've found printer_data and it's full or it was full.

There's a lot of klippy.log files.

Can I delete those as well?

Edited June 8, 2024 by TitusADuxass

[TitusADuxass]

She's back up and printing now.

There were ghosts of the gcode files still in the print history but they deleted okay.

Lesson learnt from this escapade - more housekeeping required by me.

Muchasgrassyarse for the help.

Edited June 8, 2024 by TitusADuxass

[atrushing]

3 hours ago, TitusADuxass said:

I deleted the job history the other day.

All 100 jobs are back in the list.

I managed to delete 40, but then the delete process stopped working and the system restarted - yes, all the job are once again in the history list. 

I'm pretty sure the Print History in Mainsail is just stored in a database. My best guess is that it is found in ../printer_data/database/data.mdb but I can't read the file to verify. It is less than 1mb in size so getting rid of its entries wouldn't save much space. My gcode folder is closer to 1gb though.

edit: I was busy typing and didn't see your update glad you got it working!

Edited June 8, 2024 by atrushing

[Dirk]

2 hours ago, atrushing said:

just stored in a database.

Yes. These files do not take much space indeed since they are links to the gcode files in the location @mvdveer  

showed. What I was wondering, he had on his SSD a vmlinuz.img and an image file that were both 3.2gb

but I have no idea where they reside. I always see a vmlinux file booting when I boot up a linux system. So I thought you would have more insight in the file system.

anyway. I am glad it's resolved.

[atrushing]

1 hour ago, Dirk said:

Yes. These files do not take much space indeed since they are links to the gcode files in the location @mvdveer  

showed. What I was wondering, he had on his SSD a vmlinuz.img and an image file that were both 3.2gb

but I have no idea where they reside. I always see a vmlinux file booting when I boot up a linux system. So I thought you would have more insight in the file system.

anyway. I am glad it's resolved.

I didn't notice before that there were two files tied as the largest in the directory. But those numbers were in bytes so they are only 21mb each. Plus the fact that they were exactly the same size I would guess that they are two links to the same file. According to Wikipedia, they are static links to the kernel and it is also quite common to have multiple kernels available on a given machine. Vmlinuz is just a compressed image of the vmlinux kernel that gets extracted into RAM on boot.

4 hours ago, TitusADuxass said:

I've downloaded xplorer2 - but I have no idea where to go to find the files that can/need to be deleted.

In xplorer² under the Tools menu there is an option 'Folder Statistics' that scans the size of all sub-directories and brings up a new window that organizes the results.

[claudermilk]

On 6/8/2024 at 6:49 AM, atrushing said:

I'm pretty sure the Print History in Mainsail is just stored in a database. My best guess is that it is found in ../printer_data/database/data.mdb but I can't read the file to verify. It is less than 1mb in size so getting rid of its entries wouldn't save much space. My gcode folder is closer to 1gb though.

edit: I was busy typing and didn't see your update glad you got it working!

It is held in a database, I think that's the name. Copying that when I had to re-flash a new card from scratch allowed me to keep the printer history in the fresh install; someone here pointed to that (I forget who at the moment, sorry).