Skip to content

Scrutiny SMART Monitoring in Container Manager on a Synology NAS

Important or Recent Updates
Historic UpdatesDate
Updated to use Container Manager and Projects29/05/2023
Added additional security option to the compose to restrict the container from gaining new privileges25/10/2023
Remove the need for setting up the synobridge network and allow the container to sit on its own isolated bridge14/07/2024
There may be an issue with the CRON kicking in on new installations meaning the UI doesn’t update – to remedy this I have added an override to the compose22/07/2024
Added note to database as minimum password length is 8 characters.
Added example cron schedules for running more that once per day
Added FAQ item relating to empty dashboards		08/11/2024
Historic Updates


What is Scrutiny?

Scrutiny is a Hard Drive Health Dashboard & Monitoring solution, merging manufacturer provided S.M.A.R.T metrics with real-world failure rates.

Let’s Begin

In this guide I will take you through the steps to get Scrutiny up and running in Docker.

Getting our drive details

We need to get some details about our drives in order for Scrutiny to read their SMART data.

It’s time to get logged into your Diskstation via SSH, in this guide I am using Windows Terminal however the steps will be similar on Mac and Linux,

Head into the DSM Control Panel > Terminal & SNMP and then enable SSH service.

Open up ‘‘Terminal’

Now type ‘ssh’ then your main admin account username @ your NAS IP Address and hit Enter

Bash
ssh drfrankenstein@192.168.0.101

You will then be asked to enter the password for the user you used you can either type this or right click in the window to paste (you won’t see it paste the info) then press enter.

Enter the login information for your main Synology user account, you will not be able to see the password as you type it. (If you are using a password manager right-clicking in the window will paste – you won’t be able to see it)

Now we are logged in we just need to do a single command to see our drives, note I am not prefacing this command with sudo as we don’t need the low level detail. You will see permission denied errors, but these can be ignored.

Bash
fdisk -l

The output you will see depends on the model NAS you own, the two examples below are from an 1821+ and an 1815+ which have 8 bays and the 1821+ has up to 2 NVMEs.

The 1815+ has 8 drives broken down from sda to sdh

The 1821+ has 8 drives broken down into SATA and NVME devices, sata1to sata8with the nvme0n1and nvme1n1. (Note if you have any eSATA devices connected these will also show)

Make note of the devices you see in your output as we will need them for the config file and compose.

USB Drives

If you also want to add USB drives this will depend on whether the Manufacturer of the caddy passes this info on. I have commented out the USB extra parts in the config a bit further on.

Config Files and Folders

Next lets create the folders the container will need. Head into File Station and create a subfolder in the ‘docker’ share called ‘scrutiny’ and then within that another called ‘influxdb’ it should look like the below.

Then if you don’t have one already from my other guides create another folder in the ‘docker’ share called ‘projects’ and within that another one called ‘scrutiny’

Next comes the config files, You can edit this file in a number of ways, but to keep the guide OS-agnostic we will be using the Synology Text Editor package which can be installed via Package Center.

Open up a new text document and paste one of the two code snippets below into it. Use the one that matches up with the way your drives are shown in the previous step (if you come across anything different let me know in the comments!)

Type 1

YAML
version: 1
host:
  id: ""
devices:
  - device: /dev/sata1
    type: 'sat'
  - device: /dev/sata2
    type: 'sat'
  - device: /dev/sata3
    type: 'sat'
  - device: /dev/sata4
    type: 'sat'
  - device: /dev/sata5
    type: 'sat'
  - device: /dev/sata6
    type: 'sat'
  - device: /dev/sata7
    type: 'sat'
  - device: /dev/sata8
    type: 'sat'
  - device: /dev/nvme0n1
    type: 'nvme'
  - device: /dev/nvme1n1
    type: 'nvme'
#  - device: /dev/usb1
#    type: 'sat'
#  - device: /dev/usb2
#    type: 'sat'

Type 2

YAML
version: 1
host:
  id: ""
devices:
  - device: /dev/sda
    type: 'sat'
  - device: /dev/sdb
    type: 'sat'
  - device: /dev/sdc
    type: 'sat'
  - device: /dev/sdd
    type: 'sat'
  - device: /dev/sde
    type: 'sat'
  - device: /dev/sdf
    type: 'sat'
  - device: /dev/sdg
    type: 'sat'
  - device: /dev/sdh
    type: 'sat'
  - device: /dev/nvme0n1
    type: 'nvme'
  - device: /dev/nvme1n1
    type: 'nvme'
