561118 – =sys-kernel/genkernel-next-63 crypt_root is not mapped to root

Bug 561118 - =sys-kernel/genkernel-next-63 crypt_root is not mapped to root

Summary: =sys-kernel/genkernel-next-63 crypt_root is not mapped to root

Status:	RESOLVED INVALID

Alias:	None

Product:	Gentoo Hosted Projects
Classification:	Unclassified
Component:	genkernel (show other bugs)
Hardware:	All Linux

Importance:	Normal normal
Assignee:	Gentoo Genkernel Maintainers

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2015-09-22 11:46 UTC by Nicolas Bock
Modified:	2015-09-23 12:43 UTC (History)
CC List:	0 users

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Nicolas Bock gentoo-dev

2015-09-22 11:46:07 UTC

The root filesystem device is not mapped correctly to the root= parameter from the kernel command line.

The root filesystem lives in a LUKS container in a RAID-1 array. From /etc/mdadm.conf:

ARRAY /dev/md3 metadata=0.90 devices=/dev/sda3,/dev/sdb3

I include mdadm.conf in the initramfs.

The kernel command line from /etc/default/grub:

GRUB_CMDLINE_LINUX="crypt_root=/dev/md3 root=/dev/mapper/crypt-root domdadm"

After booting, the root device is mapped to:

/dev/mapper/root_md3-crypt-root -> ../dm-0

and not crypt-root as per kernel command line.