ScsiCore: 1181: Sync CR

Summary:

One VM out of several thousands became inaccessible via network and vCenter console access (sample pictured below).  Other symptoms included:

vCenterConsole issue

Resolution:

“Trespass” or “Failover” the LUN w/ the questionable VM to another storage processor (SP).  This immediately stopped all errors and all unaffected VM’s on that LUN continued to run while releasing whatever lock was placed on the LUN causing these ‘wonky’ issues.

Other related reading from VMWare:

Comments

Popular posts from this blog

NSX-T: Release associated invalid node ID from certificate

VMware | AVS: Content Library or Non vCenter objects on VSAN produces unassociated but valid objects

iOS: Sleep Focus activating on wrong time zone