Closed mmaura closed 1 month ago
This doesn't seem right - /mnt/data
should be a writable ext4 partition with commit mount option set to 30 seconds - so even in case of an unexpected power loss, all data older than 30 should be written to the disk.
Can you elaborate a bit more about what are you trying to achieve, how you access HAOS (are you using direct host access or SSH at 22222) and what changes exactly are lost?
Anyway, please note that using direct access for any system modifications is discouraged - HAOS itself is designed as a special purpose OS with a limited features, if you want to leverage your HA instance for anything beyond that, you should look into how add-ons work.
I noticed that the mini PC's fan was running at maximum speed constantly. So, I decided to offload some functions that are installed as add-ons to other systems. I accessed the system via SSH on port 22222 to retrieve the configuration of the add-ons using rsync, and then uninstalled nginxproxymanager, vaultwarden, timescaledb, and adguardhome. Since I moved the reverse proxy and the database, I also had to modify the configuration.yaml file. But every time I reboot the PC, everything goes back to the way it was before I did all this.
My first thought was that the M2 had reached its maximum write limit, but I don't see any kernel error messages in the dmesg file. And the smartctl tools are not available on hassos. I then thought about RAUC, but the data partition is not part of it. I wondered if there could be another caching system, but from reading your response, I understand that there isn't.
I made a backup via NFS, changed the disk, reinstalled hassos, and restored the backup. Everything is working normally. Thank you for helping me.
Describe the issue you are experiencing
Hello,
Since I wanted to update HAOS 12.3, all the updates I make are canceled each time I restart and the system still offers all available updates. The "/mnt/data" partition returns to its previous state and changes to the file system are lost. With each reboot (every day), I have to manually replicate the configuration changes and the new database address of the "recorder ". How to manually persist the partition ?
What operating system image do you use?
generic-x86-64 (Generic UEFI capable x86-64 systems)
What version of Home Assistant Operating System is installed?
12.2
Did you upgrade the Operating System.
Yes
Steps to reproduce the issue
1. 2. 3. ...
Anything in the Supervisor logs that might be useful for us?
Anything in the Host logs that might be useful for us?
System information
System Information
Home Assistant Community Store
GitHub API | ok -- | -- GitHub Content | ok GitHub Web | ok GitHub API Calls Remaining | 4894 Installed Version | 1.34.0 Stage | running Available Repositories | 1453 Downloaded Repositories | 19Home Assistant Cloud
logged_in | false -- | -- can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | okHome Assistant Supervisor
host_os | Home Assistant OS 12.2 -- | -- update_channel | stable supervisor_version | supervisor-2024.06.0 agent_version | 1.6.0 docker_version | 25.0.5 disk_total | 116.7 GB disk_used | 26.5 GB healthy | true supported | failed to load: Unsupported board | generic-x86-64 supervisor_api | ok version_api | ok installed_addons | ESPHome (2024.4.2), AdGuard Home (5.0.7), Studio Code Server (5.15.0), Terminal & SSH (9.13.0), FTP (5.0.2), Mosquitto broker (6.4.0), Zigbee2MQTT (1.37.0-1), Z-Wave JS (0.5.0), Joplin Server (2.14.2), Nginx Proxy Manager (1.0.1), Portainer (2.20.1), Piper (1.5.0), Whisper (2.0.0), openWakeWord (1.10.0), Rhasspy 3 (en) (0.0.4), porcupine1 (1.2.0)Dashboards
dashboards | 5 -- | -- resources | 14 views | 16 mode | storageRecorder
oldest_recorder_run | 25 août 2023 à 04:02 -- | -- current_recorder_run | 12 juin 2024 à 08:25 estimated_db_size | 5757.04 MiB database_engine | postgresql database_version | 16.3Additional information
The installation is marked unbearable because of Portainer which I use to run "mys2mqtt" to control MySensors.