Setting up disk/container disk paths on Scrutiny

Apps and Virtualization
1

Hey guys,

I am looking to setup Scrutiny, I note that on the setup page, you need to manually setup all the disks you wish for the app to monitor and requires the Host Disk Path & Container Disk Path. See below.

image

How would I go about finding out my Host Disk Paths and associated Container Disk Path?

Many thanks,
P

2

The disks are called sda sdb etc

For sda, set container AND host disk path to /dev/sda

Repeat for all disks.

2 Likes
3

Thanks for this. I did have the command on how to list all the physical discs in my server, but seem to have misplaced it. Could you help me with that?

4

You can just go to the Storage page and click “Disks”

But smartctl —scan (two dashes) is what Scrutiny uses

1 Like
5

Thanks! Just reporting back that I got it setup, looks like however that it struggles to work with Nvme drives. HDD and SSD it all works fine, for Nvme it detects the drive but values such as Status and Temp are not populated. Either an issue with the App itself or possibly underlying TrueNas thing?

image
image1743Ă—701 40.5 KB

6

Did you try checking the Elevate Privileges checkbox?

Screenshot 2024-11-20 at 12.00.55 PM
Screenshot 2024-11-20 at 12.00.55 PM1230Ă—408 43.3 KB

1 Like
7

Thanks, good shout. I have just tried that, it does now reveal new details, but states all drives are failed.

image
image1392Ă—465 26.1 KB

I have gone ahead and logged a bud report on the projects github.

1 Like
8

If you click on the top right of each box can you try to open the View Details? I have disks that have fail but only for Scrutiny parameters. If I choose the average S.M.A.R.T parameters they pass.

image
image779Ă—194 16.7 KB

9

It cannot see my nvme boot pool nvme0n1 even after adding /dev/nvme0n1 with Elevate priviledges.
/dev/sda etc works.

10

@mantheman try only with /dev/nvme0, don’t add the “n1”. Does it work?

11

panzerscope

In the Field “Container Disk Path*” what did you enter? all my google Fo is keeps leading me back to your thread here or your bug report.

12

I have multiple NVMe drives. I needed to check “WARNING: Elevate Privileges” for the NVMe drives to fully populate data (such as temperature).

You want to set Host Disk Path and Container Disk Path the SAME, such as:
Host Disk Path: /dev/sda
Container Disk Path: /dev/sda
Add another
Host Disk Path: /dev/nvme0
Container Disk Path: /dev/nvme0
Keep going until done

If you use nvme0n1 less data will be retrieved. You can try this yourself by comparing output of “smartctl -a /dev/nvme0” compared to /dev/nvme0n1. Specifically, read of the Self-test Log will fail using nvme0n1.

1 Like
13

I have since learned you will need a cron job for the values to update periodically. Below is how I configured one:

System > Advanced Settings > Cron Jobs, Add
set Description to scrutiny
set Command to docker exec ix-scrutiny-scrutiny-1 /opt/scrutiny/bin/scrutiny-collector-metrics run
set Run As User to root
set Schedule to Hourly
check Hide Standard Error
Save

2 Likes
14

I’m trying to understand how to do it for mine, because my app instead of only scrutiny, is called scrunity-b550 (the chipset of that system). Maybe a reason to redo-it for it to work properly.

15

You can use the following to get the name:

# docker stats --no-stream
CONTAINER ID   NAME                       CPU %     MEM USAGE / LIMIT   MEM %     NET I/O          BLOCK I/O     PIDS
412f47c69c30   ix-syncthing-syncthing-1   0.13%     108.8MiB / 8GiB     1.33%     216kB / 1.03MB   19.8MB / 0B   21
04f4990fd5c9   ix-scrutiny-scrutiny-1     0.04%     149.8MiB / 4GiB     3.66%     564kB / 19.5MB   156MB / 0B    49
74a1e50e9496   ix-joplin-joplin-1         0.54%     287.1MiB / 4GiB     7.01%     475MB / 725MB    68.6MB / 0B   35
4bf32e9fa256   ix-joplin-postgres-1       0.01%     79.63MiB / 4GiB     1.94%     696MB / 458MB    254MB / 0B    8
2 Likes