Bug 258449

Summary:	sys-kernel/genkernel Not truly distinguishes LABEL at root mount on booting
Product:	Gentoo Linux	Reporter:	Kazankov Alexander <johnrdoe63>
Component:	Current packages	Assignee:	Gentoo Genkernel Maintainers <genkernel>
Status:	RESOLVED FIXED
Severity:	critical	CC:	sping
Priority:	High
Version:	2008.0
Hardware:	x86
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Kazankov Alexander 2009-02-10 14:32:55 UTC

At system loading the root who is on soft-raid is not mounted, saying that cannot find the device and enumerates all composite disks soft-raid.

Reproducible: Always

Steps to Reproduce:
1. Make root (/) on /dev/md2(examp.). Compile kernel with raid & dm support.
2. mkfs.ext3 -L / /dev/md2
3. genkernel --install --dmraid --disklable all
4. Adding in grub.conf: real_root=LABEL=/
5. Reboot

Actual Results:  
System dosen't boot.

Expected Results:  
System booting to login prompt.

If Adding in grub.conf: real_root=LABEL=/dev/md2, everything boot.
Into fstab all my disk mounting with "LABEL".

Comment 1 Peter Alfredsen (RETIRED) gentoo-dev

2009-02-11 02:05:33 UTC

Making a wild guess, I assign this to genkernel.

Comment 2 Kazankov Alexander 2009-02-11 06:38:15 UTC

Why genkernel?

After all, when the system loading, any genkernel is not started or I am not right!?
After an activation line "mdev" and "dmraid" it cannot mount root, referring on "/dev/hda5/dev/hdc5" that it not the block device. If to enter into this moment "/dev/hda5" that the system will continue to be loaded, but not on long. At the moment of repeated connection of the radical, stops that cannot find LABEL =/. 

The Most interesting, if in grub.conf to specify real_root=/dev/md2 the system completely will boot without what or problems.

Without labels terribly inconveniently!

Comment 3 Kazankov Alexander 2009-02-11 07:28:21 UTC

Though yes. In a file linuxrc function setup_md_device, mdX form only if the radical is specified like /dev/mdX.

If adding domdadm to kernel parm the picture becomes another:

active. mdev
mdadm: /dev/md0 has been started with 1 drive (out of 2)
....
....
mdadm: /dev/md9 has been started with 1 drive (out of 2)
Detected real_root=/dev/hda5
/dev/hdc5
/dev/md2
!! Block device /dev/hda5
/dev/hdc5
/dev/md2 is not a valid root device...
!! Could not find the root block device in.

But if enter /dev/md2, the system will boot, but cat /proc/mdstat will show that everywhere on one disk. $(

Comment 4 Kazankov Alexander 2009-04-26 16:39:53 UTC

maybe about that http://bugs.gentoo.org/show_bug.cgi?id=156640

Comment 5 Sebastian Pipping gentoo-dev

2011-01-11 16:04:17 UTC

Without being an expert: real_root=LABEL=/dev/md2 and real_root=LABEL=/ look rather odd to me - is that really wanted?

Also, could you try again with the experimental branch exposed by genkernel-99999 (five nines)?

I could imagine that this patch already fixed your problem:
http://git.overlays.gentoo.org/gitweb/?p=proj/genkernel.git;a=commitdiff;h=e590a493ead9a21e356215b5394172717b0f615d

If I don't hear anything in two weeks I may close this bug.

Comment 6 Sebastian Pipping gentoo-dev

2011-05-31 01:05:55 UTC

(In reply to comment #5)
> If I don't hear anything in two weeks I may close this bug.

Closing.