Hi Everyone, I am very new to Centos and I think I messed it up already. Basically, I managed to installed Centos 5.6 on a Hyper-V machine under windows 2008. All worked fine. I also installed Apache, MySQL, PHP and got my server going. Today, I got a pop-up saying that new updates were available. One of which was the new kernel 2.6.18-238.12.1.el5. I applied the updates using the GUI without any errors. I got a warning stating "modfile is etc/modprobe.conf" However, when I rebooted, I got a Kernel Panic. It says that No Volume Groups found. Thanks God I had a exported Hyper-V backup so to get back my data but one day someone else will surely apply the patches again as this is a lab server. But, I am not capable of fix this issue. Can please someone give me some hints on how to fix the problem? Thanks in advance.

http://support.microsoft.com/kb/2387594 details how to fix this.

Confirming that this is the maybe most-userfriendly way of managing these kernel modules. If you don't want install DKMS from Dell manually, consider EPEL, DKMS is there too.

• Marked as answer by Wetfish Friday, July 22, 2011 8:11 AM

Unfortunately, this workaround assumes that you are still using the old Integration Components version 2.1. I checked the current versions 3.4 (and even back to 3.2) and they were all in RPM format and no longer contained the sources. Thus, no ability to "make" and none of the "how to" instructions match the current directory layout - and the mentioned files don't exist.

Unfortunately, this workaround assumes that you are still using the old Integration Components version 2.1. I checked the current versions 3.4 (and even back to 3.2) and they were all in RPM format and no longer contained the sources. Thus, no ability to "make" and none of the "how to" instructions match the current directory layout - and the mentioned files don't exist.

~

 Are You read my answer on Youre 1-st msg?

Friday, January 25, 2013 4:02 PM

http://social.technet.microsoft.com/Forums/en-US/linuxintegrationservices/thread/c0df70a8-b65c-4400-bc16-2b2985c941ef

==

 . . .

-- try RHEL 5.9 RTM  ( or CentOS 5.9  http://wiki.centos.org/Manuals/ReleaseNotes/CentOS5.9 )

 . . .

-- on CentOS 6.3 ( and 5.X ) we can use "CentOS Plus Kernel" Or kernel-ml ( and for RHEL 6.3 , see later )

 . . .

Unfortunately, the DKMS work-around is based on IC 2.1 - when the ISO still contained the source. The 3.4 (and prior) are RPMs.

~~

~

 RPMs can be unpacked

Even on Windows comp

 . . .

==

~

• Edited by Victor Miasnikov Wednesday, January 30, 2013 9:33 AM

Has anyone solved this?

I'm running Hyper-V 2012 R2 + CentOS 5.11 + LIS 4.0

If I'm using older 308 kernel - it boots, newer kernels do not, and solutions from the internet to use mkinitrd do not work.

I think I fixed it! I had CentOS 5.5  and was upgrading to CentOS 6.6 (since theres no LiveCD yet for 6.6), and installed LIS 4.0 prior to upgrading. I had a kernel panic after upgrading. I tried rerunning the install script, but the RPMS were already installed so the script failed. Here's what I did to fix.

1) Boot into previous kernel version

2) Open the LIS folder [copy it to disk if on CD]

3) Open the <version>/install.sh file for the NEW kernel version you installed, NOT the one you're running. In my case, <version> was RHEL66. 

4) Inside the file, where the rpm command is executed (in my case, it was twice), add "--force" without quotes to end of the rpm command. 

5) Re-execute install.sh as root. This should install the RPM modules. Reboot the system, but booting into the new kernel this time.

NOTE: I recommend snapshotting your VM BEFORE doing this. It worked for me, but it might not work for you.