When trying to create an initrd image with genkernel-next and dmraid, the system is not bootable because it says that libdmraid-events-isw.so can't be loaded because it is missing (for my intel fakeraid). The raid array is being detected with dodmraid kernel parameter, but any partition is detected (including root partition) in the raid array. Reproducible: Always
Forgot to say I am using genkernel-next-60. I also modified the file gen-initramfs.sh to include all the event libraries. But now the error is different: "Unable to register a device mapper event handler (don't remember the rest of the message)" Does something happens with genkernel+dmraid? I am using kernel 4.0.2 if that matters. Also, dmraid is not compiled with static USE flag, because doing so will lead to an error in genkernel about not finding /usr/sbin/dmevent_tool file (which seems not to be installed with static use flag)
Furthermore, maybe it should be reported in another report (tell me if so), but I found another big problem in genkernel-next-60: With mdadm, the support (and config file) is being added if appropiate, but when booted, array is detected but **not** started, resulting in a non bootable system. This does not happen with "normal" genkernel, only with genkernel-next. I am no specialist on mdadm, so I can't really know why the array is not started (tested with an intel fakeraid imsm)
is this still valid for version 63?
(In reply to Pacho Ramos from comment #3) > is this still valid for version 63? Sorry for my late answer, I stop trying after reporting as of frustration and used just normal non raid install. Now I am trying again, and yes, version 63 is still affected, same error. And posibly not related, but mdadm support can't assemble and start gentoo neither :(
Hi, I'm facing the same problem with genkernel v63 on an Intel bios fake raid, I don't know if this helps but I'm sharing it. I've manually put the missing libdmraid-events-isw.so library, dmeventd and partprobe binaries (with all their libraries) inside the initrd image, now the error is gone but I'm dropped to the shell because it still can't find the root partition and if I try to partprobe the array it gives me this error: "# partprobe /dev/mapper/isw_daheciadhf_OS-Raid0 Error: Partition(s) 1, 2, 3, 4, 5, 6 on /dev/mapper/isw_daheciadhf_OS-Raid0 have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use. As a result, the old partition(s) will remain in use. You should reboot now before making further changes." I think the kernel is properly configured because I can see all the disks under /dev and it creates both /dev/dm-0 and /dev/mapper/isw_daheciadhf_OS-Raid0 correctly. Maybe something is missing in the initrc script? I'm stuck using an old ubuntu generated kernel because I can't even make dracut to work... Thanks
Try to report it to upstream please and post the link here: https://github.com/Sabayon/genkernel-next/issues
*** Bug 560122 has been marked as a duplicate of this bug. ***
Package removed.
