-
-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🐛 [SambaNAS] repair appears with every host reboot and needs manual reload input #219
Comments
HA Supervisor 2024.04.2 should fixed the proble. Try it and report if persists |
I will test as soon i receive the update because this is a major issue for me |
i updated the Supervisor to 2024.04.4 a few minutes ago but the issue still persists |
A few minutes ago I restarted it two times and the issue vanished completely |
In the last beta version of -nas3 I try to change boot sequence to ensure ha core is up before ask them to mount drive. But if you don't have updated to the last beta version is not my work. L. |
that's not possible because if it was a retry an error would appear at least once but there's absolutely nothing |
also can confirm that i did not update because i'm still on nas2 |
problem has returned |
probrably was "solved" because the drive disapeared from the network share so nothing has actually changed |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Addon
SambaNAS
Description
every time the host is rebooted a repair appears that asks to try a reload (manual button press needed) it wuold be possible to create an automation that reload the share automatically?
Reproduction steps
1. rebbot the host 2. repair appears 3. solved if manually reload
Addon Logs
Addon Config
Architecture
amd64
OS
HaOS
The text was updated successfully, but these errors were encountered: