started writing a TROUBLESHOOTING guide for the device collector.

docs/TROUBLESHOOTING_DEVICE_COLLECTOR.md

@@ -57,6 +57,12 @@ Smartctl has support for a large number of [RAID controllers](https://www.smartm
 support is not automatic, and may require some additional device type hinting. You can provide this information to the Scrutiny collector
 using a collector config file. See [example.collector.yaml](/example.collector.yaml)
 
+> NOTE: If you use docker, you **must** pass though the RAID virtual disk to the container using `--device` (see below)
+>
+> This device may be in `/dev/*` or `/dev/bus/*`. 
+>
+> If you're unsure, run `smartctl --scan` on your host, and pass all listed devices to the container.
+
 ```yaml
 # /scrutiny/config/collector.yaml
 devices:
@@ -107,11 +113,3 @@ Thankfully the collector has a special `--host-id` flag (or `COLLECTOR_HOST_ID`
 
 See the [docs/INSTALL_HUB_SPOKE.md](/docs/INSTALL_HUB_SPOKE.md) guide for more information. 
 
-
-- All RAID controllers supported by `smartctl` are automatically supported by Scrutiny.
-    - While some RAID controllers support passing through the underlying SMART data to `smartctl` others do not.
-    - In some cases `--scan` does not correctly detect the device type, returning [incomplete SMART data](https://github.com/AnalogJ/scrutiny/issues/45).
-      Scrutiny will eventually support overriding detected device type via the config file.
-- If you use docker, you **must** pass though the RAID virtual disk to the container using `--device` (see below)
-    - This device may be in `/dev/*` or `/dev/bus/*`.
-    - If you're unsure, run `smartctl --scan` on your host, and pass all listed devices to the container.