Cant update, not enugh disk space

[Frankness]

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.

[robertklep]

It looks like your VM only provides 8GB of storage? Looking at the Proxmox install script, Athom seems to suggest at least 16GB.

[Frankness]

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

[robertklep]

Have you tried to install additional commands using apt?

[Anoniemand]

Whats the output from df -h? Maybe a filesystem is full and needs to be expanded.

[MCV64]

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)

[Frankness]

[Frankness]

been trying to. and trying to use this guide Ubuntu 20.04: How to Extend Partition (For Noobs) | Cloudron Forum 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

[Anoniemand]

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:

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/sda1). 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.

[MCV64]

@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?

[Anoniemand]

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

[MCV64]

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

[MCV64]

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)

[Frankness]

tanks for the guide. now i am getting this

[Frankness]

thanks this helped me for now to

[robertklep]

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.

[MCV64]

Thanks for the tips! Will be a nice job for the weekend