Bug 170753 - LUKS + RAID1: crypt_root does not create md# devices
Bug#: 170753 Product:  Gentoo Hosted Projects Version: unspecified Platform: All
OS/Version: Linux Status: RESOLVED Severity: normal Priority: P2
Resolution: FIXED Assigned To: genkernel@gentoo.org Reported By: n.schlumberger@bluewin.ch
Component: genkernel
URL: 
Summary: LUKS + RAID1: crypt_root does not create md# devices
Keywords:  
Status Whiteboard: 
Opened: 2007-03-13 16:55 0000
Description:   Opened: 2007-03-13 16:55 0000 
Booting a RAID1 system with LUKS encrypted ROOT.
Genkernel complains about missing device (/dev/md3 in my case)
adding root= or real_root= to grub.conf helped creating the missing devices,
but would not boot set root to /dev/mapper/root.
After reading through genkernel's initrd.scripts and linuxrc, I found a missing
line in initrd.scripts

Reproducible: Always

Actual Results:  
Not cleanly booting system.
Additional typing is need to get it running (setting root device)

Expected Results:  
clean boot, with interrupt for luks passphrase.

posting patch in next comment

------- Comment #1 From Nicolas Schlumberger 2007-03-13 16:58:57 0000 ------- 
Created an attachment (id=113186) [details]
initrd.script-patch, created with diff -upN

The patch, as announced.

BTW. I've been running genkernel-3.4.6, no guarantee on later versions

cheers
nico

------- Comment #2 From Chris Gianelloni (RETIRED) 2007-06-21 00:35:31 0000 ------- 
OK.  I've added this to SVN and it will show up in the next genkernel release.

------- Comment #3 From Nicolas Schlumberger 2007-06-21 00:53:58 0000 ------- 
Thanks a lot

I already started to fear that my report was incomplete, or too unimportant.

cheers
nico

------- Comment #4 From Chris Gianelloni (RETIRED) 2007-06-21 17:22:03 0000 ------- 
Nah, we had taken a break after 2007.0's release, and then I got a new job and
moved across the country.  I'm just now returning and starting to churn through
the 1000+ bugs in my Inbox...

------- Comment #5 From Chris Gianelloni (RETIRED) 2007-08-22 19:54:06 0000 ------- 
Please test genkernel 3.4.9_prer1 or better.  This should be fixed now.