VMware Cloud Community
jperlorx
Contributor
Contributor

Error: Unable to reconfigure the destination virtual machine.

Buenos dias, estoy intentando virtualizar un Ubuntu Server 14.04.1 con un converter 5.5.1 y me da el siguiente error  al 97%

FAILED: An error occurred during the conversion: 'GrubInstaller::InstallGrub: /usr/lib/vmware-converter/installGrub.sh failed with return code: 0, and message: Installing GRUB1 on (hd0)... [ Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists the possible completions of a device/filename. ] grub> root (hd0,0) grub> setup (hd0) Checking if "/boot/grub/stage1" exists... no Checking if "/grub/stage1" exists... no Error 15:
File not found grub> '



Alguna idea?...


he actualizado el grub a la version GRUB2 y me falla igualmente, y he vuelto a bajar la version.


Saludos y gracias

0 Kudos
9 Replies
patanassov
VMware Employee
VMware Employee

Hola,

it is strange to have GRUB1 on Ubuntu 14. What is the error from the GRUB2 attempt? Can you send the logs?

Regards,

Plamen

0 Kudos
jperlorx
Contributor
Contributor

Hola,

I installed the GRUB2 cversion for ubuntu server and still gives me the same error, attached log

FAILED: An error occurred during the conversion: 'GrubInstaller::InstallGrub: /usr/lib/vmware-converter/installGrub.sh failed with return code: 127, and message: Installing GRUB1 on (hd0)... /vmware-updateGrub.sh: 52: /vmware-updateGrub.sh: grub: not found Error installing GRUB Command: grub --no-floppy --batch --device-map="/vmware-device.map" root (hd0,0) setup (hd0) Error running vmware-updateGrub.sh through chroot into /mnt/p2v-src-root /usr/lib/vmware-converter/installGrub.sh: line 143: /mnt/p2v-src-root:

Is a directory '

0 Kudos
jperlorx
Contributor
Contributor

I have a question ... any agent or application must be installed on Ubuntu for virtualization, I'm doing it from another computer that has the Converter,

0 Kudos
patanassov
VMware Employee
VMware Employee

Hi

Converter determines the grub version by calling grub-install. It has probably remained from grub1. Check it and change it accordingly.

Regards

0 Kudos
patanassov
VMware Employee
VMware Employee

In case of live Linux sources, Converter uploads a sysinfo utility to gather the OS and hardware info of the source, and then removes it. It is not like the Windows agent.

0 Kudos
jperlorx
Contributor
Contributor

Good morning ...

grub-install -v, --verbose print detailed messages.

and grub-install -V, --version shows the version of the program

Where can I change the VMWare Converter script ??

regards

0 Kudos
jperlorx
Contributor
Contributor

Version of grub-install

jperlorx@ngadichuli:/etc/default$ grub-install --version

grub-install (GRUB) 2.02~beta2-9ubuntu1

0 Kudos
patanassov
VMware Employee
VMware Employee

Ah, sh*t! The fix for version parsing didn't get into 5.5. It will be in the next release, sorry.

It is difficult to manually fix the helper. It would be easier to make a wrapper of grub-install at the source which would return the version with "-v" argument.

Regards

0 Kudos
Theles
Contributor
Contributor

This probably will be too late to help you, but, I had the same issue, and it might help someone who's seeking this, as I did a few days ago. And with the help of the folks of opensuse forums, I was able to solve it. The actions below were made using the vCenter Converter 6.

The original post with the solution is this: https://forums.opensuse.org/showthread.php/525645-vCenter-Converter-failed-code-127-RAID-and-LVM?p=2...

Just a little background, the virtualization failed at 97%, right after the grub install.

1 - Booted up the VM with the iso in Rescue mode, and logon as root(no pass)

2 - Identify the partitions and mount the root partition " / " on /mnt

3 - Mount the other existing partitions on the subsequent folders, like if /home was mounted in /dev/sda3, then, mount /dev/sda3 /mnt/home

4 - Mount the rest and chroot as follow:

mount --rbind /proc /mnt/proc 
mount --rbind /sys /mnt/sys
mount --rbind /dev /mnt/dev
chroot /mnt

5 - run blkid and take note the new UUIDs of the partitions.

Output of blkid 
/dev/loop0: TYPE="squashfs"
/dev/loop1: TYPE="squashfs"
/dev/loop2: TYPE="squashfs"
/dev/loop3: TYPE="squashfs"
/dev/loop4: TYPE="squashfs"
/dev/sda1: UUID="59b620ec-fb0d-40ab-a8b8-1951c1ed52b9" TYPE="swap" PARTUUID="1c14d8a9-01" /
dev/sda2: UUID="16fbb53e-6b84-4b5a-ab2e-71e91bb0704e" TYPE="ext4" PARTUUID="1c14d8a9-02" - boot partition
/dev/sda3: UUID="a3b48686-9add-4824-8a70-bfc5fbecb7d4" TYPE="ext4" PARTUUID="1c14d8a9-03" - usr partition
/dev/sda4: UUID="6814a062-66c0-4381-9fe0-ab41a66b4a4c" TYPE="ext4" PARTUUID="1c14d8a9-04" - root partition

6 - Update the /etc/fstab, and, if it was created as btrfs, remove the aditional mount point lines and replace the btrfs with the TYPE detected on the blkid, which in my case was ext4:

