home-assistant[bot]
commented
2 weeks ago Hey there @home-assistant/supervisor, mind taking a look at this issue as it has been labeled with an integration (hassio) you are listed as a code owner for? Thanks!
Code owner commands
Code owners of `hassio` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign hassio` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.(message by CodeOwnersMention)
hassio documentation hassio source (message by IssueLinks)
The problem
See prior stale and closed issues on this topic.
Network storage has no option for a hard mount (do nothing until the mount works) or making add-ons (ie: Scrypted video storage) or backups depend on network storage. Worse, there is no way for backups to warn that they are not writing to network storage and they'll happily write to the directory where the mount should be with no notice.
My Synology is slower to boot than my HA NUC, causing the NFS mount to fail after an extended power outage and backups to write to the HA disk instead of over NFS, due to this bug. I just went through a nerve wracking experience where the SSD inside my HA NUC died with all the backups on it. I managed to get a data recovery service to fix it, but still, if this bug was not present, I would have had backups on my Synology.
Manual intervention every time the HA server reboots is not a fix, it is a workaround that doesn't always work. Right now, the storage feature of HA is useless because of this bug. On top of that, if the mounts don't succeed, and their directories get written to, they will never succeed due to data being in the directories. In order to fix this, you have to bash into the supervisor docker and remove them. Not really a user friendly way of repair.
What version of Home Assistant Core has the issue?
core-2024.6.3
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Supervisor
Link to integration documentation on our website
No response
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response