docs(error-warning-details): update missing errors to have description

Author: hasezoey

docs/guides/error-warning-details.md

@@ -43,47 +43,116 @@ This Error gets thrown when this package runs on an unsupported architecture by
 
 ## UnknownPlatformError
 
-*extend documentation*
+Example: `Unknown Platform: "${platform}"`
+
+Details:  
+The Platform `${platform}` is not supported, only supported platform currently are:
+
+- `osx`
+- `win32` / `windows`
+- `linux`
 
 ## WaitForPrimaryTimeoutError
 
-*extend documentation*
+Example: `Timed out after ${timeout}ms while waiting for a Primary (where: "${where}")`
+
+Details:  
+Waiting for a Primary has timedout, this originates from 4 common issues:
+
+- Starting instances failed
+- A even number of instances started and are unable to elect a Primary
+- Internal Problem
+- Target System is too slow to start the number of instances
+
+Default Timeout: `1000 * 30` (30 seconds)
 
 ## EnsureInstanceError
 
-*extend documentation*
+Example:
+
+- `${baseMesasge} state was "running" but "instanceInfo" was undefined!`
+- `${baseMesasge} "instanceInfo" was undefined after running "start"`
+
+Details:
+
+- First Error Message gets thrown when `ensureInstance` is called and the `state` is `running`, but somehow `instanceInfo` is `undefined`
+- Second Error Message gets thrown when `ensureInstance` is called and after `start` was called by `ensureInstance` and `instanceInfo` is still `undefined`
+
+In any case this Error gets thrown, it means that some internal problem happened that was not handled with another Error, please report if your get this error and did not mock anything.
+
+Also see [`InstanceInfoError`](#instanceinfoerror).
 
 ## NoSystemBinaryFoundError
 
-*extend documentation*
+Example: `Config option "SYSTEM_BINARY" was provided with value "${binaryPath}", but no binary could be found!`
+
+Details:  
+Config Options [`SYSTEM_BINARY`](../api/config-options#system_binary) was set, but no binary could be found at the path `${binaryPath}`.
+Likely causes are:
+
+- No Binary Exists at the specified path
+- The Binary is does not have the necessary permissions and is so ignored (required permissions are `fs.constants.X_OK` (`--x`))
+
+Also see:
+
+- [`InsufficientPermissionsError`](#insufficientpermissionserror)
+- [`BinaryNotFoundError`](#binarynotfounderror)
 
 ## Md5CheckFailedError
 
-*extend documentation*
+Example: `MD5 check failed! Binary MD5 is "${binarymd5}", Checkfile MD5 is "${checkfilemd5}"`
+
+Details:  
+Download MD5 check was enabled ([`MD5_CHECK`](../api/config-options#md5_check)) but failed, listing the local file md5 as `${binarymd5}` and the downloaded md5 as `${checkfilemd5}`
 
 ## StartBinaryFailedError
 
-*extend documentation*
+Example: `Starting the Binary Failed (PID is undefined)! Binary: "${binary}"`
+
+Details:  
+Trying to start the binary `${binary}` as a childprocess somehow failed by having property `pid` being `undefined`.  
+
+Enable [Debug Mode](./enable-debug-mode) for more information.
 
 ## InstanceInfoError
 
-*extend documentation*
+Example: `"instanceInfo" was undefined when expected to be defined! (where: "${where}")`
+
+Details:  
+`instanceInfo` was `undefined` when it was expected to have been defined previously. Please Report if this error gets thrown.
+
+Enable [Debug Mode](./enable-debug-mode) for more information.
 
 ## KeyFileMissingError
 
-*extend documentation*
+Example: `"keyfileLocation" was undefined when expected!`
+
+Details:  
+Option `keyfileLocation` was `undefined` when it was needed. This Options is required when starting a `MongoInstance` and option `replSet` and `auth` are set.
 
 ## AuthNotObjectError
 
-*extend documentation*
+Example: `"auth" was not a object when it was expected!`
+
+Details:  
+Property `auth` was expect to be of type `object` (transform happens in the setter for `replSetOpts`). Please Report if this error gets thrown.
 
 ## InsufficientPermissionsError
 
-*extend documentation*
+Example: `File "${path}" does not have the required Permissions, required Permissions: "--x"`
+
+Details:  
+Binary Check was conducted and found that the specified file `${path}` exists, but does not have the required permissions, required permissions are `fs.constants.X_OK` (`--x`).
 
 ## BinaryNotFoundError
 
-*extend documentation*
+Example: `No Binary at path "${path}" was found! (ENOENT)`
+
+Details:  
+Binary Check was conducted and found that the specified file `${path}` did not exist (`ENOENT`), this may be a result of:
+
+- The Binary Download failed without throwing another Error
+- The Path generation had a problem
 
 ## AssertionFallbackError