• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar

Yellow Bricks

by Duncan Epping

  • Home
  • ESXTOP
  • Stickers/Shirts
  • Privacy Policy
  • About
  • Show Search
Hide Search

Disk format version 4.0 update to 2.0 suggested

Duncan Epping · Jun 15, 2016 ·

I’ve seen some people reporting a strange message in the Virtual SAN UI. The UI states the following: Disk format version 4.0 (update to 2.0 suggested). This is what that looks like (stole the pic from VMTN, thanks Phillip.)

disk format version 4.0 update to 2.0 suggested

A bit strange considering you apparently have 4.0 why would you go to 2.0 then? Well you are actually on 2.0 and are supposed to go to 3.0. The reason this happens is because, most likely, not all hosts within you cluster are on the same version of Virtual SAN, or vCenter Server was not updated to the last version and ESXi has a higher version. So far I have seen this being reported when people upgrade to vSphere 6.0 Update 2. If you are upgrading, make sure to upgrade all hosts to ESXi 6.0 Update 2, but before you do, upgrade the vCenter Server to 6.0 Update 2 first!

Related

Server, Software Defined, Storage, vSAN 6.0, 6.2, update 2, virtual san, VMware, vsan, vSphere

Reader Interactions

Comments

  1. mohammed said says

    13 July, 2016 at 21:13

    i did and unfortunately i am still facing the same issue

  2. Kevin says

    21 July, 2016 at 08:03

    Here was my situation – commissioned my environment with ESXi 6.0u2, but did not realize that I had downloaded vCenter 6.0. Installed, configured and cleared all alarms except for the weird upgrade disk format 4.0 to 2.0 error.

    Contacted support regarding this error. While waiting for a response, I realized my error and upgraded the vCenter server. My disk formats are all now 3.0, yet the warning alarm remains advising me that I have disks that need to be upgraded on every host. This warning does not have a reset to green option.

    I have disabled the alarm and re-enabled it, but that did not clear it. I have tried to re-define how the alarm is configured, but to no avail. I am continuing my support case with VMWare, but also open to suggestions. Will update when I get a resolution.

Primary Sidebar

About the author

Duncan Epping is a Chief Technologist in the Office of CTO of the Cloud Platform BU at VMware. He is a VCDX (# 007), the author of the "vSAN Deep Dive", the “vSphere Clustering Technical Deep Dive” series, and the host of the "Unexplored Territory" podcast.

Upcoming Events

May 24th – VMUG Poland
June 1st – VMUG Belgium

Recommended Reads

Sponsors

Want to support Yellow-Bricks? Buy an advert!

Advertisements

Copyright Yellow-Bricks.com © 2023 · Log in