Will it not work now?
I am on Proxmox 7 and can create on local-lvm but not on my NFS storage?
I have a pool of 5 ProxMox hosts so would prefer to run on shared storage but it fails to create the VM
Any idea or is this still a V7 issue
Ziptbm,
I am having a similar issue, after becoming completely full I deleted and restored my HA vm on proxmox and it is growing rapidly again. Have you found anything yet that was causing the storage to fill up?
Cheers
how big is your home assistant V2 db? If you aren’t limiting your logging, the db can grow huge.
I have wondered that myself and checked and it was less than 2gb.
I used whiskerz007 install script and wondering if I didn’t follow it correctly.
To resize the disk after the first boot
- At the root prompt type
df -h /dev/sda8
and note theSize
- Shutdown the VM
- Resize the disk to the desired size
- At the root prompt type
sgdisk -e /dev/sda
- At the root prompt type
reboot
- Verify resize was successful by typing
df -h /dev/sda8
at the root prompt
New VM install, before starting I increase memory, processor and disk size, start VM and then type the first command and note the size (the size I changed the disk to). Next I type second command, reboot, use the first command again and it’s still the size I changed it to before bootup.
Is that all correct?
In my fork of the script, It sets the disk size to 32gb during VM creation. Then all that’s needed to be set is Memory and Processors.
Hi,
I’m freaking out, if you know how to, because local-lvm grow up every day and i didn’t figure out to fix this.
I used this script GitHub - whiskerz007/proxmox_hassos_install
Please can you show us how to fix this, forever?
I think you need to set recorder to purge after X days in configuration.yaml:
recorder:
purge_keep_days: 5
another exampe…in configuration.yaml
recorder:
purge_interval: 2
purge_keep_days: 2
exclude:
entities:
- sensor.date_time
- sensor.icloud3_event_log
entity_globs:
- sensor.abc-*
- sensor.abc_*
- device_tracker.abc_*
- switch.*
- sun.*
- media_player.*
I have
recorder:
purge_keep_days: 1
and anyway grow up.
So isn’t the solution, every day grow up without a reason.
Maybe is the script that install HA ?
InfluxDB but for now i didn’t use it, maybe is influx ? i see that grow up always at:
2:00pm and 2:00 am
All the script does is pull and install HA and apply some settings in Proxmox, it has nothing to do with the configuration files of HA.
I have only a vm in proxmox with HA, and local-lvm grow up every day at 2:00 pm and am
I didn’t create other vms, and also if i delete HA vm, local-lvm become empty, so is HA vm that have something that make local-lvm grow up, right?
Anyone note any issues or gotchas upgrading to Proxmox 7? I know I don’t have to upgrade, but I got the itch.
Thanks! And yes, no warnings or failures noted. Assuming it’s probably OK but curious for others experience.
EDIT: the in place upgrade process was painless for me!
This is my recorder
config. Adjust to suit your needs. This keeps my DB file at, or under 2gb.
recorder:
db_url: !secret maria_db
purge_keep_days: 7
include:
domains:
- sensor
- binary_sensor
- switch
- light
- device_tracker
- vacuum
- group
- input_boolean
- cover
- person
- counter
- timer
- climate
exclude:
event_types:
- service_removed
- service_executed
- platform_discovered
- homeassistant_start
- homeassistant_stop
- feedreader
- service_registered
- call_service
- component_loaded
- logbook_entry
- system_log_event
- automation_triggered
- script_started
- timer_out_of_sync
31/07 @ 02:00pm was 23,77GB
01/08 @ 02:00am is 24,13GB
So grow up
Discard for hard drive
Every day at 02 am and pm, grow up
i didn’t set up backup in proxmox for now, some weeks ago i did it in usb, not in local, anyway for now are disabled.
And i make backup only inside Home Assistant in google drive, and i didn’t keep any backup in local.
There is only this one that doesn’t have also the right time 02:00 am or pm, and if i delete it, change nothing
This is my db and isn’t big, and i setup only 1 day
recorder:
purge_keep_days: 1
You figure out how to ?