Sergey,
If this is a real I2C issue, you may still see the same behavior on 2.0.x release if the I2C bus was not cleared before the upgrade. (in this moment I don't know if you recently performed an upgrade on the system or not)
I2C bus tranports information about the different components of the Unified System, this, meaning Chassis, IOMs, Fans, PSU, etc... What happens is that all those components try to send theit status update while other do the same and then the I2C bus gets overwhelmed, and then noone can really report their real status, so we usually recommend the customer ro reseat all major components, one at the time, to clear the bus and then do the upgrade, if that is not done before the upgrade, it still should be done after.
Try reseating the Fans and PSU, one at the time, leaving a minute in between and then, IOMs one at the time, leaving three minutes in between and begining with the subordinate to cause minimun disruption.
If this does not clear the situation, then you will need to remove one of the components already mentioned, one at the time and do a "show tech-support chassis # all brief" to see what the I2C bus reports segment by segment (chassis, Fans, PSUs...) once you remove a component and the errors on each segment stop incrementing you will have your faulty piece of hardware, and a TAC case will be needed to send a replacement.
For further analysis or assistance, I strongly recommend a TAC case to be opened.
-Kenny
