| 1 |
Am 04.05.2014 03:56, schrieb Mark Pariente: |
| 2 |
> I had a similar issue after upgrading to sys-apps/systemd-212-r3. Turned |
| 3 |
> out it was due to udev rules.d directory location. I still had a bunch |
| 4 |
> of udev rules under /usr/lib64/udev/rules.d and it looks like the new |
| 5 |
> systemd/udev is only looking at rules under /lib/udev/. |
| 6 |
> |
| 7 |
> The particular issue was that the RAID device (/dev/md127 in my case) |
| 8 |
> was no longer auto-assembled because the udev rules installed by the |
| 9 |
> mdadm package were still in /usr/lib64/udev/rules.d instead |
| 10 |
> of /lib/udev. This required me to re-emerge mdadm which then installed |
| 11 |
> the udev rules into /lib/udev. |
| 12 |
> |
| 13 |
> Unfortunately there were many other such packages affected. I just ran |
| 14 |
> 'equery belongs' on all files under /usr/lib64/udev/rules.d and |
| 15 |
> re-emerged all respective packages which fixed all issues. |
| 16 |
|
| 17 |
There is a nice command for finding and rebuilding the affected packages in |
| 18 |
|
| 19 |
https://bugs.gentoo.org/show_bug.cgi?id=509492 |
| 20 |
|
| 21 |
(in Comment 6) |
| 22 |
|
| 23 |
I just did that one of my thinkpads as I wasn't able to properly login |
| 24 |
anymore (/home encrypted via cryptsetup). |
| 25 |
|
| 26 |
Stefan |
Archives