This is fixed in ESXi 6.7 update 3.
Workaround:
Users can workaround the issue by restarting the SIOC service using the following commands on the affected ESXi Hosts:
1. Check the status of storageRM and sdrsInjector
/etc/init.d/storageRM status
/etc/init.d/sdrsInjector status
2. Stop the service
/etc/init.d/storageRM stop
/etc/init.d/sdrsInjector stop
3. Start the service
/etc/init.d/storageRM start
/etc/init.d/sdrsInjector start
If the issue persists even after the SIOC service is restarted, users can temporarily disable SIOC by turning off the feature from VMware Virtual Center