-
Type: New Feature
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Testing Infrastructure
-
Fully Compatible
-
v4.2
-
STM 2019-08-12
-
26
-
2
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.
- is related to
-
SERVER-42571 Collect Windows event logs on remote machine during powercycle
- Closed
- related to
-
SERVER-54898 Run the sync utility after initial powercycle setup on Windows
- Closed