Mike's Realm chown -R us ./base


P2V: VolGroup00 not found – Linux LVM

So you P2V'd a Linux box (CentOS, RedHat, Oracle, etc.) that is using LVM and now when it boots you get:

Reading all physical volumes. This may take awhile...
Volume group "VolGroup00" not found
Unable to access resume device (/dev/VolGroup00/LogVol01)
mount: could not find filesystem '/dev/root'
setuproot: moving /dev failed: No such file or directory
setuproot: error mounting /proc: No such file or directory
setuproot: error mounting /sys: No such file or directory
switchroot: mount failed: No such file or directory
Kernel panic - not syncing: Attempted to kill init!

Well that sucks--basically initrd didn't have the right drivers to access the file system.

Reboot the VM with the Linux distro ISO attached

Then it boots from the CD follow the instructions to enter Linux Rescue (usually you type "linux rescue" at the boot prompt)

Now we can rebuild initrd with the missing drivers.




Now hit tab and it will auto complete then add the text that was autocompleted when you hit tab except for the .img

So your command should look like:

Hit enter and it will do it's thing with a lot of output coming out, when it's done type exit annd exit again and the VM will reboot automatically.  Should boot up just fine this time.

Comments (17) Trackbacks (0)
  1. It’s very helpful. Thank you man.

  2. i’ve had similar problems and developed a p2v procedure that include exactly your same step


  3. Your solution saved a lot of RD, hat’s of for your article, it saved my day

  4. Very useful thanks a lot.

  5. Hi,

    Same my day
    maybe my job too 😉

  6. Thanks so much,,, saved my day too,

  7. Michael,
    thank you for this great working post, it really saved me. I did a WAN P2V of a production environment, it took 15 hours. This really SAVED THE DAY. really great stuff. ciao from Italy

  8. Many Thanks! This really helped me out.

  9. Thanks mate! Just spent a couple of days converting physical machine to virtual and then was heart broken when the VM didn’t boot. This solved my problem though. Thanks again!
    Nick from Australia.

  10. Worked on CentOS 6.4 Briliantly!
    Thanks lad!

  11. Works fine with Fedora 10 to ESXi 4.1.
    Thanks a lot!

Leave a comment

No trackbacks yet.