Skip to main content

Oracle Linux VM unable to boot after P2V conversion.

Recently, I was having issue where I had decided to migrate one of my Oracle Linux machine which was running in HP Blade server to visualize and migrated through VMware converter.

Migration went successful and VM migrated successfully without any error but while powering on the Oracle Linux VM its failed with below error.

To resolve this issue I tried to boot the VM with Linix iso and run into rescue mode.

Please find below steps which I followed to boot the VM successfully.

1)     Mount the linux iso to the VM and boot it from CD
2)     At the first prompt, type linux rescue and press Enter.
3)     Change root to the mounted installation. Type chroot /mnt/sysimage and press Enter
4)     Type  ls /boot
5)     There you will see lots of initrd-xxxxx.EL.img files with different name.
6)     To verify the correct initrd-file used to /boot. Type cat /etc/grub.conf, and press Enter.
7)     From the location /etc/grub.conf I found there are two initrd files was there with the same name. From the initial error before traceback its shows the same fille where the boot stuck.
boot operation stuck with 2 same files and failed with "Pid:1, comm: switch_root Not tainted 2.6.39.-400.297.3.el5uek #1


8)     Rename one of the file with initrd-2.6.39-400.297.3.e15uek.img.old
9)     Rebuild the ramdisk. run the mkinitrd -v -f /boot/initrd-2.6.39-400.297.3.e15uek.img  2.6.39-400.297.3.e15

10)  Rebooted the VM and after that all the boot loader files successfully loaded and able to bring the Oracle Linux VM back.

This article is associated with VMware KB.


  1. Nice tip. Keep sharing such ideas! Make sure to check this awesome online audio converter


Post a Comment

Popular posts from this blog

Changing the FQDN of the vCenter appliance (VCSA)

This article states how to change the system name or the FQDN of the vCenter appliance 6.x You may not find any way to change the FQDN from the vCenter GUI either from VAMI page of from webclient as the option to change the hostname always be greyed out. Now the option left is from the command line of VCSA appliance. Below steps will make it possible to change the FQDN of the VCSA from the command line. Access the VCSA from console or from Putty session. Login with root permission Use above command in the command prompt of VCSA : /opt/vmware/share/vami/vami_config_net Opt for option 3 (Hostname) Change the hostname to new name Reboot the VCSA appliance.   After reboot you will be successfully manage to change the FQDN of the VCSA . Note: Above step is unsupported by VMware and may impact your SSL certificate and face problem while logging to vSphere Web Client. If you are using self-signed certificate, you can regenerate the certificate with the

Issue : Configure Management Network option is Grayed out into ESXi

Last week I got into an issue of one of my client into Vsphere environment where one of its ESXi went done out of the network. Issue was IP address was showing on main Esxi screen and when I tried to change the network configuration, its " Configure Management network option was greyed out.  I tried to gid into it and try to analyis its vmKernal and vmwarning logs. What I found is its VMkernal switch got removed due to unexpected reason. So to resolve the issue I tried to reconfigure its vswitch0 (vmk0) by going into Tech Mode of that Exi. Below are the steps which I followed to resolve the issue. 1) Login to ESXi 2) Press F2, Check if you " Configure Management network " is greyed out or not" if yes,    follow below 3) Press ALT+F1 to move the ESXi screen to tech mode   ( This is command line like dos) 4) login with root account 5) Run the following command into it esxcli network ip interface add --interface-name= vmk0

Collecting Logs from NSX-T Edge nodes using CLI

  This article explains how to extract the logs from NSX-T Edge nodes from CLI. Let's view the steps involved: 1) Login to NSX-T  Edge node using CLI from admin credentials. 2) Use of  " get support-bundle " for Log extraction. get support-bundle command will extract the complete logs from NSX-T manager/Edge nodes. nsx-manager-1> get support-bundle file support-bundle.tgz 3) Last step is to us e of " copy file support-bundle.tgz url " command. copy file will forward your collected logs from the NSX-T manager to the destination(URL) host from where you can download the logs. copy file support.bundle.tgz url scp://root@ Here, the URL specified is the ESXi host ( under /tmp partition where logs will be copied and from there one can extract it for further log review. Happy Learning.  :)