Stefan Agner

Let's start with the fsck units explicitly. There should be two different repairs, one for the OS partitions (unhealthy `os_filesystem_check_error`): ``` systemd-fsck@dev-disk-by\x2dlabel-hassos\x2dboot.service systemd-fsck@dev-disk-by\x2dlabel-hassos\x2doverlay.service ``` And one for the data partition...

> The Supervisor's internal DNS resolver (`172.30.32.1`, which uses dnsmasq) The Supervisor does not use dnsmasq The Supervisor by default uses the DNS plug-in (separate container), which runs CoreDNS. >...

Why do I have the feeling I am talking to an AI 🤔 This is the issue tracker of Supervisor, if you feel this is a bug in Core, then...

On Sentry, the issues mainly appear around Supervisor releases (since a restart of Supervisor causes an add-on start attempt): https://home-assistant-io.sentry.io/issues/4606322517/events/9bc4628e3a4c43298bf3294531e7cf3f/?end=2025-11-04T13%3A33%3A00&start=2025-11-03T18%3A36%3A00

This is something in between a bugfix and a breaking change. Depending on how the client which is using JSON or URL encoded authentication is coded, this change might lead...

Let's go for Option 2 here, this seems much cleaner to me and limits the changes to Core.

Yeah we have two connectivity check active, the one running in Supervisor, which essentially tells us if connectivity works in containers (which use the CoreDNS DNS service), and the other...

> Is my assumption correct that the GET call is from resolvd and that the supervisor requests a AAAA record and fails to do the HEAD call, but that the...

> I managed to fix this in my system. I logged in using remote access (via internet) and then enabled wifi interface in system settings. @chrisgorgo so you've enabled WiFi...

@Krojack @ptrtech1 the original post and most issues reported in here seem to be network related, where seemingly HAOS/NetworkManager lost connection information. Your issue look more like you are hitting...