ESX P2V RedHat Linux Kernel Panic not syncing
RedHat Linux 4 Kernel Panic not syncing kill init no volume groups found
I just imaged my RHEL 4 system that was running on a Dell Poweredge 2950 server using Acronis software and I restored the image to a VmWare virtual machine.
Dell Poweredge 2950 - RAID 5
I got it fixed:
http://kb.vmware.com/selfs
http://kb.vmware.com/selfs
Virtual machine does not boot after being converted from a physical Red Hat machine
Details
• A converted physical machine running Red Hat does not boot as expected
• Virtual machine fails to boot after conversion
• The boot process halts with an error
• Possible errors include:
o No volume groups found
o Kernel panic - not syncing: Attempted to kill init!
o VFS: Cannot open root device "LABEL=/" or 00:00
o Please append a correct = "root=" boot option
o Kernel panic: VFS: Unable to mount root fs on 00:00
Solution
The issue occurs because the operating system's ramdisk image does not include the drivers or modules for the virtual SCSI adapter configured for the virtual machine. These modules are not in the ramdisk image because the image was originally created on a system that did not use this hardware. You must replace the existing ramdisk image with one that includes the proper drivers.
Converter 3.0.x did not support hot cloning of Linux operating systems or the configuration of resulting virtual machines for new virtual hardware. It only supported cold cloning without configuration. vCenter Converter 4.0 does support hot cloning and the configuration of some Linux operating systems, including Red Hat. Refer to the manual for a list of supported versions.
Please validate that each troubleshooting step below is true for your environment. Each step will provide instructions or a link to a document, in order to eliminate possible causes and take corrective action as necessary. The steps are ordered in the most appropriate sequence to isolate the issue and identify the proper resolution. Please do not skip a step.
Note: If you perform a corrective action in any of the following steps, attempt booting the virtual machine again.
1. If your physical source machine has a vCenter Converter 4.0 supported version of Red Hat installed and you still have access to it:
a. Upgrade to vCenter Converter 4.0 if you have not done so already.
b. Run Converter and perform another physical to virtual conversion. This virtual machine should boot.
2. If you are unable to use Converter to create a new Red Hat virtual machine that boots, you will need to modify the guest operating system.
Notes:
• Before beginning, VMware recommends that you take a snapshot of your virtual machine. VMware also recommends that you back up any files that you edit in the following steps. Once the operating system is working the snapshot and back up files can be deleted.
• In these steps, you will be making sure that the operating system has the appropriate type of virtual hard disk controller. This can be either LSI Logic or BusLogic. Choose the controller that is most suited to your version of Red Hat and make sure that it is this controller that is being presented to the virtual machine.
c. Boot the virtual machine from the first Red Hat installation disk.
d. At the first prompt, type linux rescue and press Enter.
e. Change root to the mounted installation. Type chroot /mnt/sysimage and press Enter.
f. If the physical computer was IDE based, replace any instance of the text /dev/hda with /dev/sda in the files /etc/fstab, /boot/grub/device.map, and /boot/grub/grub.conf.
g. Ensure that grub is installed properly. Type grub-install and press Enter.
h. If the file /etc/modules.conf exists, edit it and remove any existing entries.
i. Edit the file /etc/modprobe.conf.
i. Look for alias ethx module entries, where x is replaced by a number and module is replaced by text. Change each module entry to pcnet32.
ii. If you will be using BusLogic:
Look for alias scsi_hostadapterx module entries, where x is replaced by a number and module is replaced by text. Change each module entry to BusLogic.
iii. If you will be using LSI Logic:
Look for alias scsi_hostadapterx module entries, where x is replaced by a number and module is replaced by text. Change each module entry to mptscsih.
Additionally, look for an alias scsi_hostadapter module entry, where module is replaced by text and there is no number after hostadapter. If it exists, replace module with mptbase. If it does not exist, add alias scsi_hostadapter mptbase directly above the line that now reads alias scsi_hostadapter1 mptscsih.
j. Determine the full path to the ramdisk image to be rebuilt. The file will is located in /boot. List the contents of the directory by typing ls /boot and pressing Enter. There will be a file with a name similar to initrd-2.6.9-42.EL.img. In this example, the full path to the ramdisk image is /boot/initrd-2.6.9-42.EL.i
Note: If there is more than one initrd- file in /boot, type cat /etc/grub.conf and press Enter to determine which file is being used.
k. Determine the kernel version to use for rebuilding the ramdisk image. Type ls /lib/modules and press Enter. In this example, you will see the directory 2.6.9-42.EL. Make a note of this.
Note: If there is more than one directory shown, type cat /etc/grub.conf and press Enter to determine which kernel version is being used.
l. Rebuild the ramdisk. Type the command mkinitrd -v -f /boot/initrd-2.6.9-42.EL.i
3. If you are unable to use a supported version of Red Hat, or the procedure in 2. did not work:
. Modify the physical machine to have support for either BusLogic or LSI Logic.
a. Convert the physical machine again.
目录 返回
首页