Jump to content

Recommended Posts

Posted

I've got an Pine64 a that was one of the Kickstarter models.  For a couple of years I've been running OctoPrint on it to run my Qidi i-mates 3d printer.  Recently I decided to update from jammy to noble, before I did that I made a backup of my OctoPrint settings and files through the OctoPrint GUI in case of problems.

I got a really messed inconsistent with all sorts of dependencies errors because the apt dist-upgrade seemed to freeze and after several hours of no movement I rebooted.  As expected it was the mess.  I spent about an hour on fixing dependencies but decided it just wasn't worth it as the only thing running is OctoPrint.

When I went to restore OctoPrint, I got an error message about not enough space.  When I did a df -m , I had plenty of space on the main partition, I posted on the OctoPrint forum and it was pointed out that my /tmp was tiny.  Would anyone have any ideas of what is going on and what I can do to fix it?

Here's the OctoPrint Error:
 

Uploading backup, this can take a while. Please wait... Restoring from backup... Unpacking backup to /tmp/tmpf_d22xwu...Removing temporary unpacked folderError while running restoreTraceback (most recent call last):  File "/home/ageoffri/OctoPrint/lib/python3.12/site-packages/octoprint/plugins/backup/__init__.py", line 1243, in _restore_backup
    zip.extract(member, temp)  File "/usr/lib/python3.12/zipfile/__init__.py", line 1726, in extract
    return self._extract_member(member, path, pwd)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^  File "/usr/lib/python3.12/zipfile/__init__.py", line 1802, in _extract_member
    shutil.copyfileobj(source, target)  File "/usr/lib/python3.12/shutil.py", line 204, in copyfileobj
    fdst_write(buf)OSError: [Errno 28] No space left on device Restore failed! Chec


And here's the df -m :
 

Filesystem 1M-blocks Used Available Use% Mounted on
tmpfs 198 4 195 2% /run
/dev/mmcblk0p1 59861 3078 56137 6% /
tmpfs 988 1 988 1% /dev/shm
tmpfs 5 0 5 0% /run/lock
tmpfs 988 0 988 0% /tmp
/dev/zram1 47 3 41 6% /var/log
tmpfs 198 1 198 1% /run/user/1000



 

Posted

Hello @alg_42

 

You have only 1 GB of space in /tmp.  This is tmpfs, so it uses your RAM.  It is not enough to unpack your backup into.  You can increase the size but the Pine64 either has only 512MB or 1GB of RAM, so that is not a good idea.  I suggest you temporarily deactivate the /tmp mount instead, reboot, complete your backup and then reactivate the /tmp mount and reboot again. Armbian puts /tmp on tmpfs so that the frequent writes to it do not wear out your flash so it is important you reactivated it later on and don't leave it on your main partition indefinitely.

 

Can you share the output of "grep tmp /etc/fstab" with us?

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines