Hello,
I am running HASSOS on Hyper-V (Windows 10).
HASSOS is running out of space.
I have expanded the volume to 32gb.
According to the documentation, HASSOS should extend partitions automatically.
How can I manually extend the partitions to take advantage of the unallocated space?
df shows that /dev/sda8 is 80% full.
fdisk -l gives no output?
Thanks for your help in advance.
Thanks for your help in advance.
Restarted already?
I found the solution.
My VHDX disk was configured as 32GB dynamically expanding but was physically 6GB.
I downloaded a Ubuntu installation ISO and attached that to my HASSOS VM and booted into Ubuntu.
I ran Gparted and saw that Ubuntu did not recognize that the disk is dynamically expandable.
I then went to the settings of the HASSOS VM and selected to edit the Hard Drive.
I converted the Hard disk to VHD fixed-sized disk.
I then converted the fixed-sized VHD disk to a fixed-sized VHDX disk and then created a new HASSOS VM.
When started HASSOS automatically recognized the free space and used it.
Just want to contribute with my experience – and solution (after lots of frustration) of my problem very much related to this.
My HA got some updates and could not install them. It gave me the error:
> 21-01-07 16:14:25 ERROR (SyncWorker_3) [supervisor.docker.interface] Can't install homeassistant/qemux86-64-homeassistant:2021.1.0 -> 404 Client Error for http+docker://localhost/v1.40/images/homeassistant/qemux86-64-homeassistant:2021.1.0/json: Not Found ("no such image: homeassistant/qemux86-64-homeassistant:2021.1.0: No such image: homeassistant/qemux86-64-homeassistant:2021.1.0").
It turned out that I got the error because the disk had not enough free space to download the update.
I’m running HA on a Windows server 2016 Hyper-V virtual machine using a dynamically expandable VHDX-disk.
I tried to expand the disk using the “Edit disk…”-wizard in Hyper-V Manager. According to the Hyper-V Manager, the disk had then expanded as it should, but HA was not aware of that.
It turns out, that the problem was that if my Hyper-V VHDX-disk had snapshots, it did not communicate to HA its new size.
I removed all the snapshots and booted the virtual machine. HA immediately recognized the new space and – ta-da!! HA updated as it should, and problem solved!