#  - device: /dev/usb1
#    type: 'sat'
#  - device: /dev/usb2
#    type: 'sat'

You will need to edit the config file in line with the number of drives you had in the output earlier either adding or removing lines accordingly, including adding or removing the NVME drives.

Also, I have included a couple of commented out lines for USB drives if you have them connected.

Next you can save this file as ‘collector.yaml’ in the ‘/docker/scrutiny’ folder.

Notifications Config (optional)

This step is optional and depends on if you want to set up some notifications in case one of your drive has issues.

As of writing there are 14 different notification method, as you can imagine I cannot cover every single type in this guide, but this will get the config file in place for you to amend based on your preferences

Open up a new file Text Editor again, this time you need to copy and paste the full contents of the example config file located here

Scroll to the bottom of the file where you will see a number of config options for notifications. You will need to the remove the # from the ‘notify’ and ‘urls’ lines and then depending on which type of notification you decide to set up the # will need to be removed from the corresponding line.

The level of notification you receive (Critical or All Issues) can be set up in the WebUI once Scrutiny is up and running.

Removing the # from the required lines

Finally, save this file as ‘scrutiny.yaml’ into the /docker/scrutiny folder.

Docker Compose

We will be using Docker Compose in the Projects section of Container Manager to set up the container.

Open up Container Manager and click on Project then on the right-hand side click ‘Create’.

In the next screen we will set up our General Settings ‘Project Name’ will be ‘scrutiny’ the ‘Path’ click the button and select the folder we created earlier in ‘/docker/projects/scrutiny’. ‘Source:’ change the drop-down to ‘Create docker-compose.yml’.

Next we are going to drop in our docker compose configuration copy all the code in the box below and paste it into line ‘1’ just like the screenshot.

YAML
services:
  scrutiny:
    container_name: scrutiny
    image: ghcr.io/analogj/scrutiny:master-omnibus
    cap_add:
      - SYS_RAWIO
      - SYS_ADMIN
    ports:
      - 6090:8080/tcp # webapp
      - 8086:8086/tcp # influxDB admin
    volumes:
      - /run/udev:/run/udev:ro
      - /volume1/docker/scrutiny:/opt/scrutiny/config
      - /volume1/docker/scrutiny/influxdb:/opt/scrutiny/influxdb
    devices:
      - /dev/nvme0n1:/dev/nvme0n1
      - /dev/nvme1n1:/dev/nvme1n1
      - /dev/sata1:/dev/sata1
      - /dev/sata2:/dev/sata2
      - /dev/sata3:/dev/sata3
      - /dev/sata4:/dev/sata4
      - /dev/sata5:/dev/sata5
      - /dev/sata6:/dev/sata6
      - /dev/sata7:/dev/sata7
      - /dev/sata8:/dev/sata8
#      - /dev/usb1:/dev/usb1
#      - /dev/usb2:/dev/usb2
    environment:
      - SCRUTINY_WEB_INFLUXDB_TOKEN=ANYLONGSTRING
      - SCRUTINY_WEB_INFLUXDB_INIT_USERNAME=A-USERNAME
      - SCRUTINY_WEB_INFLUXDB_INIT_PASSWORD=A-PASSWORD
      - COLLECTOR_CRON_SCHEDULE=0 23 * * *
    security_opt:
      - no-new-privileges:true
    restart: unless-stopped


As you can see the devices section contains all our drives, you will need to amend this again in line with the config file you created earlier. You will need to amend the paths each side of the : so they match, adding or removing drives accordingly including the NVMEs.

e.g., /dev/sata1:/dev/sata1 or /dev/sda:/dev/sda and so on.

In addition to this you will see in the ‘environment’ section three variables that will need to be updated as outlined below, these secure the database used by scrutiny.

VariableValue
SCRUTINY_WEB_INFLUXDB_TOKENenter a sting of characters you can use almost anything treat it like a password so a nice long string
SCRUTINY_WEB_INFLUXDB_INIT_USERNAMEThis can be anything you like
SCRUTINY_WEB_INFLUXDB_INIT_PASSWORDa secure password (min of 8 characters)
COLLECTOR_CRON_SCHEDULE0 23 * * *

