| Summary: | sys-kernel/genkernel-next: booting with dodmraid fails because init script looks for /sbin/dmraid instead of /usr/sbin/dmraid | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | henning.f |
| Component: | [OLD] Core system | Assignee: | Fabio Erculiani (RETIRED) <lxnay> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | AMD64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
This has been fixed some time ago in git. Now I also committed this: commit 55c809c090acacd25bf4a10738b1310e2653cd4a Author: Fabio Erculiani <lxnay@sabayon.org> Date: Mon Sep 9 15:21:10 2013 +0200 linuxrc: make sure that /sbin and /usr/sbin are in PATH |
Starting a kernel, with a initramfs generated with genkernel-next, with the dodmraid argument does not start dmraid. The reason for this can be found when looking in the generated inird.scripts file located in the cpio file. if [ "${USE_DMRAID_NORMAL}" = '1' ] then if [ -e '/sbin/dmraid' ] then good_msg "Activating Device-Mapper RAID(s)" if [ '${DMRAID_OPTS}' = '' ] then /sbin/dmraid -ay else /sbin/dmraid -ay ${DMRAID_OPTS} fi fi fi There is no /sbin/dmraid file in the cpio archive. It is located under /usr/sbin/dmraid Reproducible: Always Steps to Reproduce: 1. /etc/genkernel.conf with DMRAID="yes" 2. genkernel --no-compress-initrd initramfs 3. /etc/defaults/grub GRUB_CMDLINE_LINUX="... dodmraid" 4. Reboot Actual Results: dmraid is not started Expected Results: dmraid is started sys-kernel/genkernel-next-24 was built with the following: USE="crypt cryptsetup dmraid plymouth -gpg (-ibm) -iscsi (-selinux)"