<

vCenter Troubleshooting TIPS: ESXi 6.0 Bug: Deprecated VMFS volume warning reported by ESXi hosts (adding iSCSI LUN)

Published on
5,025 Points
1,825 Views
2 Endorsements
Last Modified:
Luciano Patrão
VCP6.5-DCV, vSAN Specialist, vExpert last 3*, Veeam Vanguard. Expertises VMware, Virtual Backups and Storage design and a active Blogger.
When adding iSCSI LUNs to ESXi 6.0 we can encounter a bug
Today we need to add a new iSCSI logical unit number (LUN) to one of our vCenter 6.0 and found a bug in ESXi 6.0.

After creating the LUN in NetApp it is presented to the hosts. Adding the iSCSI to one of the hosts everything was okay, but when the rest of the hosts recognized the new Datastore we found some warnings in all hosts.

"Deprecated VMFS volume(s) found on the host. Please consider upgrading volume(s) to the latest version"

 
Screen-2BShot-2B03-02-16-2Bat-2B12.4.PNG
Troubleshooting the host log in /var/log/hostd.log  we found something similar to this:


warning hostd[]2EFC2B70] [Originator@6876 sub=Hostsvc.DatastoreSystem opID=7878B682-0000041D-2b-bb-41-25e0 user=vpxuser] VMFS volume []/vmfs/volumes/56d6cfc8-c7b45bfc-0cd5-984be167ca4c] of version []0] is not supported.
warning hostd[]2EFC2B70] [Originator@6876 sub=Hostsvc.DatastoreSystem opID=7878B682-0000041D-2b-bb-41-25e0 user=vpxuser] UpdateConfigIssues: Deprecated VMFS filesystems detected. These volumes should be upgraded to the latest version 
It seems that ESXi 6.0 has a bug when adding the iSCSI LUN to the host and while it is mounting (when unmounted) it gets this warning. Because the version of the filesystem is not known during the initial detection, it cannot be matched in the initial state (while mounting the LUN).

There is no solution from VMware for this issue; the knowledgebase article about this bug is here: VMware KB 2109735

Since there is no fix at the moment for the issue, the solution is to restart the management agents on the hosts that have this issue. This will clear the warming message.

To restart the management agents we can go through the Direct Console User Interface (DCUI) and just choose the Restart Management Agents option.

Note: This option can disconnect your ESXi host temporarily from vCenter.

Or we can just log in using SSH in the ESXi host(my prefer option) and restart from the console. Just use this:
 

/etc/init.d/hostd restart
/etc/init.d/vpxa restart

Open in new window

image.gifimage.gif Do this on all hosts affected (that have the warning message) and they will be cleared.

Hope this can help you fixing this bug.

This is the part of my "TIP Articles". So, please vote "Helpful" on this Article. And I encourage your comments and feedback.This is the part of my "TIP Articles". So, please vote "Helpful" on this Article. And I encourage your comments and feedback.
2
Comment
2 Comments

Expert Comment

by:McMillan LLP
Please note that it appears that Update 2 has fixed this issue and the workaround is no longer required.  I was able to add 3 datastores just now and did not get the warning.
0
LVL 25

Author Comment

by:Luciano Patrão
Thanks for the update.

Did not tested yet, but will.

Thanks again
0

Featured Post

Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

Join & Write a Comment

Advanced tutorial on how to run the esxtop command to capture a batch file in csv format in order to export the file and use it for performance analysis. He demonstrates how to download the file using a vSphere web client (or vSphere client) and exp…
Video by: ITPro.TV
In this episode Don builds upon the troubleshooting techniques by demonstrating how to properly monitor a vSphere deployment to detect problems before they occur. He begins the show using tools found within the vSphere suite as ends the show demonst…

Keep in touch with Experts Exchange

Tech news and trends delivered to your inbox every month