RPC: Port mapper failure - Unable to receive: errno 113 (No route to host)

So I was trying to make an NFS server on my Linux box running Centos 7 and after successfully installing the NFS utilities and exporting a share called /nfsshare, I was trying to mount it on my client box. However when I ran the command showmount -e,  which should show the existing mounts on the nfs server, I got the below error message.

clnt_create: RPC: Port mapper failure - Unable to receive: errno 113 (No route to host)

So I had to add some parameters on my NFS server's firewall and after that everything was fixed. On my NFS server I had to say:

firewall-cmd --permanent --add-service=mountd
firewall-cmd --permanent --add-service=nfs
firewall-cmd --permanent --add-service=rpc-bind
firewall-cmd --reload


Incorrect disk usage information on a Windows Server

I have a windows 2008 server and I ran into a situation, where one of my disks was showing up incorrect used space information and that was driving me crazy!

As you can see below, my drive was showing up as 81.6 GB utilized but in reality, I was only using 8GB of it. So where was the extra space coming from?! 


I checked my shadow copy settings because sometimes that is the culprit, but I had none configured.


Also, I ran tools like SpaceMonger which I use to identify space issues and that did not give me anything. So after a while, one of my team member pointed me to check the hidden files and system files and then I checked the size of my hidden "Recycle bin" which I found to be eating up all that extra space!


How to remove conflicting VIB's during Esxi host upgrade

So you want to upgrade your Esxi version from 5.5 to 6.5 using the host upgrade option with the vsphere client, which in my case that is what I was trying to perform. I have a Cisco UCS server, so I downloaded the custom Cisco image from the Vmware website to make life a little easy during the upgrade.

So when you create a new baseline for your Cisco UCS image and attach it to the host (I am assuming you guys know how to create a baseline and attach it to the host) and within update manager click on the "Scan for Updates" button and select "Upgrades".


You notice that after the scan completes in the summary box below, that the status details say that there are a few conflicting VIB's that need to be removed in order for the upgrade to proceed.


Here is what you do to remove those VIB's, so that you can proceed with the upgrade.

  • Enable SSH on the desired host from the security profile of the host
  • Use Putty and ssh to the host using the root credentails
  • Once at the console, type  the command --> esxcli software vib list
  • Match the conflicting Vib name that you encountered earlier to this list and note down the name. (In my case it was net-mst)
  • So at the ssh console type the command --> esxcli software vib remove -n=net-mst
  • Once the VIB has been removed, it will prompt you for the reboot. So go ahead and reboot your host.
  • Once the host is back and connected within your vcenter, go under update manager and scan for updates again and this time, you should see the image being Non-Compliant. Now you can proceed with the Remediation of this host to apply this image.

Can i cancel Vmware snapshot, stuck at 99%!

This is probably the most trickiest decision to make at any time, you have clicked on the action to delete a snapshot on a virtual machine and its stuck at 99% for like a very long time.  You want to cancel the task, but you are not sure if its safe?!

I have had to do this a couple of times and I am thankful, everything has gotten back to normal. So the situation is, you have a snapshot at 99% and you gather up the courage to cancel it and it gets stuck again and you are just waiting! First I recommend reading up the below blog and do a quick check if at all you need to perform a hard kill. (Read this). Its a pretty well written blog and in case you want to do ahead, which I did on a couple of occasions, just enabled SSH on your host and type in the command:

services.sh restart ( Please note that this will not affect your working virtual machines and its completely safe, you might see the host getting disconnected from vcentre for a bit but it will come back, so don't worry)

Once done, the snapshot tasks will be cancelled and then you may be prompted to consolidate your disks, which would be slow as well but please don't cancel the consolidation at this point.

I know it's not recommended to cancel a snapshot, but sometimes you have to take a leap of faith!

A file I/O error occurred while accessing - Vmware converter V2V


So this morning, I was trying to convert a virtual machine running on a Hyper-V host on a different domain to another using the Vmware converter tool. The destination was to the Vmware 5.5 cluster. I had installed the vmware converter on the Hyper-V machine and ran through the initial setup and clicked on the finish button. When I did that after a while I got an error "A file I/O error occurred while accessing". After looking around for a while I realized that from my source machine I cannot ping the FQDN of my Vcenter server and the destination host that I am trying to migrate this virtual machine to, even though I can ping the IP's the DNS names cannot be pinged.

So it was pretty straight forward from this point, I opened by the local hosts file, on the source server and made some manual entries to the vcenter server and the destination vmware host. After I did that I re-ran my conversion tool and this time it worked! (I hope you know how to get the local host file on a server to make manual entries, if you don't then drop me a comment and I shall respond back!)