Unable to Start Matter Server (or uninstall it)

[BlueMoon23]

Describe the issue you are experiencing

On restarting home assistant, I am unable to restart my matter server and have the following logs:

code: 'ERR_MODULE_NOT_FOUND',
url: 'file:///app/node_modules/@matter/node/dist/esm/behavior/internal/ServerBehaviorBacking.js'
}
Node.js v24.19.0
[18:52:56] WARNING: matter-server service exited with code 1 (by signal 0).

Advice from copilot is to delete the matter server app, delete the file core_matter_server, reboot and re-install the matter server app. However, after every reboot the matter server app is there with the same problem (so I can't re-install). It looks like copilot is suggesting a reinstall to allow the missing file to be uploaded, however the HA behaviour seems to be preventing this.

What type of installation are you running?

Home Assistant OS

Which operating system are you running on?

Home Assistant Operating System

Which app are you reporting an issue with?

Matter Server

What is the version of the app?

9.2.0

Steps to reproduce the issue

1. I can't get rid of the issue, I can't start or uninstall the matter server.

...

System Health information

There are no repairs pending.

Anything in the Supervisor logs that might be useful for us?

Anything in the app logs that might be useful for us?

Additional information

No response

[Apollon77]

@agners Any idea? Seems like a broken image

[BlueMoon23]

@agners Any idea? Seems like a broken image

I'm not sure, I tried restoring from a good backup (prior to the problem) and I still have the same issue.

[agners]

The symptoms described here indicate local corruption of the Docker image storage. This typically happens when the system loses power or is reset while Docker writes an image to disk, or due to failing storage. Docker verifies image checksums only while pulling — once an image is written to disk, its integrity is not checked again, so such corruption can stay dormant until the affected container is recreated (e.g. on a host reboot).

Note that deleting and re-pulling the affected image does not necessarily help: image layers are shared between images and reused across versions, and docker pull skips layers it believes are already present locally.

To recover, make a full backup, download it, then reinstall Home Assistant OS and restore the backup. A dedicated feature to reset the Docker image storage is tracked in#6555.

---

It looks like copilot is suggesting a reinstall to allow the missing file to be uploaded, however the HA behaviour seems to be preventing this.

It is not HA which prevents this, it is Docker. The layer sharing/caching prevents a full (forced) redownload/rewrite of container images, unfortunately 😢 .

[BlueMoon23]

The symptoms described here indicate local corruption of the Docker image storage. This typically happens when the system loses power or is reset while Docker writes an image to disk, or due to failing storage. Docker verifies image checksums only while pulling — once an image is written to disk, its integrity is not checked again, so such corruption can stay dormant until the affected container is recreated (e.g. on a host reboot).

Note that deleting and re-pulling the affected image does not necessarily help: image layers are shared between images and reused across versions, and docker pull skips layers it believes are already present locally.

To recover, make a full backup, download it, then reinstall Home Assistant OS and restore the backup. A dedicated feature to reset the Docker image storage is tracked in#6555.

It looks like copilot is suggesting a reinstall to allow the missing file to be uploaded, however the HA behaviour seems to be preventing this.

It is not HA which prevents this, it is Docker. The layer sharing/caching prevents a full (forced) redownload/rewrite of container images, unfortunately 😢 .

Thanks, I'll try this when I return home next week.