desadi10's Accepted Solutions

Hi MohamadAlhoussein, Thanks so much for your reply. I solved the problem deleting the RAID Volume in the physical server, then, i tried to install the VMware ESXi 6.0 again and i didn't have any problem.

Finally, I managed to solve the problem. I booted from the CD-ROM Drive, I entered in the rescue mode, I identified the disk containing the root file system, I selected the option to initialise the shell and I ran these commands: root@debian:~# grub-install /dev/sda root@debian:~# update-grub root@debian:~# reboot

After look for a lot of information about this issue, I found the solution. This problem is because of an old snapshot linked to vmx. Before doing anything, we must check if there are blocked VMDSs in the Proxy in this link: “Removing Stuck VMDK’s from the Veeam Proxy - https://www.veeam.com/kb1775” After this, we can repair manually the replica in this link: “How-To: Manually Repair a VMware Replica created by Veeam - https://www.veeam.com/kb1773 “ After this, my problem was solved.

I contacted with Veeam Support, and i download the mlocate service from this page: http://download.opensuse.org/repositories/server:/search/SLE_11_SP3/x86_64/ I installed it with the wget command. Thanks so much.

I contacted with Veeam and I solved this problem. I have this problem with the vCenter virtual machine, so that, I added a standalone server where there was the vCenter virtual machine through DNS, I configure the replication job and I didn’t choose the “Enable application-aware processing” check. Apparently, the problem is solved.