| 1 |
I had a similar issue after upgrading to sys-apps/systemd-212-r3. Turned |
| 2 |
out it was due to udev rules.d directory location. I still had a bunch |
| 3 |
of udev rules under /usr/lib64/udev/rules.d and it looks like the new |
| 4 |
systemd/udev is only looking at rules under /lib/udev/. |
| 5 |
|
| 6 |
The particular issue was that the RAID device (/dev/md127 in my case) |
| 7 |
was no longer auto-assembled because the udev rules installed by the |
| 8 |
mdadm package were still in /usr/lib64/udev/rules.d instead |
| 9 |
of /lib/udev. This required me to re-emerge mdadm which then installed |
| 10 |
the udev rules into /lib/udev. |
| 11 |
|
| 12 |
Unfortunately there were many other such packages affected. I just ran |
| 13 |
'equery belongs' on all files under /usr/lib64/udev/rules.d and |
| 14 |
re-emerged all respective packages which fixed all issues. |
| 15 |
|
| 16 |
--Mark |
| 17 |
|
| 18 |
|
| 19 |
On Sat, 2014-05-03 at 12:12 +0200, Stefan G. Weichinger wrote: |
| 20 |
> I see boot problems on two of my machines ... very likely related to |
| 21 |
> lvm2 as far as I can tell so far. |
| 22 |
> |
| 23 |
> Downgraded and even disabled systemd, re-emerged stuff ... I am still at |
| 24 |
> trying to find the reason. Maybe it is with the mdadm raids also ... |
| 25 |
> |
| 26 |
> I just want to ask you other gentoo users if anyone else hit this issue |
| 27 |
> since around yesterday? Maybe someone else also scratches his head |
| 28 |
> already ... |
| 29 |
> |
| 30 |
> Stefan |
| 31 |
> |
Archives