6

I have migrated a CentOS 5.11 server from VmWare to Hyper-V and when trying to boot the server. I'm getting the following error messages:

"No volume groups found" ""VolumeGroup00" not found" and consequently the other messages you see on the screenshot.

enter image description here

I have booted the VM from a live CD I had in hand and I can see & mount the volume group (lv in the volume group) fine. Here's the vgdisplay command output:

enter image description here

You can see the grub contents on the start of the first screenshot. Why do you think this is happening? Any tips?

edit: hd0 is mapped to /dev/sda as it should be.

chicks
  • 3,793
  • 10
  • 27
  • 36
user2629636
  • 774
  • 5
  • 19
  • 40
  • How are the disks attached to the vm? Hyper-V seemed to prefer ide disks when I last looked into it. Are you using the Hyper-V drivers? – Etan Reisner Sep 09 '15 at 13:47

3 Answers3

2

Finally, just after creating a bounty, I was able ti fix it by rebuilding the initrd as explained here: https://wiki.centos.org/TipsAndTricks/CreateNewInitrd

user2629636
  • 774
  • 5
  • 19
  • 40
  • ok, that would say some driver was missing in your old initrd – c4f4t0r Sep 09 '15 at 14:28
  • Thanks, this worked perfectly! If the link ever dies, the short version is: boot from CD in rescue mode, `chroot /mnt/sysimage`, `mkinitrd -f -v /boot/initrd-$(uname -r).img $(uname -r)` – Emil Styrke Jan 31 '17 at 13:41
0

boot from cdlive and use the command vgchange -ay VolGroup00 and Now Mount the mkdir /mnt/root && mount /dev/VolGroup00/LogVol00 /mnt/root

Now you can check your lvm filter with grep filter /mnt/root/etc/lvm/lvm.conf

Other thing you can check is grep volume_list /mnt/root/etc/lvm/lvm.conf

c4f4t0r
  • 5,301
  • 3
  • 31
  • 42
0

Easy fix, you'll just need to reconnect those volume groups.

  1. Boot into rescue mode.
  2. Select 'shell' Start Shell
  3. chroot into your image chroot /mnt/sysimage/
  4. Re-connect your lvm volumes vgchange -ay
  5. change your root password if you need.
  6. Reboot

additional steps may be required to fix fstab, but this should do the trick without much additional information, I had mounted a HBA iSCSI drive to a RAW Mapped drive by performing these additional steps.

  1. Remove _netdev from /etc/fstab
  2. Remove iSCSI Boot options from /etc/grub.conf

Booting the first time will take a while. (it did for me anyway, different scenario but similar situation.)

Good Luck!

Jacob Evans
  • 7,886
  • 3
  • 29
  • 57