[Bug 349161] Missing entries in the init script of the initrd image makes the system unbootable on dmraid

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: Missing entries in the init script of the initrd image makes the system unbootable on dmraid


https://bugzilla.redhat.com/show_bug.cgi?id=349161


fernando at lozano.eti.br changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |fernando at lozano.eti.br
  Status Whiteboard| bzcl34nup                  |bzcl34nup




------- Additional Comments From fernando at lozano.eti.br  2008-05-13 17:33 EST -------
It looks the same problem happens with RHEL5 (5.1 and 5.2 beta). See ticket
#1825896 on RHN Support.

I have a server using a Intel S5000VSA SATAR motherboard and three SATA hard
disks configured as a RAID0 array. RHEL 5.0 installs fine, both 32 ad x86_64,
but 5.1 and 5.2 beta don't boot after install, although rescue mode works fine.

If I install RHEL5.0 and then update the kernel via RHN, the system can't boot
anynore, showing the same panic as RHEL 5.1/5.2 fresh installs.

After the update, I checked the contents of initrd before and after the update.
I found I could fix it adding the following lines to the initrd init script:

rmparts sdc
rmparts sdb
rmparts sda
dm create ddf1_4c5349202020202080862682000000003547905e00000a28 0 2923825152
striped 3 128 8:0 0 8:16 0 8:32 0
dm partadd ddf1_4c5349202020202080862682000000003547905e00000a28 

My RAID controller us identifyed by lspci as "Intel 631xESB/632xESB/ SATA
Storage Controller" 


-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.