# Update was not successful because of Filesystem I/O Error: Not enough space and nothing to prune! **URL:** \ **Category:** StartOS Support\ **Created:** [October 11, 2026, 12:31am UTC](https://community.start9.com/t/update-was-not-successful-because-of-filesystem-i-o-error-not-enough-space-and-nothing-to-prune/5835 "2026-10-11T00:31:48Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![salvemundi](https://community.start9.com/letter_avatar_proxy/v4/letter/s/7ba0ec/32.png) [@salvemundi](https://community.start9.com/u/salvemundi)\ **Post date:** [October 11, 2026, 12:31am UTC](https://community.start9.com/t/update-was-not-successful-because-of-filesystem-i-o-error-not-enough-space-and-nothing-to-prune/5835/1 "2026-10-11T00:31:48Z")
Trying to upgrade from 0.4.0.1 to 0.4.0.2 on a Raspberry PI with 2TB external SSD with these ‘Storage’ stats taken from the WebUI ‘Metrics’ page: Percentage used 46.4% Capacity 1995.67 GB Used 925.52 GB Available 1070.14 GB Running Bitcoin Core (full node), ToR, Gitea, and Vaultwarden at the moment Happy to provide any CLI output that would be helpful, of course. Thanks! ---
**Author:** ![StuPleb](https://community.start9.com/user_avatar/community.start9.com/stupleb/32/195_2.png) [@StuPleb](https://community.start9.com/u/StuPleb)\ **Post date:** [October 11, 2026, 8:13am UTC](https://community.start9.com/t/update-was-not-successful-because-of-filesystem-i-o-error-not-enough-space-and-nothing-to-prune/5835/2 "2026-10-11T08:13:26Z")
The storage figures on the Metrics page are for the part of your drive that holds your services and their data. An update needs room somewhere else: a small separate area where StartOS keeps its own system files. It has to fit the new version next to the current one, plus about 1 GB to spare, and the error means it couldn’t find that room even after clearing out older versions. On a Raspberry Pi, that area is supposed to grow to about 16 GB the first time the server starts. On some Pis it only half happened: the space was set aside, but the filesystem inside it stayed at its original size of around 1.6 GB, which is too small for any update. That’s a bug on our side. 0.4.0.2 fixes it for new installs, but a server that’s already running needs a one-time fix, and that’s most likely what’s stopping yours. To check, connect to your server over SSH as `start9` with your master password and run: ```auto df -h /media/startos/images ``` If the **Size** column shows roughly 1.6G, run this to grow the filesystem to fill its space. It’s safe to run while everything is running and doesn’t touch your services or data: ```auto sudo btrfs filesystem resize max /media/startos/config ``` Run the `df` command again and Size should now be close to 16G. Then try the update again from the web interface. If Size already showed something much larger than 1.6G, don’t run the resize. Paste the output of `df -h /media/startos/images` and `lsblk` here instead. ---
**Author:** ![salvemundi](https://community.start9.com/letter_avatar_proxy/v4/letter/s/7ba0ec/32.png) [@salvemundi](https://community.start9.com/u/salvemundi)\ **Post date:** [October 11, 2026, 3:33pm UTC](https://community.start9.com/t/update-was-not-successful-because-of-filesystem-i-o-error-not-enough-space-and-nothing-to-prune/5835/3 "2026-10-11T15:33:36Z")
@StuPleb Nice one shot! My Pi had the the 1.6 GB /media/startos/images partition. The btrfs resize worked and I was able to successfully update to 0.4.0.2. Thanks! Currently running a backup and then will be upgrading the services since they all show updates available. Again, thank you! ---
**Author:** ![system](https://community.start9.com/uploads/default/original/1X/2dcde8aa6ad3ce3d7873096ee4b3e5395e19a7b5.png) [@system](https://community.start9.com/u/system)\ **Post date:** [October 13, 2026, 3:34pm UTC](https://community.start9.com/t/update-was-not-successful-because-of-filesystem-i-o-error-not-enough-space-and-nothing-to-prune/5835/4 "2026-10-13T15:34:01Z")
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.