logo
  • Home
  • About Me
  • EMC
  • Virtualization

This issue occurs because the version of the filesystem is not known during the initial detection. Therefore, comparing it against the list of valid filesystems does not return a match.

Resolution

This is a known issue affecting vCenter Server 6.0.

This issue is resolved in vCenter Server 6.0 Update 2, available at VMware Downloads.

To work around this issue, restart the management agents on the impacted hosts to clear the warning.

From the Local Console or SSH:

  1. Log in to SSH or Local console as root.
  2. Run these commands:

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

Share this:

  • Tweet

Related

« Stopping, starting, or restarting vCenter Server Appliance services
VPLEX GUI Not Showing Performance Counters »

Leave a comment Cancel reply

Your email address will not be published. Required fields are marked *

Subscribe to Blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Categories

Follow me on Twitter

My Tweets

Top Posts & Pages

  • Storage vMotion Stuck at 32% when migrating from One Vplex to Other
  • Changing the IP Address of the Cisco DCNM-SAN & DCNM-SMIS OVA/LINUX Installation

Social

  • View anujajju’s profile on Twitter

Pages

  • About Me

Archives

  • July 2019
  • April 2018
  • January 2018
  • September 2017
  • August 2017
  • August 2016
  • July 2016
  • June 2016
  • May 2016

Categories

  • EMC (3)
    • Unisphere (2)
    • VPLEX (1)
  • UCS (3)
  • Virtualization (19)

WordPress

  • Log in
  • WordPress
follow @anujajju
  • About Me