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

  i.e
initrd-2.6.39-400.297.3.e15uek.img
initrd-2.6.39-400.297.3.e15uek.img 

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.


Comments

  1. Nice tip. Keep sharing such ideas! Make sure to check this awesome online audio converter https://onlineconvertfree.com

    ReplyDelete

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

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@192.168.11.15/tmp Here, the URL specified is the ESXi host ( 192.168.11.15) under /tmp partition where logs will be copied and from there one can extract it for further log review. Happy Learning.  :)

Removing NSX-T manager extension from vCenter

In NSX-T starting from ver 2.4 NSX-T appliance got decoupled from vCenter where now its not mandatory to run NSX-T on vCenter platform only. Now NSX-T can be managed through standalone ESXi host, KVM or through container platform. As in version 2.4 there is still an option available to connect vCenter to NSX-T using Compute Manager. Here in this blog we will learn how we can unregister and register NSX-T extenstion from vCenter in case of any sync or vCenter connectivity issue with NSX-T. Lets get started.. 1) Login to NSX-T UI Go to -> System ->Compute Manager Here, vCenter is showing in Down status where the status is showing as "Not Registered" 2) When we click on "Not Registered" option its states below error. 3) When try to click on Resolve option its states below. At this stage if the Resolve option doesn't work then its require the remove the NSX-T extenstion from vCenter. To remove the NSX-T e