Content of the old /etc/fstab 
UUID=a4aba881-1637-4909-9809-6b9f7884960d swap swap defaults 0 0
UUID=66d9c957-3caa-4a84-8432-a85a3434cfad / btrfs defaults 0 0
UUID=ee41ddf1-dcfd-4520-bdb5-2da5647ab336 /boot                ext4       acl,user_xattr        1 2
UUID=66d9c957-3caa-4a84-8432-a85a3434cfad /boot/grub2/i386-pc btrfs subvol=@/boot/grub2/i386-pc 0 0
UUID=66d9c957-3caa-4a84-8432-a85a3434cfad /boot/grub2/x86_64-efi btrfs subvol=@/boot/grub2/x86_64-efi 0 0
UUID=66d9c957-3caa-4a84-8432-a85a3434cfad /home btrfs subvol=@/home 0 0
UUID=66d9c957-3caa-4a84-8432-a85a3434cfad /opt btrfs subvol=@/opt 0 0
UUID=66d9c957-3caa-4a84-8432-a85a3434cfad /srv btrfs subvol=@/srv 0 0
UUID=66d9c957-3caa-4a84-8432-a85a3434cfad /tmp btrfs subvol=@/tmp 0 0
UUID=873338a7-102f-479b-9c99-b972415bf9f4 /usr                 btrfs      defaults              0 0
UUID=66d9c957-3caa-4a84-8432-a85a3434cfad /usr/local btrfs subvol=@/usr/local 0 0
UUID=66d9c957-3caa-4a84-8432-a85a3434cfad /var/crash btrfs subvol=@/var/crash 0 0
UUID=66d9c957-3caa-4a84-8432-a85a3434cfad /var/lib/libvirt/images btrfs subvol=@/var/lib/libvirt/images 0 0
UUID=66d9c957-3caa-4a84-8432-a85a3434cfad /var/lib/mailman btrfs subvol=@/var/lib/mailman 0 0
UUID=66d9c957-3caa-4a84-8432-a85a3434cfad /var/lib/mariadb btrfs subvol=@/var/lib/mariadb 0 0
UUID=66d9c957-3caa-4a84-8432-a85a3434cfad /var/lib/mysql btrfs subvol=@/var/lib/mysql 0 0
UUID=66d9c957-3caa-4a84-8432-a85a3434cfad /var/lib/named btrfs subvol=@/var/lib/named 0 0
UUID=66d9c957-3caa-4a84-8432-a85a3434cfad /var/lib/pgsql btrfs subvol=@/var/lib/pgsql 0 0
UUID=66d9c957-3caa-4a84-8432-a85a3434cfad /var/log btrfs subvol=@/var/log 0 0
UUID=66d9c957-3caa-4a84-8432-a85a3434cfad /var/opt btrfs subvol=@/var/opt 0 0
UUID=66d9c957-3caa-4a84-8432-a85a3434cfad /var/spool btrfs subvol=@/var/spool 0 0
UUID=66d9c957-3caa-4a84-8432-a85a3434cfad /var/tmp btrfs subvol=@/var/tmp 0 0
UUID=66d9c957-3caa-4a84-8432-a85a3434cfad /.snapshots btrfs subvol=@/.snapshots 0 0

content of updated /etc/fstab 
UUID=59b620ec-fb0d-40ab-a8b8-1951c1ed52b9 swap swap defaults 0 0
UUID=6814a062-66c0-4381-9fe0-ab41a66b4a4c / ext4 defaults 0 0
UUID=16fbb53e-6b84-4b5a-ab2e-71e91bb0704e /boot                ext4       acl,user_xattr        1 2
UUID=a3b48686-9add-4824-8a70-bfc5fbecb7d4 /usr                 ext4      defaults              0 0

7 - After this, I ran in order:

mkinitrd

grub2-install /dev/sda

grub2-mkconfig -o /boot/grub2/grub.cfg

grub2-install /dev/sda

- exited from chroot

umount -a

reboot

OBS: If your disk is GPT, after the grub2-install you might get a message informing that it could not install on it, yada yada yada... In this case, you must create a BIOS partition. I use cgdisk in order to do so.

#cgdisk /dev/sda

- in my case, I excluded the swap, and created a new partition, of 5MB using the code ef02, recreating the swap using the remain space:

wdprd:~ # cgdisk /dev/sda 
cgdisk 0.8.8   Disk Drive: /dev/sda Size: 286676992, 136.7 GiB  
Part. #     Size        Partition Type            Partition Name
----------------------------------------------------------------
         47.0 KiB    free space
1        5.0 MiB     BIOS boot partition       bios
5        8.0 GiB     Linux swap                swap
2        70.0 GiB    Linux filesystem          usr
3        58.0 GiB    Linux filesystem          raiz
4        720.0 MiB   Linux filesystem          boot
         943.5 KiB   free space

At this point the machine should boot up successfully. If it stop saying that the boot failed, reboot in rescue mode again, remount everything and double check UUIDs in the fstab.

8 - You also MUST check if the the /home has being copied with full content. In one of the servers, it wasn't. So, I went back on the physical machine and:

server😕 # tar -zcvf home.tar.gz /home

copy the file to the vm and unzip it overwriting the /home

That's all folks!

Theles Silveira

0 Kudos