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

VM Creation Date & Time from Powercli

Most of the times we have several requirement when we talk about IT environment like designing , deployment , compliance check or for Security auditing the environment. Somewhere during security auditing we require to provide several information to security team to get successful audit. One of them is the compliance of Virtual machine auditing of creation date and time. Here into this post we will explore how to get the creation date and time of virtual machine hosted into the vCenter or ESXi. To get the details we will use VMware Powercli to extract the details. By default there is no function added into Powercli to get such details, so here we will add a function of vm creation date. Below is the function which needed to be copy and paste into the Powercli. ======================================================================= function  Get-VMCreationTime  {     $vms  =  get-vm     $vmevts  = @()     $vmevt  =  new-object  PSObject     for

Unable to poweron the VM. (Failed to lock the file)

I have encountered may issues like where after some upgrade or migration we were unable to power on the VM. Figure 1 An error was received from the ESX host while powering on VM HSSVSQL01. Failed to start the virtual machine. Cannot open the disk '/vmfs/volumes/578d835c-18b2c97a-9b0d-0025b5f13920/SAMPLE1_cloud/000000.vmdk' or one of the snapshot disks it depends on. Failed to lock the file In above Figure:1, where while powering on the VM, its prompt for an error. Well, there are several reason for where the VM unable to poweron and you can find many article on this. Here in this article we will discuss to resolve this issue. Please use below step to resolve the disk lock issue  C hecked that VM is running on snapshot if its getting error " VM Consolidation required". Checked the snapshot manager if its showing any snapshot. If yes, try to delete the  snapshot. Verified the same from Esxi cl
google.com, pub-4920175566720914, DIRECT, f08c47fec0942fa0 google.com, pub-4920175566720914, DIRECT, f08c47fec0942fa0