This overrides the default cron schedule at midnight and runs at 23:00

You can change the schedule to run more than once per day by using https://crontab.cronhub.io/ to get the right code to include. For example 0 * * * * is hourly.

These 3 values are only required for the first ever setup – you can remove them once Scrutiny is up and running but keep them safe in case you ever need them. Maybe in Vaultwarden!

Once you have made the edits press ‘Next’

You do not need to enable anything on the ‘Web portal settings’ screen click ‘Next’ again.

On the final screen click ‘Done’ which will begin the download of the container image and once downloaded they will be launched!

You will now see Scrutiny running and should have a green status on the left-hand side.

You should now be able to access the Scrutiny WebUI by going to your NAS IP followed by port 6090

e.g., 192.168.0.30:6090

Sometimes it can take a few minutes before all your drives appear, as Scrutiny needs to obtain their information so don’t panic if it’s initially empty. You can now adjust settings for the UI and Notifications in the WebUI.

FAQ (Frequently Asked Questions)

I added extra drives to my config, and they don’t appear in the UI even after waiting

You can overcome this by stopping the overall Project and then rebuilding it via Action > Build in the Container Manager UI

My dashboard is empty and shows no drives

If you have waited until after the initial scan and still no drives appear then you can try triggering a manual scan via SSH

Bash
sudo docker exec scrutiny /opt/scrutiny/bin/scrutiny-collector-metrics run

Looking for some help, join our Discord community

If you are struggling with any steps in the guides or looking to branch out into other containers join our Discord community!

Buy me a beverage!

If you have found my site useful please consider pinging me a tip as it helps cover the cost of running things or just lets me stay hydrated. Plus 10% goes to the devs of the apps I do guides for every year.

Published inDockerOther Tools 7.2Synology

