VMware Cloud Community
lytledd
Contributor
Contributor
Jump to solution

ESXi 6.0.0, 9239799 vmware tools breakage

I just upgraded from ESXi 6.0.0, 7967664 to 9239799 via the handy web link:

https://esxi-patches.v-front.de/

After the system came back up, all VMs are reporting, "Running, (Unsupported)" for vmware tools

Browsing to the vmimages shows the folder is empty.

From a ssh console, I show the below in /storage/packages

drwxr-xr-x1 root root         8 Nov 19  2016 6.5.0
drwxr-xr-x1 root root         8 Nov 19  2016 var

Is anybody else seeing this?  Is the fix just as simple as copying the 6.5.0 folder to 6.0.0?

Thanks,


Doug

Thanks, Doug
1 Solution

Accepted Solutions
Vijay2027
Expert
Expert
Jump to solution

I don't expect to see 6.5.0 dir on ESXi 6.0

Anyways create a 6.0.0 dir and copy the content from a diff ESXi 6.0 host.

View solution in original post

Reply
0 Kudos
6 Replies
Vijay2027
Expert
Expert
Jump to solution

You will need to copy from 6.0.0 and re-create symlinks.

ssh into ESXi host and share the output please:

ls -lrth

Reply
0 Kudos
lytledd
Contributor
Contributor
Jump to solution

ls -lrth

total 565

lrwxrwxrwx    1 root     root          17 Jul 21 01:45 vmupgrade -> /locker/vmupgrade

lrwxrwxrwx    1 root     root           4 Jul 21 01:45 sbin -> /bin

-r--r--r--    1 root     root      324.3K Jul 21 02:02 bootpart.gz

-r-x------    1 root     root       22.7K Aug 12 14:34 local.tgz

drwxr-xr-x    1 root     root         512 Aug 12 14:38 vmimages

drwxr-xr-x    1 root     root         512 Aug 12 14:38 vmfs

drwxr-xr-x    1 root     root         512 Aug 12 14:38 var

drwxr-xr-x    1 root     root         512 Aug 12 14:38 usr

drwxr-xr-x    1 root     root         512 Aug 12 14:38 tardisks.noauto

drwxr-xr-x    1 root     root         512 Aug 12 14:38 tardisks

drwxr-xr-x    1 root     root         512 Aug 12 14:38 opt

drwxr-xr-x    1 root     root         512 Aug 12 14:38 mbr

drwxr-xr-x    1 root     root         512 Aug 12 14:38 lib64

drwxr-xr-x    1 root     root         512 Aug 12 14:38 lib

drwxr-xr-x    1 root     root         512 Aug 12 14:38 bin

lrwxrwxrwx    1 root     root          49 Aug 12 14:39 store -> /vmfs/volumes/57a61609-d28c2bae-37c5-089e01ba0599

lrwxrwxrwx    1 root     root          49 Aug 12 14:39 bootbank -> /vmfs/volumes/001fa2ed-4bc179d3-73a8-9af486f888d6

lrwxrwxrwx    1 root     root          49 Aug 12 14:39 altbootbank -> /vmfs/volumes/50daa6ee-a2c94ddd-5cc0-1d06b9f33fcc

lrwxrwxrwx    1 root     root          12 Aug 12 14:39 scratch -> /tmp/scratch

lrwxrwxrwx    1 root     root          22 Aug 12 14:39 productLocker -> /locker/packages/6.0.0

lrwxrwxrwx    1 root     root           6 Aug 12 14:39 locker -> /store

drwxr-xr-x    1 root     root         512 Aug 12 15:39 etc

drwxrwxrwt    1 root     root         512 Aug 12 16:01 tmp

drwxr-xr-x    1 root     root      128.0K Aug 12 16:13 proc

drwxr-xr-x   15 root     root         512 Aug 12 16:13 dev

Thanks, Doug
Reply
0 Kudos
Vijay2027
Expert
Expert
Jump to solution

can you cd in to /locker/packages/6.0.0/vmtools

Reply
0 Kudos
lytledd
Contributor
Contributor
Jump to solution

No,

Since /locker/packages has sub-directories of:

drwxr-xr-x1 root root         8 Nov 19  2016 6.5.0
drwxr-xr-x1 root root         8 Nov 19  2016 var
Thanks, Doug
Reply
0 Kudos
Vijay2027
Expert
Expert
Jump to solution

I don't expect to see 6.5.0 dir on ESXi 6.0

Anyways create a 6.0.0 dir and copy the content from a diff ESXi 6.0 host.

Reply
0 Kudos
lytledd
Contributor
Contributor
Jump to solution

Instead of a copy I just did a mv 6.5.0/ 6.0.0 and rebooted the host.  Things are fine again. 

Thank you for your help!

Thanks, Doug