If you don't want to show the output from that line on the console, where should it go then?
If nowhere, you could just remove the line.
I suspect you are mixing disk characteristics as seen by vSPhere and what the guest OS sees as partitions.
These are not the same!
You can have for example multiple guest OS partitions on one VMDK.
And the inverse is also possible, you can have a VMDK, which doesn't have any partitions in the guest OS.
ohhh yes you are right i can remove that line .
my intention is to get guest partitions and my understanding so far and what i have observed is vmdk and guest partition have one to one mapping and relationship.
so if i have vm with 2 vmdks ican have c: on first vmdk and D: drive on second vmdk and so on.. i think this is the best practice and i have not seen anyone creating two partitions on same vmdk.
That is indeed the best practice, but not universally in use.
A Windows guest OS, for example, creates a partition as well, not in use for the users of the guest OS.
In short, currently, there is no fool-proof method to link a VMDK with one or more guest partitions.
Even if you have a one-to-one mapping, it's impossible to say which VMDK corresponds with which guest OS partition.
Whatever method you might find on the Internet, I can produce you an example where the method will not work.
Sorry, no real solution available (at this point in time).
I thought there might be some way of checking this but as yu mentioned no solution at this point of time so only option is to check through size of vmdk.however that causes confusion when two vmdk have same size.
Indeed, and it can be even more confusing with specific guest OSs.
Note that Windows creates a small System partition, so comparing VMDK sizes would already be a problem.