After updating the ADM version from ADM 5.0.0.RFP3 to ADM 5.0.0.RHJ2 on the Asustor AS6404T, I can no longer access the Home Assistant page.
Home Assistant version from Asustor’s App Central: 2025.2.0.r01
After accessing the page:
The website is not available
The following appears repeatedly, one after the other, in “home-assistant.log.1”.
2025-05-07 04:31:37.689 ERROR (MainThread) [homeassistant.components.bring.coordinator] Unexpected error fetching bring data
Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py”, line 380, in _async_refresh
self.data = await self._async_update_data()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/src/homeassistant/homeassistant/components/bring/coordinator.py”, line 80, in _async_update_data
items = await self.bring.get_list(lst.listUuid)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/local/lib/python3.13/site-packages/bring_api/bring.py”, line 310, in get_list
raise BringAuthException(
…<2 lines>…
)
bring_api.exceptions.BringAuthException: Loading list items failed due to authorization failure, the authorization token is invalid or expired.
Can I reset everything but keep the database?
Does anyone have a solution?
Same problem updated from some version 4 to 5.0.0.RHJ2 a day ago and Home Assistant Docker for Asustor stops working. So I reinstalled it (very simple config no big loss)… at last I try. But HA container cant start with shown by Portainer:
“Failed starting container:
failed to create task for container:
failed to create shim task:
OCI runtime created failed:
runc create failed:
unable to start container process:
error during container init:
chmod /dev/console:
read-only file system: unknown.” shown in one liner but I thing error ends with colon :
I only found that in shim task do not start and initialise container nothing will work. So I even do not get any Home Assistant file written to Docker folder. (Portainer reinstall rewriting file with out problem so it probably isint folder permissions issue.)
Any clue how to make it work or debug? Except ADM 5 broke some dependences.
Portrainer shows HA container as failed to start, if I try to start it manually:
Failure
Failed starting container: failed to create task for container:
failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: chmod /dev/console: read-only file system: unknown
Hello Sir Goodenough, no, the IP is the same, nothing has changed. Just the Asustor firmware. DNS is working. No Pihole, Adguard, or anything else, just the Fritbox. Vaultwarden is running stable even after the update. I’m already considering deleting the Docker directory and trying to reinitialize Homeassistant. Maybe I can copy the old database there?
It’s really a problem.
HA container did not work anymore on asustor NAS using last docker engine provided by Asustor…
Same error message
Help needed
Thanks in advance
I had the same problem after updating to 5.0.0.RHJ2.
In my case helped doing the following:
Using Portrainer CE for Home-Assistant container change access rights for Bind “/dev” from Read-Only to Writable.
To do so, open container details (click on container), then edit container using Dublicate/Edit button and at Advanced container settings (volumes tab) change access rights for “/dev” from Read-Only to Writable. Then deploy container with replacement. After that container should immediately change state to Running.
