VirtualBox and LVM

Latest response

I'm running RHEL6 in a VirtualBox.

Any time I start RHEL, I get a Kernel Panic - not syncing: Attempted to kill init!...

If I restart RHEL, and append "rdshell" to the startup line, it will drop me to a dracut shell. I then issue the following commands:

# lvm vgscan
# lvm vgchange -ay
# blkid (I doubt that one is really necessary)
# exit

The system will then finish starting fine.

Why do I have to do that every time? Any way to avoid having to do this?

Thanks.

Responses

It'd be helpful if you could share your GRUB kernel options and a list of what modules dracut has injected into its initial ramdisk image.

grub> kernel /vmlinuz-2.6.32-504.16.2.el6.x86_64 ro root=/dev/mapper/vg_intermediate-lv_root rd_NO_LUKS rd_LVM-LV=vg_intermediate/lv_swap rd_NO_MD SYSFONT=latarcyrheb-sun16 crashkernel=auto KEYBOARDTYPE=pc KEYTABLE=us rd_LVM-LV=vg_intermediated/lv_root rd_NO_DM LANG=en_US.UTF-8 rhgb quiet

I add "rdshell" at the end to get it to boot to the dracut shell.

How can I tell what modules dracut has injected into its initial ramdisk image?

After further testing, I just type "lvm vgchange -ay" then "exit" and it boots.

If I understand it, I am manually tell it that all the volume groups are now active - I don't understand why they would be not be active to start...

Thanks.

You've got typos in your GRUB configuration. Change:

rd_LVM-LV=vg_intermediate/lv_swap

and

rd_LVM-LV=vg_intermediated/lv_root

to

rd_LVM_LV=vg_intermediate/lv_swap

and

rd_LVM_LV=vg_intermediated/lv_root

Looks like I put in an extra "d" in the line that isn't in the grub.conf - that's what I get for typing it...

It should be:

grub> kernel /vmlinuz-2.6.32-504.16.2.el6.x86_64 ro root=/dev/mapper/vg_intermediate-lv_root rd_NO_LUKS rd_LVM_LV=vg_intermediate/lv_swap rd_NO_MD SYSFONT=latarcyrheb-sun16 crashkernel=auto KEYBOARDTYPE=pc KEYTABLE=us rd_LVM_LV=vg_intermediate/lv_root rd_NO_DM LANG=en_US.UTF-8 rhgb quiet

Sorry about that...

Typo !! ...... Check logs during early stage of boot ...... you might get some clue there about this typo or other possible cause of this issue

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.