operating-system icon indicating copy to clipboard operation
operating-system copied to clipboard

Published 20 hours ago • verified publisher icon home-assistant

Systemd 252 breaks usb serial by-id paths

Open paradox460 opened this issue 2 years ago • 6 comments
trafficstars

Describe the issue you are experiencing

When attaching dongles, a reasonable practice is to use the /dev/serial/by-id/<bus>-<serial>-<interface> path, instead of /dev/tty0 and others, that can "move around"

Systemd introduced a bug in 252 that breaks these paths; they simply do not exist on systems running 252, because the udev serial ruleset for them is broken.

This was fixed in https://github.com/systemd/systemd/pull/25246, which added this feature back, and has been backported to systemd 252.1, as well as being included in systemd 253 and newer.

What operating system image do you use?

ova (for Virtual Machines)

What version of Home Assistant Operating System is installed?

11.0

Did you upgrade the Operating System.

Yes

Steps to reproduce the issue

  1. Attach a USB dongle to the host machine, such as a Z-Wave stick
  2. Ensure dongle has proper passthrough configured in the VM
  3. Ensure dongle appears as a /dev/ttyUSB* style device in the guest OS (HAOS)
  4. You will not see the device at /dev/serial/by-id/* path, the /dev/serial/by-id directory is entirely missing

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

23-10-30 09:01:09 INFO (MainThread) [supervisor.resolution.check] Starting system checks with state running
23-10-30 09:01:09 INFO (MainThread) [supervisor.resolution.checks.base] Run check for dns_server_ipv6_error/dns_server
23-10-30 09:01:09 INFO (MainThread) [supervisor.resolution.checks.base] Run check for pwned/addon
23-10-30 09:01:09 INFO (MainThread) [supervisor.resolution.checks.base] Run check for trust/supervisor
23-10-30 09:01:09 INFO (MainThread) [supervisor.resolution.checks.base] Run check for dns_server_failed/dns_server
23-10-30 09:01:09 INFO (MainThread) [supervisor.resolution.checks.base] Run check for security/core
23-10-30 09:01:09 INFO (MainThread) [supervisor.resolution.checks.base] Run check for ipv4_connection_problem/system
23-10-30 09:01:09 INFO (MainThread) [supervisor.resolution.checks.base] Run check for multiple_data_disks/system
23-10-30 09:01:09 INFO (MainThread) [supervisor.resolution.checks.base] Run check for docker_config/system
23-10-30 09:01:09 INFO (MainThread) [supervisor.resolution.checks.base] Run check for free_space/system
23-10-30 09:01:09 INFO (MainThread) [supervisor.resolution.check] System checks complete
23-10-30 09:01:09 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state running
23-10-30 09:01:09 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
23-10-30 09:01:09 INFO (MainThread) [supervisor.resolution.fixup] Starting system autofix at state running
23-10-30 09:01:09 INFO (MainThread) [supervisor.resolution.fixup] System autofix complete
23-10-30 09:01:36 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token






23-10-30 09:31:36 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token






23-10-30 10:01:06 INFO (MainThread) [supervisor.updater] Fetching update data from https://version.home-assistant.io/stable.json
23-10-30 10:01:09 INFO (MainThread) [supervisor.resolution.check] Starting system checks with state running
23-10-30 10:01:09 INFO (MainThread) [supervisor.resolution.checks.base] Run check for dns_server_ipv6_error/dns_server
23-10-30 10:01:09 INFO (MainThread) [supervisor.resolution.checks.base] Run check for pwned/addon
23-10-30 10:01:09 INFO (MainThread) [supervisor.resolution.checks.base] Run check for trust/supervisor
23-10-30 10:01:09 INFO (MainThread) [supervisor.resolution.checks.base] Run check for dns_server_failed/dns_server
23-10-30 10:01:09 INFO (MainThread) [supervisor.resolution.checks.base] Run check for security/core
23-10-30 10:01:09 INFO (MainThread) [supervisor.resolution.checks.base] Run check for ipv4_connection_problem/system
23-10-30 10:01:09 INFO (MainThread) [supervisor.resolution.checks.base] Run check for multiple_data_disks/system
23-10-30 10:01:09 INFO (MainThread) [supervisor.resolution.checks.base] Run check for docker_config/system
23-10-30 10:01:09 INFO (MainThread) [supervisor.resolution.checks.base] Run check for free_space/system
23-10-30 10:01:09 INFO (MainThread) [supervisor.resolution.check] System checks complete
23-10-30 10:01:09 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state running
23-10-30 10:01:09 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
23-10-30 10:01:09 INFO (MainThread) [supervisor.resolution.fixup] Starting system autofix at state running
23-10-30 10:01:09 INFO (MainThread) [supervisor.resolution.fixup] System autofix complete
23-10-30 10:01:36 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token






23-10-30 10:31:37 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token





23-10-30 10:54:31 INFO (MainThread) [supervisor.host.info] Updating local host information
23-10-30 10:54:32 INFO (MainThread) [supervisor.host.services] Updating service information
23-10-30 10:54:32 INFO (MainThread) [supervisor.host.network] Updating local network information
23-10-30 10:54:32 INFO (MainThread) [supervisor.host.sound] Updating PulseAudio information
23-10-30 10:54:32 INFO (MainThread) [supervisor.host.manager] Host information reload completed

23-10-30 11:01:09 INFO (MainThread) [supervisor.resolution.check] Starting system checks with state running
23-10-30 11:01:09 INFO (MainThread) [supervisor.resolution.checks.base] Run check for dns_server_ipv6_error/dns_server
23-10-30 11:01:10 INFO (MainThread) [supervisor.resolution.checks.base] Run check for pwned/addon
23-10-30 11:01:10 INFO (MainThread) [supervisor.resolution.checks.base] Run check for trust/supervisor
23-10-30 11:01:10 INFO (MainThread) [supervisor.resolution.checks.base] Run check for dns_server_failed/dns_server
23-10-30 11:01:10 INFO (MainThread) [supervisor.resolution.checks.base] Run check for security/core
23-10-30 11:01:10 INFO (MainThread) [supervisor.resolution.checks.base] Run check for ipv4_connection_problem/system
23-10-30 11:01:10 INFO (MainThread) [supervisor.resolution.checks.base] Run check for multiple_data_disks/system
23-10-30 11:01:10 INFO (MainThread) [supervisor.resolution.checks.base] Run check for docker_config/system
23-10-30 11:01:10 INFO (MainThread) [supervisor.resolution.checks.base] Run check for free_space/system
23-10-30 11:01:10 INFO (MainThread) [supervisor.resolution.check] System checks complete
23-10-30 11:01:10 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state running
23-10-30 11:01:10 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
23-10-30 11:01:10 INFO (MainThread) [supervisor.resolution.fixup] Starting system autofix at state running
23-10-30 11:01:10 INFO (MainThread) [supervisor.resolution.fixup] System autofix complete
23-10-30 11:01:23 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/esphome/home-assistant-addon repository
23-10-30 11:01:23 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/home-assistant/addons repository
23-10-30 11:01:23 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/hassio-addons/repository repository
23-10-30 11:01:24 INFO (MainThread) [supervisor.store] Loading add-ons from store: 72 all - 0 new - 0 remove
23-10-30 11:01:24 INFO (MainThread) [supervisor.store] Loading add-ons from store: 72 all - 0 new - 0 remove
23-10-30 11:01:37 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token






23-10-30 11:31:37 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token

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

Oct 30 17:48:48 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-e91a8ce87af7750350b42b9674aa65458e06e07a7dc00db41ef34240243df512-runc.s4KeZH.mount: Deactivated successfully.
Oct 30 17:48:49 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-1e2cfcbf015395dd6b7b2f6584c59c6c32a3fad4103b4e4ee52bfec5b347e738-runc.DOBgd5.mount: Deactivated successfully.
Oct 30 17:48:57 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-ae30063642c2fdf7afea1c709c20eec527f0a943bf5360a4262e40ee0f5669fd-runc.263r2K.mount: Deactivated successfully.
Oct 30 17:49:27 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-ae30063642c2fdf7afea1c709c20eec527f0a943bf5360a4262e40ee0f5669fd-runc.wAlJj4.mount: Deactivated successfully.
Oct 30 17:49:28 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-717e6fdc4ff5bfe526ea8444fe41ce6307e6c21fdbc4dec30d6de914855ec5dc-runc.0Cbi56.mount: Deactivated successfully.
Oct 30 17:49:47 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-cfe916de0bece10f2d86a06a565daebcc5d6fb3d0195908f023ce5a00b64375f-runc.MWAjyE.mount: Deactivated successfully.
Oct 30 17:49:49 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-1e2cfcbf015395dd6b7b2f6584c59c6c32a3fad4103b4e4ee52bfec5b347e738-runc.NHCuBN.mount: Deactivated successfully.
Oct 30 17:49:52 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-e91a8ce87af7750350b42b9674aa65458e06e07a7dc00db41ef34240243df512-runc.aFGi70.mount: Deactivated successfully.
Oct 30 17:49:57 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-ae30063642c2fdf7afea1c709c20eec527f0a943bf5360a4262e40ee0f5669fd-runc.ZWoPAt.mount: Deactivated successfully.
Oct 30 17:49:58 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-717e6fdc4ff5bfe526ea8444fe41ce6307e6c21fdbc4dec30d6de914855ec5dc-runc.I0RcfZ.mount: Deactivated successfully.
Oct 30 17:50:18 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-cfe916de0bece10f2d86a06a565daebcc5d6fb3d0195908f023ce5a00b64375f-runc.HgilDE.mount: Deactivated successfully.
Oct 30 17:50:19 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-1e2cfcbf015395dd6b7b2f6584c59c6c32a3fad4103b4e4ee52bfec5b347e738-runc.bylsks.mount: Deactivated successfully.
Oct 30 17:50:27 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-ae30063642c2fdf7afea1c709c20eec527f0a943bf5360a4262e40ee0f5669fd-runc.dTutwv.mount: Deactivated successfully.
Oct 30 17:50:28 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-717e6fdc4ff5bfe526ea8444fe41ce6307e6c21fdbc4dec30d6de914855ec5dc-runc.KUNWvf.mount: Deactivated successfully.
Oct 30 17:50:49 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-1e2cfcbf015395dd6b7b2f6584c59c6c32a3fad4103b4e4ee52bfec5b347e738-runc.csCDl4.mount: Deactivated successfully.
Oct 30 17:50:49 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-cfe916de0bece10f2d86a06a565daebcc5d6fb3d0195908f023ce5a00b64375f-runc.iIjGES.mount: Deactivated successfully.
Oct 30 17:50:56 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-e91a8ce87af7750350b42b9674aa65458e06e07a7dc00db41ef34240243df512-runc.cPtTz5.mount: Deactivated successfully.
Oct 30 17:50:57 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-ae30063642c2fdf7afea1c709c20eec527f0a943bf5360a4262e40ee0f5669fd-runc.E9SQMg.mount: Deactivated successfully.
Oct 30 17:50:58 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-717e6fdc4ff5bfe526ea8444fe41ce6307e6c21fdbc4dec30d6de914855ec5dc-runc.o27R29.mount: Deactivated successfully.
Oct 30 17:51:19 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-1e2cfcbf015395dd6b7b2f6584c59c6c32a3fad4103b4e4ee52bfec5b347e738-runc.LxHQnH.mount: Deactivated successfully.
Oct 30 17:51:20 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-cfe916de0bece10f2d86a06a565daebcc5d6fb3d0195908f023ce5a00b64375f-runc.iyDFmO.mount: Deactivated successfully.
Oct 30 17:51:27 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-ae30063642c2fdf7afea1c709c20eec527f0a943bf5360a4262e40ee0f5669fd-runc.k7ncMj.mount: Deactivated successfully.
Oct 30 17:51:28 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-e91a8ce87af7750350b42b9674aa65458e06e07a7dc00db41ef34240243df512-runc.NGE3cy.mount: Deactivated successfully.
Oct 30 17:51:49 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-1e2cfcbf015395dd6b7b2f6584c59c6c32a3fad4103b4e4ee52bfec5b347e738-runc.mFY2KH.mount: Deactivated successfully.
Oct 30 17:51:51 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-cfe916de0bece10f2d86a06a565daebcc5d6fb3d0195908f023ce5a00b64375f-runc.sXmX0E.mount: Deactivated successfully.
Oct 30 17:51:59 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-717e6fdc4ff5bfe526ea8444fe41ce6307e6c21fdbc4dec30d6de914855ec5dc-runc.vQVq27.mount: Deactivated successfully.
Oct 30 17:52:01 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-e91a8ce87af7750350b42b9674aa65458e06e07a7dc00db41ef34240243df512-runc.4Hrzut.mount: Deactivated successfully.
Oct 30 17:52:27 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-ae30063642c2fdf7afea1c709c20eec527f0a943bf5360a4262e40ee0f5669fd-runc.VfHqw6.mount: Deactivated successfully.
Oct 30 17:52:33 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-e91a8ce87af7750350b42b9674aa65458e06e07a7dc00db41ef34240243df512-runc.uQMraQ.mount: Deactivated successfully.
Oct 30 17:52:49 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-1e2cfcbf015395dd6b7b2f6584c59c6c32a3fad4103b4e4ee52bfec5b347e738-runc.IHKIpf.mount: Deactivated successfully.
Oct 30 17:52:53 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-cfe916de0bece10f2d86a06a565daebcc5d6fb3d0195908f023ce5a00b64375f-runc.FfdEhg.mount: Deactivated successfully.
Oct 30 17:52:57 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-ae30063642c2fdf7afea1c709c20eec527f0a943bf5360a4262e40ee0f5669fd-runc.ElkI9A.mount: Deactivated successfully.
Oct 30 17:52:59 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-717e6fdc4ff5bfe526ea8444fe41ce6307e6c21fdbc4dec30d6de914855ec5dc-runc.5OKGZc.mount: Deactivated successfully.
Oct 30 17:53:05 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-e91a8ce87af7750350b42b9674aa65458e06e07a7dc00db41ef34240243df512-runc.AVPjAy.mount: Deactivated successfully.
Oct 30 17:53:24 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-cfe916de0bece10f2d86a06a565daebcc5d6fb3d0195908f023ce5a00b64375f-runc.JO2jA2.mount: Deactivated successfully.
Oct 30 17:53:27 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-ae30063642c2fdf7afea1c709c20eec527f0a943bf5360a4262e40ee0f5669fd-runc.VEFGvX.mount: Deactivated successfully.
Oct 30 17:53:29 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-717e6fdc4ff5bfe526ea8444fe41ce6307e6c21fdbc4dec30d6de914855ec5dc-runc.ePZSpf.mount: Deactivated successfully.
Oct 30 17:53:37 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-e91a8ce87af7750350b42b9674aa65458e06e07a7dc00db41ef34240243df512-runc.xV2JHZ.mount: Deactivated successfully.
Oct 30 17:53:49 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-1e2cfcbf015395dd6b7b2f6584c59c6c32a3fad4103b4e4ee52bfec5b347e738-runc.oqe5pa.mount: Deactivated successfully.
Oct 30 17:53:56 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-cfe916de0bece10f2d86a06a565daebcc5d6fb3d0195908f023ce5a00b64375f-runc.X8PYvP.mount: Deactivated successfully.
Oct 30 17:53:57 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-ae30063642c2fdf7afea1c709c20eec527f0a943bf5360a4262e40ee0f5669fd-runc.Tk93Bc.mount: Deactivated successfully.
Oct 30 17:53:59 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-717e6fdc4ff5bfe526ea8444fe41ce6307e6c21fdbc4dec30d6de914855ec5dc-runc.gTzZnX.mount: Deactivated successfully.
Oct 30 17:54:19 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-1e2cfcbf015395dd6b7b2f6584c59c6c32a3fad4103b4e4ee52bfec5b347e738-runc.uMMMnl.mount: Deactivated successfully.
Oct 30 17:54:27 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-cfe916de0bece10f2d86a06a565daebcc5d6fb3d0195908f023ce5a00b64375f-runc.NhmQ5M.mount: Deactivated successfully.
Oct 30 17:54:27 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-ae30063642c2fdf7afea1c709c20eec527f0a943bf5360a4262e40ee0f5669fd-runc.wtHSRu.mount: Deactivated successfully.
Oct 30 17:54:29 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-717e6fdc4ff5bfe526ea8444fe41ce6307e6c21fdbc4dec30d6de914855ec5dc-runc.0rCeEK.mount: Deactivated successfully.
Oct 30 17:54:49 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-1e2cfcbf015395dd6b7b2f6584c59c6c32a3fad4103b4e4ee52bfec5b347e738-runc.IlwowW.mount: Deactivated successfully.
Oct 30 17:54:58 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-ae30063642c2fdf7afea1c709c20eec527f0a943bf5360a4262e40ee0f5669fd-runc.PUUmO7.mount: Deactivated successfully.
Oct 30 17:54:58 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-cfe916de0bece10f2d86a06a565daebcc5d6fb3d0195908f023ce5a00b64375f-runc.Qqymiz.mount: Deactivated successfully.
Oct 30 17:54:59 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-717e6fdc4ff5bfe526ea8444fe41ce6307e6c21fdbc4dec30d6de914855ec5dc-runc.gvD82Y.mount: Deactivated successfully.
Oct 30 17:55:13 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-e91a8ce87af7750350b42b9674aa65458e06e07a7dc00db41ef34240243df512-runc.0SevBS.mount: Deactivated successfully.
Oct 30 17:55:20 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-1e2cfcbf015395dd6b7b2f6584c59c6c32a3fad4103b4e4ee52bfec5b347e738-runc.QkRC92.mount: Deactivated successfully.
Oct 30 17:55:28 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-ae30063642c2fdf7afea1c709c20eec527f0a943bf5360a4262e40ee0f5669fd-runc.GJSwZu.mount: Deactivated successfully.
Oct 30 17:55:29 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-cfe916de0bece10f2d86a06a565daebcc5d6fb3d0195908f023ce5a00b64375f-runc.WnXCnF.mount: Deactivated successfully.
Oct 30 17:55:29 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-717e6fdc4ff5bfe526ea8444fe41ce6307e6c21fdbc4dec30d6de914855ec5dc-runc.9ItFPH.mount: Deactivated successfully.
Oct 30 17:55:45 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-e91a8ce87af7750350b42b9674aa65458e06e07a7dc00db41ef34240243df512-runc.3VJImB.mount: Deactivated successfully.
Oct 30 17:55:58 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-ae30063642c2fdf7afea1c709c20eec527f0a943bf5360a4262e40ee0f5669fd-runc.4E7xmz.mount: Deactivated successfully.
Oct 30 17:55:59 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-717e6fdc4ff5bfe526ea8444fe41ce6307e6c21fdbc4dec30d6de914855ec5dc-runc.aFkn1I.mount: Deactivated successfully.
Oct 30 17:56:00 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-cfe916de0bece10f2d86a06a565daebcc5d6fb3d0195908f023ce5a00b64375f-runc.tcc5mE.mount: Deactivated successfully.
Oct 30 17:56:20 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-1e2cfcbf015395dd6b7b2f6584c59c6c32a3fad4103b4e4ee52bfec5b347e738-runc.f8VGOy.mount: Deactivated successfully.
Oct 30 17:56:28 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-ae30063642c2fdf7afea1c709c20eec527f0a943bf5360a4262e40ee0f5669fd-runc.w6xrtT.mount: Deactivated successfully.
Oct 30 17:56:29 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-717e6fdc4ff5bfe526ea8444fe41ce6307e6c21fdbc4dec30d6de914855ec5dc-runc.HhMAiR.mount: Deactivated successfully.
Oct 30 17:56:31 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-cfe916de0bece10f2d86a06a565daebcc5d6fb3d0195908f023ce5a00b64375f-runc.p2l9Le.mount: Deactivated successfully.
Oct 30 17:56:49 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-e91a8ce87af7750350b42b9674aa65458e06e07a7dc00db41ef34240243df512-runc.mNwSpS.mount: Deactivated successfully.
Oct 30 17:56:50 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-1e2cfcbf015395dd6b7b2f6584c59c6c32a3fad4103b4e4ee52bfec5b347e738-runc.5q1ifg.mount: Deactivated successfully.
Oct 30 17:56:58 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-ae30063642c2fdf7afea1c709c20eec527f0a943bf5360a4262e40ee0f5669fd-runc.mFUufw.mount: Deactivated successfully.
Oct 30 17:56:59 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-717e6fdc4ff5bfe526ea8444fe41ce6307e6c21fdbc4dec30d6de914855ec5dc-runc.mjOD8F.mount: Deactivated successfully.
Oct 30 17:57:02 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-cfe916de0bece10f2d86a06a565daebcc5d6fb3d0195908f023ce5a00b64375f-runc.n6I9xg.mount: Deactivated successfully.
Oct 30 17:57:20 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-1e2cfcbf015395dd6b7b2f6584c59c6c32a3fad4103b4e4ee52bfec5b347e738-runc.1ADZhI.mount: Deactivated successfully.
Oct 30 17:57:21 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-e91a8ce87af7750350b42b9674aa65458e06e07a7dc00db41ef34240243df512-runc.84A9V4.mount: Deactivated successfully.
Oct 30 17:57:28 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-ae30063642c2fdf7afea1c709c20eec527f0a943bf5360a4262e40ee0f5669fd-runc.PsuYkZ.mount: Deactivated successfully.
Oct 30 17:57:29 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-717e6fdc4ff5bfe526ea8444fe41ce6307e6c21fdbc4dec30d6de914855ec5dc-runc.h2iiBn.mount: Deactivated successfully.
Oct 30 17:57:53 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-e91a8ce87af7750350b42b9674aa65458e06e07a7dc00db41ef34240243df512-runc.HfQTV6.mount: Deactivated successfully.
Oct 30 17:57:58 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-ae30063642c2fdf7afea1c709c20eec527f0a943bf5360a4262e40ee0f5669fd-runc.UJzhrs.mount: Deactivated successfully.
Oct 30 17:57:59 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-717e6fdc4ff5bfe526ea8444fe41ce6307e6c21fdbc4dec30d6de914855ec5dc-runc.vWWwJ1.mount: Deactivated successfully.
Oct 30 17:58:04 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-cfe916de0bece10f2d86a06a565daebcc5d6fb3d0195908f023ce5a00b64375f-runc.PmTsES.mount: Deactivated successfully.
Oct 30 17:58:26 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-e91a8ce87af7750350b42b9674aa65458e06e07a7dc00db41ef34240243df512-runc.0yrSWC.mount: Deactivated successfully.
Oct 30 17:58:28 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-ae30063642c2fdf7afea1c709c20eec527f0a943bf5360a4262e40ee0f5669fd-runc.s3hx2v.mount: Deactivated successfully.
Oct 30 17:58:50 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-1e2cfcbf015395dd6b7b2f6584c59c6c32a3fad4103b4e4ee52bfec5b347e738-runc.kSXZrQ.mount: Deactivated successfully.
Oct 30 17:58:58 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-e91a8ce87af7750350b42b9674aa65458e06e07a7dc00db41ef34240243df512-runc.20A5BS.mount: Deactivated successfully.
Oct 30 17:58:58 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-ae30063642c2fdf7afea1c709c20eec527f0a943bf5360a4262e40ee0f5669fd-runc.4KVDgJ.mount: Deactivated successfully.
Oct 30 17:59:00 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-717e6fdc4ff5bfe526ea8444fe41ce6307e6c21fdbc4dec30d6de914855ec5dc-runc.IkZrJy.mount: Deactivated successfully.
Oct 30 17:59:06 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-cfe916de0bece10f2d86a06a565daebcc5d6fb3d0195908f023ce5a00b64375f-runc.4nqdyC.mount: Deactivated successfully.
Oct 30 17:59:20 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-1e2cfcbf015395dd6b7b2f6584c59c6c32a3fad4103b4e4ee52bfec5b347e738-runc.ysc8rm.mount: Deactivated successfully.
Oct 30 17:59:28 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-ae30063642c2fdf7afea1c709c20eec527f0a943bf5360a4262e40ee0f5669fd-runc.v4y0qn.mount: Deactivated successfully.
Oct 30 17:59:30 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-717e6fdc4ff5bfe526ea8444fe41ce6307e6c21fdbc4dec30d6de914855ec5dc-runc.qlwoGe.mount: Deactivated successfully.
Oct 30 17:59:30 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-e91a8ce87af7750350b42b9674aa65458e06e07a7dc00db41ef34240243df512-runc.w4nVy2.mount: Deactivated successfully.
Oct 30 17:59:37 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-cfe916de0bece10f2d86a06a565daebcc5d6fb3d0195908f023ce5a00b64375f-runc.amgV8y.mount: Deactivated successfully.
Oct 30 17:59:50 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-1e2cfcbf015395dd6b7b2f6584c59c6c32a3fad4103b4e4ee52bfec5b347e738-runc.Vq3y0E.mount: Deactivated successfully.
Oct 30 17:59:58 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-ae30063642c2fdf7afea1c709c20eec527f0a943bf5360a4262e40ee0f5669fd-runc.cT2K0H.mount: Deactivated successfully.
Oct 30 18:00:00 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-717e6fdc4ff5bfe526ea8444fe41ce6307e6c21fdbc4dec30d6de914855ec5dc-runc.iCCQWi.mount: Deactivated successfully.
Oct 30 18:00:02 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-e91a8ce87af7750350b42b9674aa65458e06e07a7dc00db41ef34240243df512-runc.oTCMi5.mount: Deactivated successfully.
Oct 30 18:00:09 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-cfe916de0bece10f2d86a06a565daebcc5d6fb3d0195908f023ce5a00b64375f-runc.kVtpoY.mount: Deactivated successfully.
Oct 30 18:00:20 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-1e2cfcbf015395dd6b7b2f6584c59c6c32a3fad4103b4e4ee52bfec5b347e738-runc.tCwKDn.mount: Deactivated successfully.
Oct 30 18:00:28 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-ae30063642c2fdf7afea1c709c20eec527f0a943bf5360a4262e40ee0f5669fd-runc.CMeXlw.mount: Deactivated successfully.
Oct 30 18:00:30 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-717e6fdc4ff5bfe526ea8444fe41ce6307e6c21fdbc4dec30d6de914855ec5dc-runc.wYhgww.mount: Deactivated successfully.
Oct 30 18:00:31 homeassistant kernel: audit: type=1334 audit(1698688831.452:1696): prog-id=757 op=LOAD
Oct 30 18:00:31 homeassistant systemd[1]: Started Journal Gateway Service.
Oct 30 18:00:31 homeassistant systemd-timesyncd[398]: Network configuration changed, trying to establish connection.
Oct 30 18:00:31 homeassistant systemd-timesyncd[398]: Contacted time server 162.159.200.123:123 (time.cloudflare.com).
Oct 30 18:00:31 homeassistant systemd-journal-gatewayd[2783084]: microhttpd: MHD_OPTION_EXTERNAL_LOGGER is not the first option specified for the daemon. Some messages may be printed by the standard MHD logger.

System information

No response

Additional information

I opened this issue against HA-core, but was told it was better to put it here. The relevant HA-Core issue is: https://github.com/home-assistant/core/issues/101979

I also left a comment with instructions on a bandaid fix, quoted here:

For those that find this issue, and are waiting for a fix, you can apply the new rules file to your system.

  1. Create a new file at /etc/udev/rules.d/60-serial.rule with the contents of the new rules
  2. Run sudo udevadm control --reload-rules && sudo udevadm trigger
  3. Unplug and replug (or the equivalent if you are running virtualized) the USB devices.
  4. You should now see them mounted in /dev/serial/by-id

paradox460 avatar Oct 30 '23 18:10 paradox460

Home Assistant OS ships with systemd 252.9 (see https://github.com/home-assistant/buildroot/blob/82003cc280472999d0488a42e700ef8dacb58198/package/systemd/systemd.mk#L22), so this issue should be fixed.

In my test instances I also have /dev/serial/by-id/ entries for USB devices.

You will not see the device at /dev/serial/by-id/* path, the /dev/serial/by-id directory is entirely missing

How do you check this?

What virtualization environment are you using?

agners avatar Oct 31 '23 09:10 agners

I'm in QEMU via virt-framework (virsh)

I've been checking it by accessing the console via virsh console hass, and then navigating to /dev. Prior to manually adding a serial rule to udev, I did not see them there at all. They worked prior to the update to 252.

paradox460 avatar Nov 01 '23 20:11 paradox460

There wasn't really an update to systemd with HAOS 11.2, but just in case, did that resolve it for you? (if so, then maybe the kernel stable updates helped :man_shrugging: )

I've checked virsh/libvirtd based installation on my end. Both a FTDI and a CP2102N based USB-to-serial adapater device appeared properly in /dev/serial/by-id/. Maybe this is a problem for certain devices only? What type of device do you use?

agners avatar Dec 05 '23 08:12 agners

Jumping in on this; I have QEMU + Virsh too, and updated to HAOS 11.2, same problem.

Noticed because my ConBee II stopped working.

Error setting up entry ConBee II for zha

Traceback (most recent call last):
  File "/usr/local/lib/python3.11/site-packages/serial/serialposix.py", line 322, in open
    self.fd = os.open(self.portstr, os.O_RDWR | os.O_NOCTTY | os.O_NONBLOCK)
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
FileNotFoundError: [Errno 2] No such file or directory: '/dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2289119-if00'

The bandaid fix works if you use the actual new version of the 60-serial.rules. The one previously suggested is the old rules file.

WinterPhoenix avatar Dec 06 '23 23:12 WinterPhoenix

This all really doesn't make a lot of sense currently: /usr/lib/udev/rules.d/60-serial.rules is there and it's content is

# do not edit this file, it will be overwritten on update

ACTION=="remove", GOTO="serial_end"
SUBSYSTEM!="tty", GOTO="serial_end"

SUBSYSTEMS=="usb", IMPORT{builtin}="usb_id", IMPORT{builtin}="hwdb --subsystem=usb"
SUBSYSTEMS=="pci", ENV{ID_BUS}=="", ENV{ID_BUS}="pci", \
  ENV{ID_VENDOR_ID}="$attr{vendor}", ENV{ID_MODEL_ID}="$attr{device}", \
  IMPORT{builtin}="hwdb --subsystem=pci"

# /dev/serial/by-path/, /dev/serial/by-id/ for USB devices
KERNEL!="ttyUSB[0-9]*|ttyACM[0-9]*", GOTO="serial_end"

SUBSYSTEMS=="usb-serial", ENV{.ID_PORT}="$attr{port_number}"

IMPORT{builtin}="path_id"
ENV{ID_PATH}=="?*", ENV{.ID_PORT}=="", SYMLINK+="serial/by-path/$env{ID_PATH}"
ENV{ID_PATH}=="?*", ENV{.ID_PORT}=="?*", SYMLINK+="serial/by-path/$env{ID_PATH}-port$env{.ID_PORT}"

ENV{ID_BUS}=="", GOTO="serial_end"
ENV{ID_SERIAL}=="", GOTO="serial_end"
ENV{ID_USB_INTERFACE_NUM}=="", GOTO="serial_end"
ENV{.ID_PORT}=="", SYMLINK+="serial/by-id/$env{ID_BUS}-$env{ID_SERIAL}-if$env{ID_USB_INTERFACE_NUM}"
ENV{.ID_PORT}=="?*", SYMLINK+="serial/by-id/$env{ID_BUS}-$env{ID_SERIAL}-if$env{ID_USB_INTERFACE_NUM}-port$env{.ID_PORT}"

LABEL="serial_end"

Comparing with the linked file, it only has the additional ID_PATH_WITH_USB_REVISION entries, which from what I understand is something which needs a newer systemd-udev version as well (see https://github.com/systemd/systemd/commit/873be895ed1fe65010fb84c6b71e2ec0a6b6fc91#diff-a712a6f4004cd0bd01dc6e4c9494e329c29cc52de1c4cbc24879c7f03c1aae29).

My best guess is that this is some race condition or random issue. The additional udev rules might change that race and/or it just randomly working at times.

agners avatar Dec 19 '23 13:12 agners

So an update. At least for me, part of the problem was that Virsh has begun not properly attaching the device when the VM starts, despite it being in the config. I have to attach it manually every time for it to appear, or even for /dev/serial/by-id/ to appear.

That said, removing the custom 60-serial.rules still breaks it, so there might be more than one thing going on here.

WinterPhoenix avatar Jan 04 '24 01:01 WinterPhoenix

There hasn't been any activity on this issue recently. To keep our backlog manageable we have to clean old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant OS version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

github-actions[bot] avatar Apr 03 '24 05:04 github-actions[bot]