We've seen a variety of errors during powercycle testing on Windows after upgrading to Windows Server 2016, none of which are indicative of a MongoDB issue:
- StartService fails with "The service did not respond to the start or control request in a timely fashion"
- StartService fails with "The device is not ready"
- StartService fails with "Access is denied"
- StartService fails with "Error performing inpage operation"
- The mongod-powertest service terminates unexpectedly due to not being able to access some file (unnamed by the Application event logs)
We should run the chkdsk command in read-only mode (i.e. without any extra parameters) to see if we can collect diagnostics indicating the NTFS volume is corrupt after using notmyfault.exe to crash the machine.