Creating a bug report/issue
I have searched the existing open and closed issues
Required Information
- DietPi version | G_DIETPI_VERSION_CORE=10
G_DIETPI_VERSION_SUB=5
G_DIETPI_VERSION_RC=2
G_GITBRANCH=‘master’
G_GITOWNER=‘MichaIng’
- Distro version | trixie 0
- Kernel version | Linux homeassistant 6.18.34+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.18.34-1+rpt1 (2026-06-09) aarch64 GNU/Linux
- Architecture |
arm64
- SBC model | RPi 4 Model B (aarch64)
Additional Information (if applicable)
- Software title | Home Assistant
- Was the software title installed freshly or updated/migrated? Updated
Steps to reproduce
- …Update Home Assistant to 2026.7.1
- … Error extracting homeassistant-2026.7.1-py3-none-any.whl
Expected behaviour
How did you try to update HA? And please paste the full error message.
Yes. Same error with the update or the full install.
Resolved 102 packages in 3.27s
× Failed to download homeassistant==2026.7.1
├─
Failed to extract archive: homeassistant-2026.7.1-py3-none-any.whl
├─
I/O operation failed during extraction
╰─
failed to flush file /tmp/.tmpnPuSkt/.tmpWPJUCM/homeassistant/components/srp_energy/translations/vi.json: No space left on device (os error
28)
What is the size of the /tmp tmpfs and memory?
df -h /tmp
free -h
1GB /tmp
2GB raspberry pi
Filesystem Size Used Avail Use% Mounted on
tmpfs 1.0G 572M 453M 56% /tmp
total used free shared buff/cache available
Mem: 1.9Gi 733Mi 831Mi 601Mi 958Mi 1.1Gi
Swap: 152Mi 13Mi 139Mi
1GB /tmp
2GB raspberry pi
Filesystem Size Used Avail Use% Mounted on
tmpfs 1.0G 572M 453M 56% /tmp
total used free shared buff/cache available
Mem: 1.9Gi 733Mi 831Mi 601Mi 958Mi 1.1Gi
Swap: 152Mi 13Mi 139Mi
Hmm, 1 GiB should be sufficient for only extracting wheels. But 572 MiB usage is quite high for /tmp. Is this from the remains of the failed attempt, i.e. does /tmp/.tmpnPuSkt still exist?
To get an overview:
G_TREESIZE /tmp
In any case, you can raise the swap size to get some buffer, e.g. to 4 GiB:
/boot/dietpi/func/dietpi-set_swapfile 4096
But ideally, this should be used (written to) only during rare peak times, not regularly, else it slows down stings and adds to SD card wear a lot (if you use an SD card).
Bumping it up to 4GB did the job.
/tmp/.tmpnPuSkt did still exist, but even removing everything I ran into the error.
I’m using and SSD for HA, so not worried. Wonder if anyone else will run into this.