I have an intel fakeraid raid0 with 3 disks correctly configured under mdadm. The problem, is that mdadm -I /dev/md127 seems to be needed to correctly assemble the mdadm raid for intel fakeraid devices, and genkernel does not seem to do it automatically (I think it only does mdadm -As which detects the array but does not assemble, as seems -I (incremental) is needed in this case. The affected version is genkernel-next-63. I am also getting some errors maybe not related at start. So, as can be seen in the following image, in order to start my system, I have to type shell to get a busybox shell, and manually type mdadm -I /dev/md127 and ctrl + D for my system to boot properly: http://i.imgur.com/lw3RFJb.jpg Can't any option for this be added? Or detect if the raid is intel and run the mdadm command automatically?
Created attachment 411508 [details] mdadm config
Created attachment 411510 [details] genkernel.conf file
As aditional info, once I click ctrl+D I am also getting some errors related to btrfs, which I don't know if are related to this, but wanted to comment them here: http://i.imgur.com/7aojOR5.jpg
Should I upload my generated init image so you can see where the sed failed commands are from?
I updated my current genkernel generated image with command line genkernel --btrfs --no-lvm --mdadm --mdadm-config=/etc/mdadm.conf --no-dmraid --install --firmware --makeopts=-j8 --callback="emerge @module-rebuild --ask=n" all If it is useful for seing what causes sed errors and the other: https://mega.nz/#!vMkGlYyY!LwQnMhLbuNhkEB-ctGrlkqsKLtPFB5pm2qjApfPNyTw I also have to say, that because of this bug, I am totally unable to resume my system from hibernation, as swap partition is also inside raid, and can't be detected.
*** This bug has been marked as a duplicate of bug 549488 ***
