gilles/scrutiny
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

started writing a TROUBLESHOOTING guide for the device collector.

Browse Source
This commit is contained in:
Jason Kulatunga
2022-04-30 15:59:45 -07:00
parent 5a1e390acd
commit 9ee2674804
1 changed files with 6 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/TROUBLESHOOTING_DEVICE_COLLECTOR.md
+6 -8
View File
@@ -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 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) 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 ```yaml
# /scrutiny/config/collector.yaml # /scrutiny/config/collector.yaml
devices: 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. 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.