Summary: | genkernel-next can't correctly assemble intel fakeraid | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | David Carlos Manuelda <StormByte> |
Component: | [OLD] Core system | Assignee: | Fabio Erculiani (RETIRED) <lxnay> |
Status: | RESOLVED DUPLICATE | ||
Severity: | major | ||
Priority: | Normal | ||
Version: | 10.1 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
mdadm config
genkernel.conf file |
Description
David Carlos Manuelda
2015-09-10 13:05:46 UTC
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 *** |