[BlueOnyx:12050] Re: Dracut can't mount LVM volumes

Jason Ozin bluequartz at ozin.com
Sat Jan 19 17:16:55 -05 2013


Further to the below, I have more information.

 

Kernel 5.9 has built in support for Hyper-V

(see:
http://virtualisationandmanagement.wordpress.com/2013/01/10/red-hat-rhel-5-9
-now-includes-the-hyper-v-linux-integration-services-built-in/ )

so actually all you need to do is:

 

Boot into the old kernel

Remove the old Hyper-V components as follows:

 

Execute the following steps in the bash shell.

1. First, execute:

rpm -qa | grep microsoft

Example:

On a RHEL 5.8 system, you will see the following:

# rpm -qa | grep microsoft

kmod-microsoft-hyper-v-3.4-1.20120727

microsoft-hyper-v-3.4.20120727

2. Next, execute:

rpm -e microsoft-hyper-v-<version string from step 1>
kmod-microsoft-hyper-v-<version string from step 1>

 

            Then reboot into the new kernel

 

Jason Ozin

 

================================================

 

Hi Chuck

 

Don't panic. I think I know what this is.

 

I guess you are virtualised using Hyper-V and you recently did a yum update.
The new kernel thus the new kernel cannot see your disks.

 

The quick fix is to reboot, hit a key to get to the boot menu and select an
earlier kernel.

 

The next fix is to edit both:

 

/boot/grub/grub.conf

/etc/grub.conf  

 

And make the working kernel the default.

 

Then once you have calmed down look at post 11567 and 11643 in this list for
the way to make the new kernel behave.

 

Jason Ozin

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.blueonyx.it/pipermail/blueonyx/attachments/20130119/b2a6dc56/attachment.html>


More information about the Blueonyx mailing list