97 Comments

  1. Sam Sam

    Hi Doc,
    Thanks for the helpful guide, I believe I followed it to the T and to be sure I deleted everything and tried again. On my scrutiny dashboard the “Last Updated” time does not update and neither do the temperatures and the temperature graph. It is not my browser as I tried edge, chrome and firefox. Restarting the container (right click on the container in DSM Container Manager and select Restart) does not help too. The only way to get the values to update is to stop the container and start it again. Am I missing some other setting?

    # 22 March 2024 Reply
  2. Nathan Nathan

    For anyone following this guide in the future. If you capitalize the S in the scrutiny folder like I did, you will have get an error message when building. “Failed to bind to mount point”
    Just rename the folder to all lowercase letters.

    # 14 March 2024 Reply
  3. Sergey Sergey

    Hello! Based on your instructions, I created a docker container Scrutiny.
    Not one one attribute is not read from disks connected to the motherboard. Everything is OK from the disks connected to the LSI controller. I found differences in the container logs. For drives on the motherboard device_protocol`=”SCSI”,device_type`=”scsi”, for drives on LSI device_protocol`=”ATA”,device_type`=”scsi”. It looks like the protocol is not defined correctly.
    https://bafista.ru/wp-content/uploads/2024/02/image.thumb_.png.137f3a00b451213c9c45a6c032733267-1707819165.2884.png

    # 13 February 2024 Reply
    • Dr_Frankenstein Dr_Frankenstein

      When you run the command what is DSM (xpenology) seeing for the drive info on the output? As your experience will likely be different depending on what if any information Scrutiny is going to be receiving via the drives connected via the LSI controller.

      # 13 February 2024 Reply
  4. xIExodusIx xIExodusIx

    Hi Dr. Frankenstein

    I have migrated all my Docker-Container to Container Manger on my SynoNAS (DS918+ DSM 7.2) by using your guides. Everythin went well so far. Every Container/Project is up and running. Also can I reach all ARR’s with my Browser. Only 4 Projects/Container makes problems. Scrutiny, spotweb and nzbhydra2 can not be reached over web, and minecraftjava crashes? after some time and the green point went to orange.
    Could you tell me what I’ve done wrong?

    # 19 January 2024 Reply
    • Dr_Frankenstein Dr_Frankenstein

      Hey, xIExodusIx

      I will need a bit more detail of the problematic containers. Can you reach out to me via my Help Me! page or via Discord and can certainly have a look at logs for you,

      # 19 January 2024 Reply
      • xIExodusIx xIExodusIx

        Hello Doc 🙂

        The Project scrutiny I got to run, it works now after I deleted all in the “influxdb” Folder and building the Project new.
        But spotweb won’t. I got some trouble with the Database Password, but this I could solve, but now, if I type my NASIP:9096 in my browser (Edge) I got an empty Webpage with the comment: “This page is not reachable”. Maybe I have to wait until tomorrow, and then try again and further. Under Docker all was fine.
        For NZBHydra2 I modified the NZBGet script, under DFokker it works, but now I can’t reach it with NASIP:5075.
        Minecraftjava I should start from scratch I think. I will try this first.
        Thanks for helping. I will write if I have mor trouble.
        xIExodusIx

        # 19 January 2024 Reply
        • xIExodusIx xIExodusIx

          Hi Doc,
          it’s me again, the nzbhydra2 project is up and running, but still not reachable by NASIP:5075. But I don’t really need this tool, it’s not important for me! The spotweb projekt is also up and running and also not reachable by NASIP:9096.
          I don’t have any clue anymore. What do you need from me for help solving this problem?
          Thanks for helping 🙂
          xIExodusIx

          # 20 January 2024 Reply
          • Dr_Frankenstein Dr_Frankenstein

            Hey spotted your other comments, ping me a message via my Help Me page so we keep the comments he related to the guide above.

            # 21 January 2024 Reply
  5. Wolfram Heinz Wolfram Heinz

    Hello Dr. Frankenstein,
    thank you for that tutorial. I followed step by step. Unfortunately, when opening up the Scrutiny-Dashboard, I don’t see any drives listed there – its just empty. fdisk -l command returned this:
    fdisk: cannot open /dev/ram0: Permission denied
    fdisk: cannot open /dev/ram1: Permission denied
    fdisk: cannot open /dev/ram2: Permission denied
    fdisk: cannot open /dev/ram3: Permission denied
    fdisk: cannot open /dev/ram4: Permission denied
    fdisk: cannot open /dev/ram5: Permission denied
    fdisk: cannot open /dev/ram6: Permission denied
    fdisk: cannot open /dev/ram7: Permission denied
    fdisk: cannot open /dev/ram8: Permission denied
    fdisk: cannot open /dev/ram9: Permission denied
    fdisk: cannot open /dev/ram10: Permission denied
    fdisk: cannot open /dev/ram11: Permission denied
    fdisk: cannot open /dev/ram12: Permission denied
    fdisk: cannot open /dev/ram13: Permission denied
    fdisk: cannot open /dev/ram14: Permission denied
    fdisk: cannot open /dev/ram15: Permission denied
    fdisk: cannot open /dev/sata2: Permission denied
    fdisk: cannot open /dev/sata1: Permission denied
    fdisk: cannot open /dev/md0: Permission denied
    fdisk: cannot open /dev/zram0: Permission denied
    fdisk: cannot open /dev/zram1: Permission denied
    fdisk: cannot open /dev/zram2: Permission denied
    fdisk: cannot open /dev/zram3: Permission denied
    fdisk: cannot open /dev/md1: Permission denied
    fdisk: cannot open /dev/synoboot: Permission denied
    fdisk: cannot open /dev/usb1: Permission denied
    fdisk: cannot open /dev/md2: Permission denied
    fdisk: cannot open /dev/mapper/vg1-syno_vg_reserved_area: Permission denied
    fdisk: cannot open /dev/mapper/vg1-volume_1: Permission denied

    and I used this for my collector.yaml file:
    version: 1
    host:
    id: “”
    devices:
    – device: /dev/sata1
    type: ‘sat’
    – device: /dev/sata2
    type: ‘sat’
    – device: /dev/md0
    type: ‘md’
    – device: /dev/md1
    type: ‘md’
    – device: /dev/md2
    type: ‘md’

    Any help is appreciated. Thank you in advance!

    # 7 January 2024 Reply
    • Dr_Frankenstein Dr_Frankenstein

      Hey remove the mdX lines they are the raid array you just need the sata ones

      # 7 January 2024 Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

drfrankenstein.co.uk – writing Synology Docker Guides since 2016 – Join My Discord!