Skip to content
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

buster: delete broken udev rules #271

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

KanjiMonster
Copy link
Contributor

The udev rules 60-block.rules and 60-net.rules try to call binaries that do not exist at these paths in the main rootfs, so always fail. Since neither of them do anything useful outside of the initrd (where udev isn't used), drop the udev rules trying to call them instead of trying to fix them up.

Silences errors like:

root@localhost:/# journalctl -b | grep "failed with exit code"
Sep 15 09:18:55 localhost systemd-udevd[573]: Process '/sbin/initnetdev ma1 add' failed with exit code 1.
Sep 15 09:18:55 localhost systemd-udevd[574]: Process '/sbin/initblockdev mtdblock0 add' failed with exit code 1.
Sep 15 09:18:55 localhost systemd-udevd[557]: Process '/sbin/initblockdev mtdblock1 add' failed with exit code 1.
Sep 15 09:18:55 localhost systemd-udevd[567]: Process '/sbin/initblockdev mtdblock2 add' failed with exit code 1.
Sep 15 09:18:56 localhost systemd-udevd[555]: Process '/sbin/initblockdev sda add' failed with exit code 1.
Sep 15 09:18:56 localhost systemd-udevd[553]: Process '/sbin/initnetdev eth1 add' failed with exit code 1.
Sep 15 09:18:56 localhost systemd-udevd[586]: Process '/sbin/initnetdev eth11 add' failed with exit code 1.
Sep 15 09:18:56 localhost systemd-udevd[555]: Process '/sbin/initblockdev sda1 add' failed with exit code 1.
...
root@localhost:/# journalctl -b | grep "failed with exit code" | wc -l
141

The udev rule 60-block.rules tries to call '/sbin/initblockdev', but that
file only exists in the initrd, but not in the main rootfs, so any
attempts will just fail. So drop the udev rule trying to call it.

Silences errors at boot like:

> Sep 15 09:18:55 localhost systemd-udevd[574]: Process '/sbin/initblockdev mtdblock0 add' failed with exit code 1.
> Sep 15 09:18:55 localhost systemd-udevd[557]: Process '/sbin/initblockdev mtdblock1 add' failed with exit code 1.
> Sep 15 09:18:55 localhost systemd-udevd[567]: Process '/sbin/initblockdev mtdblock2 add' failed with exit code 1.
> Sep 15 09:18:56 localhost systemd-udevd[555]: Process '/sbin/initblockdev sda add' failed with exit code 1.
> Sep 15 09:18:56 localhost systemd-udevd[555]: Process '/sbin/initblockdev sda1 add' failed with exit code 1.
> ...

Signed-off-by: Jonas Gorski <[email protected]>
The udev rule 60-net.rules tries to call '/sbin/initnetdev', but that
file is found at a different location, at '/usr/bin/initnetdev', so the
call always fails.

Since the only purpose of initnetdev is to rename network devices based
on the platform configuration, the initial management port renaming is
already done by the initrd, and for any subsequent port devices we have
an extra rule, drop the udev rule instead of trying to fix it.

Silences errors at boot like:

> Sep 15 09:18:55 localhost systemd-udevd[573]: Process '/sbin/initnetdev ma1 add' failed with exit code 1.
> Sep 15 09:18:56 localhost systemd-udevd[553]: Process '/sbin/initnetdev eth1 add' failed with exit code 1.
> Sep 15 09:18:56 localhost systemd-udevd[586]: Process '/sbin/initnetdev eth11 add' failed with exit code 1.
> Sep 15 09:18:56 localhost systemd-udevd[594]: Process '/sbin/initnetdev eth33 add' failed with exit code 1.
> Sep 15 09:18:56 localhost systemd-udevd[596]: Process '/sbin/initnetdev eth19 add' failed with exit code 1.
> ...

Signed-off-by: Jonas Gorski <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants