I am having disk space issues and was hoping someone could help me determine the cause, or correct me if I am wrong!
I am running HomeAssistant in Virtual Box. Currently have Home Assistant Core 111.4. Supervisor latest version 228, HassOS 4.10. However I had this same issue with the prior version before upgrading about a week ago too.
Originally I set the virtual disk up with 32 GB, but one morning after an unexpected reboot, I had issues getting HomeAssistant started. It would go to the Hassos boot menu showing:
1. Auto Boot
2. Boot System 0
3. Boot System 1
After some digging, I found it might be related to my disk space. Looking at the virtual media manager in virtual box, it showed that I had taken up the entire 32 GB allotted. I upped this Virtual Size to 64 GB and rebooted. This appeared to fix my boot issues, and I haven’t seen the boot menu since.
However, I still don’t know what caused the problem. This all happened about 2 weeks ago. I took a look again today and the actual size of my virtual disk is now 37.34 GB. My concern is in a few months I will be back in the same boat with a full virtual disk.
What I’ve tried:
1. I looked through a few threads like these:
Following the recommendations in these other threads:
2. I ran the
df -h command shows that the available size is 62.3G but only 8.1G is used:
du -hs command shows only 1.7G taken
4. Again from the SSH Terminal Addon I also tried
ha su repair. I don’t believe i saw any noticeable change in disk size. Maybe this is because this was run from within Home Assistant?
5. I also pulled the VDI image up in PowerISO to poke around.
The partitions within the VDI image show hassos-data is the largest partition.
From within that hass-os data partition, it only shows that 10.5GB are taken up:
- The docker folder is 7GB (7,516,837,685 bytes)
- My overlays2 folder within the docker folder is the bulk of that at 7GB total.(7,503,213,066 bytes)
- The logs folder is 1.8 GB
- The Supervisor folder is 1.7 GB
- My database file is only 1.2 GB within the supervisor folder.
Current information shown on the VirtualBox Media Manager: