Not enough space

Hello everyone

I had an old computer lying around at home and thought I’d try experimenting with Home Assistant.

After doing a lot of reading to figure out how to install it, since it doesn’t have UEFI BIOS…I finally managed to get it started.

The problem I’m having now is that when I go to http://homeassistant.local:8123/ and the installation starts, it immediately gives me an error “no space left on device” when I have 200 GB of free space on the disk.

I’m not really sure which partition, from sda1 to sda9, should I need to expand.

Can you give me a hand?

Thank you very much

Tell us how you are installing it? Whay guide you are following etc.

But more importantly why do have 9 partitions on your hard drive.

Maybe he being using like ChromeOS Flex, that do a lot of partitions on the disk.

Maybe he could just remove all partions and start fresh.

I, too, don’t understand the reason for all the partitions. If you do, more power to you. I think something went Fubar during your installation.

If you have virtualization turned on in BIOS, at least 8 gigs of RAM and at least four cores for your processor. I’d recommend installing HA in a virtual box under Ubuntu.

Instructions for installing Ubuntu are on the Ubuntu page.

For installing in a virtual box, see the ha documentation that says installing in Linux.

HAOS create +8 partitions

Please share lsblk -o+FSTYPE,LABEL,MODEL from the CLI. You might have to enter login first.

Proxmox VE is a much better option.

Example of an HA-OS VM with a 32 GB virtual hard disk.
All partitions have fixed sizes, with the exception of sda8.
sda8 is normally expanded to the maximum available space when HA-OS is started for the first time.

# lsblk
NAME   MAJ:MIN RM  SIZE RO TYPE MOUNTPOINTS
sda      8:0    0   32G  0 disk
|-sda1   8:1    0   32M  0 part /mnt/boot
|-sda2   8:2    0   24M  0 part
|-sda3   8:3    0  256M  0 part
|-sda4   8:4    0   24M  0 part
|-sda5   8:5    0  256M  0 part /
|-sda6   8:6    0    8M  0 part
|-sda7   8:7    0   96M  0 part /var/lib/systemd
|                               /var/lib/bluetooth
|                               /var/lib/NetworkManager
|                               /root/.docker
|                               /root/.ssh
|                               /etc/udev/rules.d
|                               /etc/systemd/timesyncd.conf
|                               /etc/modprobe.d
|                               /etc/usb_modeswitch.d
|                               /etc/hosts
|                               /etc/sysctl.d
|                               /etc/modules-load.d
|                               /etc/hostname
|                               /etc/dropbear
|                               /etc/default
|                               /etc/NetworkManager/system-connections
|                               /mnt/overlay
`-sda8   8:8    0 31.3G  0 part /var/log/journal
                                /var/lib/docker
                                /mnt/data
zram0  252:0    0    0B  0 disk
zram1  252:1    0   32M  0 disk
zram2  252:2    0   16M  0 disk /tmp

I have followed the instructions here.

I’ve booted up Ubuntu Desktop in trial mode.

After that, since the system wouldn’t boot up, i used this instructions

** se gparted to create a small ext4 partition on the HassIO drive. I’m assuming it’s /dev/sda. It’ll probably tell you that the partition table doesn’t include the whole disk and offer to fix it. Let it. A 10MB partition should be fine. Tell gparted to leave 0 bytes after the partition so it ends up at the end of the disk. That way HassIO will be able to resize its partitions and use all the unallocated space.

Note: You may end up with a tiny bit of unallocated space after this partition even if tell gparted to make it 0. That’s due to alignment. Don’t worry about it.

Mount the new partition (should be sda9 but check):

sudo mount /dev/sda9 /mnt

Install GRUB on the new partition. If you’re using Parrot OS you’ll need to install the GRUB package first:

sudo apt install grub2

Then install GRUB onto the HassIO drive. Replace /dev/sda with your device if different:

sudo grub-install --compress=xz --root-directory=/mnt /dev/sda --force

Now that GRUB is installed, all that’s left is to configure it to redirect to the HassIO installation. Run the following to create the necessary config file in /mnt/boot/grub/grub.cfg (the first line tells it to use the first partition on the first drive, the second tells it where HassIO’s GRUB config file is):

cat <<! | sudo dd of=/mnt/boot/grub/grub.cfg
set root=(hd0,1)
configfile /efi/boot/grub.cfg
!

Remove the boot media and reboot. You should go straight to the HassIO boot menu.
**

Now the systems boots up, but when I try to complete installation using homeassistant.local:8123, the “not free space” appears.

Thank you

Maybe i should expand sda8 before create sda9 qith grub to allow non uefi boot…

I Believe this is where it went wrong , Where is this instruction from ?

From this forum

Install HA on old laptop without UEFI - Configuration - Home Assistant Community

you deviated from this with instructions from an aged thread? :up_arrow:

What laptop is it?

As LiQuid above ask, Please read that Topic you refers to … to the END

I don’t know because i never tried installing HA-OS on non UEFI capable machine.

Here’s another instruction.

Maybe a 32bits, as the majority of old efi Devices are

I was curious about the access to the hard drive and available USB ports.

I’d recommend you either use the docker installation method or virtualize HAOS. Depends on the exact hardware you have. Otherwise try to extend hassos-data first. Just know that this setup/environment is unsupported.

Solved.
I have expanded the sda8 partition – Data, more than 5 Gb and now all runs correctly

Thank you for your support