Summary: | sys-fs/udev-240-r2 breaks LVM volumes on boot with error messages WARNING: Device /dev/sdXXX not initialized in udev database even after waiting 10000000 microseconds. | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | email200202 |
Component: | Current packages | Assignee: | udev maintainers <udev-bugs> |
Status: | RESOLVED WORKSFORME | ||
Severity: | major | CC: | julien.sanchez, kripton, marci_r, n-roeser, volkov, zzam |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: |
https://bugs.gentoo.org/show_bug.cgi?id=673796 https://bugs.gentoo.org/show_bug.cgi?id=683260 |
||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
email200202
2019-01-07 02:52:24 UTC
Please create a bug report upstream. https://github.com/systemd/systemd/issues I can confirm that udev-240-r2 creates improper 660 permissions on /dev/null, /dev/urandom, and the like. I am not using lvm2, so this problem doesn't prevent booting for me, but it is annoying to have to change permissions after each reboot. Unkeywording udev backs off to udev-239, which fixes the problem for me. gentoo-sources 4.20.3 openrc 0.40.3 udisks 2.8.1 The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d3b151ff2a468c62638ca87ac89bc1321e730fba commit d3b151ff2a468c62638ca87ac89bc1321e730fba Author: Mike Gilbert <floppym@gentoo.org> AuthorDate: 2019-01-24 14:57:17 +0000 Commit: Mike Gilbert <floppym@gentoo.org> CommitDate: 2019-01-24 14:57:17 +0000 sys-fs/udev: patchset for 240 based on v240-stable branch upstream Bug: https://bugs.gentoo.org/676138 Bug: https://bugs.gentoo.org/674816 Bug: https://bugs.gentoo.org/674748 Package-Manager: Portage-2.3.56_p3, Repoman-2.3.12_p50 Signed-off-by: Mike Gilbert <floppym@gentoo.org> sys-fs/udev/Manifest | 1 + sys-fs/udev/udev-240-r3.ebuild | 325 +++++++++++++++++++++++++++++++++++++++++ 2 files changed, 326 insertions(+) As an alternative to having sys-fs/udev, I am using sys-fs/eudev now. Works lika a charm As another workaround please test lvm2-2.02.184-r1. |