<div class="gmail_quote">On Mon, Feb 28, 2011 at 12:06 PM, Alan Bartlett <span dir="ltr"><<a href="mailto:ajb@elrepo.org">ajb@elrepo.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div><div></div><div class="h5">On 28 February 2011 18:26, Miguel Alvarez <<a href="mailto:miguellvrz9@gmail.com">miguellvrz9@gmail.com</a>> wrote:<br>
<br>
> I just installed kernel-ml-2.6.37-1.el5.elrepo on my HP DL-380 G7 (also G6<br>
> with same results) and when it comes up, the system kernel panics in the<br>
> ramdisk. Looks like there are four modules that exist in my stock<br>
> kernel-2.6.18-194.32.1.el5 ramdisk that don't exist in 2.6.37:<br>
><br>
> dm-region_hash.ko<br>
> dm-mem-cache.ko<br>
> dm-message.ko<br>
> dm-raid45.ko<br>
><br>
> I didn't see any new device-mapper packages in the repo so is there<br>
> something else that I'm missing or need to update?<br>
<br>
</div></div>Hi Miguel,<br>
<br>
I currently don't have access to my el5 system that is running<br>
kernel-ml-2.6.35-11.el5.elrepo, so I am relying on memory. ;-)<br>
<br>
Please boot up the current distro kernel (-194.32.1.el5, if CentOS, or<br>
-238.1.1.el5, if RHEL) and go to the /etc/sysconfig/mkinitrd/<br>
directory. Do you have a file name "dmraid"? If not, create one with<br>
one line contents:<br>
<br>
DMRAID=no<br>
<br>
The file should be UID/GID == root, with mode == 755.<br>
<br>
Now go to the /boot directory and re-make the initrd for the<br>
2.6.37-1.el5.elrepo kernel. If I've remembered the details correctly,<br>
that should solve the problem.<br>
<br>
It might also be worthwhile adding:<br>
<br>
nodmraid<br>
<br>
to the kernel boot parameters. (Via the line in your /etc/grub.conf file.)<br>
<br>
Regards,<br>
Alan.<br></blockquote><div><br>Hi Alan,<br><br>Thanks for the reply. I created the file, ensured perms/ownership, re-created the ramdisk and added the 'nodmraid' boot option. Unfortunately, I'm still panicing. It looks like it's an issue detecting lvm volumes (see attached screenshots).<br>
<br>When 2.6.18 boots, it scans for logical volumes and finds the "VolGroup00" VG. When 2.6.37 boots, it scans but is unable to find anything and naturally panic shortly thereafter. Any ideas?<br><br>Thanks again</div>
</div>