# Cant update, not enugh disk space **URL:** \ **Category:** Homey Self-Hosted Server\ **Created:** [April 1, 2026, 10:43am UTC](https://community.homey.app/t/cant-update-not-enugh-disk-space/153231 "2026-04-01T10:43:45Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![Frankness](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/frankness/32/121586_2.png) [@Frankness](https://community.homey.app/u/Frankness)\ **Post date:** [April 1, 2026, 10:43am UTC](https://community.homey.app/t/cant-update-not-enugh-disk-space/153231/1 "2026-04-01T10:43:45Z")
I cant update my homey shs it say not enugh disk space. Well i know i dont have enugh. due to “other eating up my disk” and thats apparently normel when i ask for help about it. so please tell me how to update my homey shs when other is taking up all space. ![Uden titel](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/7/8/780c5a04ec02ce4dc3f80a75837e25bd010ddb37.jpeg) ![Skærmbillede 2026-04-01 123748](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/0/a/0aaa08b96269a9843c2f22fdbec35136d1b37d1e.jpeg) ![Skærmbillede 2026-04-01 123718](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/f/6/f6b101aae249eb6e1f714e23b6ecdb861c339ecf.jpeg) ---
**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\ **Post date:** [April 1, 2026, 12:04pm UTC](https://community.homey.app/t/cant-update-not-enugh-disk-space/153231/2 "2026-04-01T12:04:08Z")
It looks like your VM only provides 8GB of storage? Looking at the Proxmox install script, Athom seems to suggest at least 16GB. ---
**Author:** ![Frankness](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/frankness/32/121586_2.png) [@Frankness](https://community.homey.app/u/Frankness)\ **Post date:** [April 1, 2026, 1:44pm UTC](https://community.homey.app/t/cant-update-not-enugh-disk-space/153231/3 "2026-04-01T13:44:06Z")
In VMware homey have 20gb. But can’t figure out how to expand inside Homey. Did try the guide to Homey pro 2023 but it say parted is a uknown Command ---
**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\ **Post date:** [April 1, 2026, 2:00pm UTC](https://community.homey.app/t/cant-update-not-enugh-disk-space/153231/4 "2026-04-01T14:00:46Z")
Have you tried to install additional commands using `apt`? ---
**Author:** ![Anoniemand](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/anoniemand/32/120697_2.png) [@Anoniemand](https://community.homey.app/u/Anoniemand)\ **Post date:** [April 1, 2026, 4:47pm UTC](https://community.homey.app/t/cant-update-not-enugh-disk-space/153231/5 "2026-04-01T16:47:15Z")
Whats the output from `df -h`? Maybe a filesystem is full and needs to be expanded. ---
**Author:** ![MCV64](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mcv64/32/29783_2.png) [@MCV64](https://community.homey.app/u/MCV64)\ **Post date:** [April 2, 2026, 5:56pm UTC](https://community.homey.app/t/cant-update-not-enugh-disk-space/153231/6 "2026-04-02T17:56:44Z")
In fact, i’m running into the same problem, dev/sda1\* 100% used, overlayfs (“Other” indeed also taking up roughly 6-7 GB). Also happened after trying to update. I have plenty of space on the vmware vm, but not confident enough how to expand the filesystem within homey-shs as it seems it is the boot image. Any help would really be appreciated. (i have enlarged the disk of the vm already) ---
**Author:** ![Frankness](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/frankness/32/121586_2.png) [@Frankness](https://community.homey.app/u/Frankness)\ **Post date:** [April 2, 2026, 7:28pm UTC](https://community.homey.app/t/cant-update-not-enugh-disk-space/153231/7 "2026-04-02T19:28:20Z")
![Skærmbillede 2026-04-02 212707](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/3/7/378a9b749f28a35a59f1c6cec68063081623d6e9.jpeg) ---
**Author:** ![Frankness](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/frankness/32/121586_2.png) [@Frankness](https://community.homey.app/u/Frankness)\ **Post date:** [April 2, 2026, 7:31pm UTC](https://community.homey.app/t/cant-update-not-enugh-disk-space/153231/8 "2026-04-02T19:31:01Z")
been trying to. and trying to use this guide [Ubuntu 20.04: How to Extend Partition (For Noobs) | Cloudron Forum](https://forum.cloudron.io/topic/6086/ubuntu-20-04-how-to-extend-partition-for-noobs) but really dont want to remove sda1 for then get i back. starting to think its easier to create a backup and then make a new homey shs in vmware ---
**Author:** ![Anoniemand](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/anoniemand/32/120697_2.png) [@Anoniemand](https://community.homey.app/u/Anoniemand)\ **Post date:** [April 2, 2026, 8:04pm UTC](https://community.homey.app/t/cant-update-not-enugh-disk-space/153231/9 "2026-04-02T20:04:49Z")
I think these should be the right steps, no delete involved, only resize (both partition and filesystem). 1. Backup. → Create a snapshot of the VM (just in case) 2. install parted: `apt update && apt install -y parted` 3. execute parted with the device as argument (in your case /dev/sda): `parted /dev/sda` 4. Type `print`, you should see something like this: ```auto Model: VMware Virtual disk (scsi) Disk /dev/sda: 21.5GB Sector size: 512B Partition Table: msdos Number Start End Size Type File system Flags 1 1049kB 8590MB 8589MB primary ext4 boot ``` Notice the disk size (21.5 GB) and the partition size (8589 MB). This means you could increase the size of the partition, which brings us to the next step. 5. Type the following to resize the partition to maximum: `resizepart 1 100%` The first number is the number of the partition. In this example it’s 1, but it could have another value. In your case it’s 1 @Frankness (/dev/sda **1** ). `100%` means: take all available free unallocated disk space. 6. Exit parted by typing: `quit` 7. Not done yet, the filesystem needs to be increased as well, type resize2fs [filesystem]: `resize2fs /dev/sda1` 8. We should be good now. The filesystem should have increased, confirm via: `df -h` If anything didn’t go as planned, revert the snapshot. ---
**Author:** ![MCV64](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mcv64/32/29783_2.png) [@MCV64](https://community.homey.app/u/MCV64)\ **Post date:** [April 2, 2026, 8:22pm UTC](https://community.homey.app/t/cant-update-not-enugh-disk-space/153231/10 "2026-04-02T20:22:11Z")
> [@Anoniemand](#): > > apt update && apt install -y parted Thanks for the help! But I’ve noticed just now i cannot even install parted anymore, not enough diskspace haha. I start to think to uninstall the whole thing, start fresh, increase first the size , then restore from backup. I’m a bit puzzeled why the docker file as downloaded from Homey is so tight in size? ---
**Author:** ![Anoniemand](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/anoniemand/32/120697_2.png) [@Anoniemand](https://community.homey.app/u/Anoniemand)\ **Post date:** [April 2, 2026, 8:25pm UTC](https://community.homey.app/t/cant-update-not-enugh-disk-space/153231/11 "2026-04-02T20:25:54Z")
Oh nevermind it did only install parted via the earlier command. I need some sleep now 😉 Parted isn’t that large, maybe one of the following helps: APT cache cleanup (start with this one, should be enough) `apt clean` search large files `du -sh /* 2>/dev/null | sort -rh | head -20` cleanup old logs `journalctl --vacuum-size=50M` ---
**Author:** ![MCV64](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mcv64/32/29783_2.png) [@MCV64](https://community.homey.app/u/MCV64)\ **Post date:** [April 2, 2026, 8:34pm UTC](https://community.homey.app/t/cant-update-not-enugh-disk-space/153231/12 "2026-04-02T20:34:58Z")
Thanks again! I now get the error that it can’t have overlapping partitions, which makes sense when thinking about it. Might have to start from scratch after all lol, there goes my weekend lol ---
**Author:** ![MCV64](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mcv64/32/29783_2.png) [@MCV64](https://community.homey.app/u/MCV64)\ **Post date:** [April 2, 2026, 8:59pm UTC](https://community.homey.app/t/cant-update-not-enugh-disk-space/153231/13 "2026-04-02T20:59:10Z")
I think i’ve solved it for now! I was browsing through the filesystem and noticed there were for some reason lots of containers/images. That made no sense so I used the command `docker image prune` . That cleaned up almost 5GB at once. Then restarted, it downloaded and installed the update and all is well now. I wonder where it came from. maybe some earlier failed updates. Anyhow, thanks again for the help! I anyhow want to know more about linux so will install ubuntu soon and will run homey-shs from there (but first make sure it will have plenty of space haha) ---
**Author:** ![Frankness](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/frankness/32/121586_2.png) [@Frankness](https://community.homey.app/u/Frankness)\ **Post date:** [April 2, 2026, 9:14pm UTC](https://community.homey.app/t/cant-update-not-enugh-disk-space/153231/14 "2026-04-02T21:14:05Z")
tanks for the guide. now i am getting this ![Skærmbillede 2026-04-02 230922](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/5/0/50694f1ea223ae19be9c227bfe24d85eded52f78.jpeg) ---
**Author:** ![Frankness](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/frankness/32/121586_2.png) [@Frankness](https://community.homey.app/u/Frankness)\ **Post date:** [April 2, 2026, 9:14pm UTC](https://community.homey.app/t/cant-update-not-enugh-disk-space/153231/15 "2026-04-02T21:14:20Z")
thanks this helped me for now to 🙂 ---
**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\ **Post date:** [April 3, 2026, 4:30am UTC](https://community.homey.app/t/cant-update-not-enugh-disk-space/153231/16 "2026-04-03T04:30:26Z")
The person that created this image apparently doesn’t have a lot of Linux/UNIX experience, placing the main (“boot”) partition _first_ on the disk is asking for trouble since it means you’ll never be able to resize it because it will overlap with the following (“lba”) partition. Also, a separate swap partition is silly nowadays, _especially_ when it’s only 503MB big. And it wouldn’t surprise me if there’s still a `swapfile` somewhere in the boot partition. My suggestion: - (make sure the current image is backed up properly!) - remove the #2 (“lba”) and #5 (“swap”) partitions (they’re useless anyway) - resize the #1 (“boot”) partition - reboot - after rebooting, use `resize2fs` to resize the filesystem I’m not sure if you can perform the second and third step (with `parted`) while the system is running normally (that is, with filesystems/swap mounted). You may also need to run `swapoff` to get Linux to “let go” of the swap partition before removing it. So it might be necessary to boot the VM from a virtual USB device, with something like a live Ubuntu or Debian image. ---
**Author:** ![MCV64](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mcv64/32/29783_2.png) [@MCV64](https://community.homey.app/u/MCV64)\ **Post date:** [April 3, 2026, 6:06am UTC](https://community.homey.app/t/cant-update-not-enugh-disk-space/153231/17 "2026-04-03T06:06:58Z")
Thanks for the tips! Will be a nice job for the weekend 🙂 ---
**Author:** ![Anoniemand](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/anoniemand/32/120697_2.png) [@Anoniemand](https://community.homey.app/u/Anoniemand)\ **Post date:** [April 3, 2026, 1:13pm UTC](https://community.homey.app/t/cant-update-not-enugh-disk-space/153231/18 "2026-04-03T13:13:21Z")
Oh I see now because of sda2 and sda5, I missed that earlier. Yeah like Robert is suggesting. Reinstalling won’t solve the issue, because you’ll get the same partitions back and the same issue (at a time). You can use the following command to backup your homey data to your desktop use Powershell / Terminal / CMD on your Windows computer: `scp -r root@:/root/.homey-shs c:\users\\Desktop\homey-backup` When you want to reinstall Homey SHS you can also use that data to migrate to the new Homey SHS instance. ---
**Author:** ![Dillon\_Standley](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dillon_standley/32/120739_2.png) [@Dillon\_Standley](https://community.homey.app/u/Dillon_Standley)\ **Post date:** [April 9, 2026, 1:52am UTC](https://community.homey.app/t/cant-update-not-enugh-disk-space/153231/19 "2026-04-09T01:52:35Z")
So I don’t know how helpfull this will be but I had the same issue and asked Claude Ai how to increase the storage. It walked me through it which was a good thing because I had no clue how to do it. ---
**Author:** ![MCV64](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mcv64/32/29783_2.png) [@MCV64](https://community.homey.app/u/MCV64)\ **Post date:** [July 18, 2026, 11:30am UTC](https://community.homey.app/t/cant-update-not-enugh-disk-space/153231/20 "2026-07-18T11:30:20Z")
Sorry for opening up this older topic but i’ve noticed that quite often i need to prune those docker images, because otherwise all my storage in homey will be full again. I really wonder why those images appear, is something going wrong with updating maybe? (though it did update to the latest version ). I want to migrate to linux soon for homey but i just really want to know why this happens all the time, it’s like it refuses to delete old images. [Next page](https://community.homey.app/t/cant-update-not-enugh-disk-space/153231.md?page=2)