| View previous topic :: View next topic |
| Author |
Message |
Bounteous
n00b
Joined: 09 Feb 2018
Posts: 9
Location: Spain
|
 Posted: Fri Nov 09, 2018 11:03 pm Post subject: Genkernel: ERROR: Binary /sbin/mdassemble could not be found |
 |
|
| Code: | | genkernel --udev --lvm --mdadm --luks initramfs |
| Code: | * Gentoo Linux Genkernel; Version 68
* Running with options: --udev --lvm --mdadm --luks initramfs
* Using genkernel.conf from /etc/genkernel.conf
* Sourcing arch-specific config.sh from /usr/share/genkernel/arch/x86_64/config.sh ..
* Sourcing arch-specific modules_load from /usr/share/genkernel/arch/x86_64/modules_load ..
* Linux Kernel 4.14.78-gentoo-v0.0.1 for x86_64...
* .. with config file /usr/share/genkernel/arch/x86_64/kernel-config
* busybox: >> Using cache
* initramfs: >> Initializing...
* >> Appending base_layout cpio data...
* >> Appending udev cpio data...
cp: cannot stat '/etc/modprobe.d/blacklist.conf': No such file or directory
* cannot copy /etc/modprobe.d/blacklist.conf from udev
* >> Appending auxilary cpio data...
* >> Copying keymaps
* >> Appending busybox cpio data...
* >> Appending lvm cpio data...
* LVM: Adding support (copying binaries from system)...
* >> Appending mdadm cpio data...
* ERROR: Binary /sbin/mdassemble could not be found
|
Downgrade version from sys-fs/mdadm-4.1 to 3.4 fixed it. |
|
| Back to top |
|
 |
fedeliallalinea
Administrator
Joined: 08 Mar 2003
Posts: 30917
Location: here
|
| Posted: Sat Nov 10, 2018 12:41 pm Post subject: |
|
|
There is also an open bug https://bugs.gentoo.org/669792
_________________
Questions are guaranteed in life; Answers aren't. |
|
| Back to top |
|
|
russK
l33t
Joined: 27 Jun 2006
Posts: 665
|
| Posted: Tue Nov 27, 2018 3:14 am Post subject: |
|
|
I can confirm Comment #15 to the bugreport, you can now upgrade genkernel-next to sys-kernel/genkernel-next-69 to get past this problem.
https://bugs.gentoo.org/669792#c15
Cheers |
|
| Back to top |
|
|
TiccTech
n00b
Joined: 13 Jun 2004
Posts: 42
Location: Oregon, US
|
| Posted: Fri Nov 30, 2018 2:58 am Post subject: |
|
|
EDIT: I figured out what my problem was. Details in https://forums.gentoo.org/viewtopic-t-1090040.html.
I tried sys-kernel/genkernel-next-69 with sys-fs/mdadm-4.1. However, doing a | Code: | | genkernel --mdadm initramfs |
produced an initramfs that panicked on boot because it could not find the root partition (which is RAID1). I downgraded to sys-kernel/genkernel-next-68 and sys-fs/mdadm-3.4, did the same procedure, and can successfully boot.
So something's not quite right somewhere in the newer versions. 
-TiccTech
Last edited by TiccTech on Sat Dec 01, 2018 1:12 am; edited 1 time in total |
|
| Back to top |
|
|
Maitreya
Guru
Joined: 11 Jan 2006
Posts: 441
|
| Posted: Fri Nov 30, 2018 2:33 pm Post subject: |
|
|
I think I had the same with btrfs and not finding udev in initramfs at boot.
For me a genkernel cache clear was enough to fix it. |
|
| Back to top |
|
|
Arrta
Tux's lil' helper
Joined: 09 Nov 2003
Posts: 106
|
| Posted: Fri Mar 08, 2019 9:26 pm Post subject: |
|
|
4 month old post, but I just ran in to this myself today.
genkernel-next nolonger has a 69 build, and I was getting the "mdassemble could not be found" error.
Back reved mdadm to 3.4 to resolve. |
|
| Back to top |
|
|
|
Kernel & Hardware
