Closed paulmorabito closed 8 months ago
mcarbonne
commented
9 months ago Maybe you can run smartctl from inside the scrutiny docker to obtain detailed logs :
sudo docker exec -it scrutiny /bin/sh(replace scrutiny by the name of you running container) and then execute smartctl --xall /dev/sda.
paulmorabito
commented
9 months ago Here you go:
root@7e29e6c5589c:/opt/scrutiny# smartctl --xall /dev/sda
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.10.60-qnap] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Vendor: WDC
Product: WD100EMAZ-00WJTA
Revision: 83.H
Compliance: SPC-3
User Capacity: 10,000,831,348,736 bytes [10.0 TB]
Logical block size: 512 bytes
Physical block size: 4096 bytes
LU is fully provisioned
Rotation Rate: 5400 rpm
Form Factor: 3.5 inches
Logical Unit id: 0x5000cca273e1ef5b
Serial number: 2YJDN6SD
Device type: disk
Local Time is: Wed Jan 3 08:51:52 2024 UTC
SMART support is: Unavailable - device lacks SMART capability.
Read Cache is: Enabled
Writeback Cache is: Enabled
=== START OF READ SMART DATA SECTION ===
Current Drive Temperature: 0 C
Drive Trip Temperature: 0 C
Error Counter logging not supported
[GLTSD (Global Logging Target Save Disable) set. Enable Save with '-S on']
Device does not support Self Test logging
Device does not support Background scan results loggingThe issue is on smartmontools side.
I don't know the kind of HW used in your NAS but maybe it prevents auto detection from smartctl. Nevertheless you can try to manually find a working configuration.
From inside the scrutiny docker, you can run smartctl --xall --device=XXX /dev/sda (replace XXX by sat, scsi ...). There is a list of all available options in man pages (https://linux.die.net/man/8/smartctl).
If you succeed, then have a look at metrics_smart_args parameter. Default value is --xall --json but you can add extra required parameters for you drives (--xall --json --device sat for example).
paulmorabito
commented
9 months ago I found the missing parameter (--device=sat) and can run this successfully from the command line in the container. When I update the config though, it's not running the command with the addition of --device. I'm setting it according to below:
# Commented Scrutiny Configuration File
#
# The default location for this file is /scrutiny/config/collector.yaml.
# In some cases to improve clarity default values are specified,
# uncommented. Other example values are commented out.
#
# When this file is parsed by Scrutiny, all configuration file keys are
# lowercased automatically. As such, Configuration keys are case-insensitive,
# and should be lowercase in this file to be consistent with usage.
######################################################################
# Version
#
# version specifies the version of this configuration file schema, not
# the scrutiny binary. There is only 1 version available at the moment
version: 1
# This block allows you to override/customize the settings for devices detected by
# Scrutiny via `smartctl --scan`
# See the "--device=TYPE" section of https://linux.die.net/man/8/smartctl
# type can be a 'string' or a 'list'
devices:
# example for forcing device type detection for a single disk
- device: /dev/sda
type: 'sat'
- device: /dev/sdb
type: 'sat'
- device: /dev/sdc
type: 'sat'
- device: /dev/sdd
type: 'sat'
commands:
# metrics_scan_args: '--scan --json' # used to detect devices
# metrics_info_args: '--info --json' # used to determine device unique ID & register device with Scrutiny
metrics_smart_args: '--xall --device=sat --json' # used to retrieve smart data for each device.Error from the logs below:
time="2024-01-04T14:06:58Z" level=info msg="Collecting smartctl results for sda\n" type=metrics
time="2024-01-04T14:06:58Z" level=info msg="Executing command: smartctl --xall --json /dev/sda" type=metrics
time="2024-01-04T14:06:58Z" level=error msg="smartctl returned an error code (4) while processing sda\n" type=metrics
time="2024-01-04T14:06:58Z" level=error msg="smartctl detected a checksum error" type=metrics
time="2024-01-04T14:06:58Z" level=info msg="Publishing smartctl results for 2yjdn6sd\n" type=metrics
time="2024-01-04T14:06:58Z" level=info msg="No notification endpoints configured. Skipping failure notification." type=webI'm running the latest container version etc. Is there anything I am missing?
chrisuhg
commented
9 months ago The issue is on
smartmontoolsside. I don't know the kind of HW used in your NAS but maybe it prevents auto detection fromsmartctl. Nevertheless you can try to manually find a working configuration. From inside the scrutiny docker, you can runsmartctl --xall --device=XXX /dev/sda(replace XXX bysat,scsi...). There is a list of all available options in man pages (https://linux.die.net/man/8/smartctl).If you succeed, then have a look at
metrics_smart_argsparameter. Default value is--xall --jsonbut you can add extra required parameters for you drives (--xall --json --device satfor example).
Many thanks for your comment :)
I got the same error in my all of SSD(SATA) on collector.log file: level=error msg="smartctl returned an error code (4) while processing sdf\n" type=metrics
and i went to docker exec -it scrutiny /bin/sh and ran smartctl --xall /dev/sde, it shown me:
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-4.4.302+] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Vendor: WDC
Product: WDS250G2B0B-00YS
Revision: 20WD
Compliance: SPC-3
User Capacity: 250,059,350,016 bytes [250 GB]
Logical block size: 512 bytes
LU is fully provisioned
Rotation Rate: Solid State Device
Logical Unit id: 0x5001b444a773882b
Serial number: 202********10
Device type: disk
Local Time is: Thu Jan 4 15:35:31 2024 UTC
SMART support is: Unavailable - device lacks SMART capability.
Read Cache is: Enabled
Writeback Cache is: Enabled
=== START OF READ SMART DATA SECTION ===
Current Drive Temperature: 0 C
Drive Trip Temperature: 0 C
Error Counter logging not supported
[GLTSD (Global Logging Target Save Disable) set. Enable Save with '-S on']
Device does not support Self Test logging
Device does not support Background scan results loggingI tired different args of the --device=TYPE:
smartctl --xall --device=ata /dev/sdj
smartctl --xall --device=scsi /dev/sdj
smartctl --xall --device=sat /dev/sdjuntil to smartctl --xall --device=sat /dev/sdj, it shown all of the SMART informations ! What is certain is that this type is appropriate !
so i split the compose.yaml to compose.yaml and collector.yaml:
compose.yaml
version: '3.5'
services:
scrutiny:
container_name: scrutiny
image: ghcr.io/analogj/scrutiny:master-omnibus
privileged: true # !!PLEASE REMOVE WHEN WORKING!!
cap_add:
- SYS_RAWIO
- SYS_ADMIN
ports:
- "8080:8080" # webapp
environment:
- PUID=1000
- PGID=1000
- DEBUG=true
- COLLECTOR_LOG_FILE=/opt/scrutiny/config/collector.log
- SCRUTINY_LOG_FILE=/opt/scrutiny/config/web.log
volumes:
- /run/udev:/run/udev:ro
- ./config:/opt/scrutiny/config
- ./influxdb:/opt/scrutiny/influxdb
devices: # if you will always run in "privileged" mode, you can remove this section
- /dev/sda
- /dev/nvme0collector.yaml | path to ./config/collector.yaml
# Commented Scrutiny Configuration File
#
# The default location for this file is /opt/scrutiny/config/collector.yaml.
# In some cases to improve clarity default values are specified,
# uncommented. Other example values are commented out.
#
# When this file is parsed by Scrutiny, all configuration file keys are
# lowercased automatically. As such, Configuration keys are case-insensitive,
# and should be lowercase in this file to be consistent with usage.
######################################################################
# Version
# version specifies the version of this configuration file schema, not
# the scrutiny binary. There is only 1 version available at the moment
version: 1
# The host id is a label used for identifying groups of disks running on the same host
# Primiarly used for hub/spoke deployments (can be left empty if using all-in-one image).
host:
id: ""
# This block allows you to override/customize the settings for devices detected by
# Scrutiny via `smartctl --scan`
# See the "--device=TYPE" section of https://linux.die.net/man/8/smartctl
# type can be a 'string' or a 'list'
devices:
- device: /dev/sda
type: 'ata'
- device: /dev/sdb
type: 'sat'
- device: /dev/sde
type: 'sat'
- device: /dev/sdf
type: 'ata'
- device: /dev/sdj
type: 'sat'
- device: /dev/nvme0
type: 'nvme'remove files or folder to clean the cache:
re-build your scrutiny object and open your config/collector.log file, you should be see the level=info msg="Executing command: smartctl --info --json --device sat /dev/sdf" type=metrics when you searching smartctl --info --json --device sat
now everything is normal 👯
I made a lot of efforts to search for the section on collection.yaml or metrics_smart_args in issue or document of offical, But I can't see (or missed) any guides of the Synology Container Manager environment, I hope what i shared is helpful :D
paulmorabito
commented
9 months ago @chrisuhg Thanks for the info. Although, I'm not sure why you need to rebuild the container when my config files are stored outside of it and the container reads the config upon every start/restart?
chrisuhg
commented
9 months ago @chrisuhg Thanks for the info. Although, I'm not sure why you need to rebuild the container when my config files are stored outside of it and the container reads the config upon every start/restart?
I knew the container will reads config when every start option, but the Container Manager of the Synology NAS app can not following after i edited the compose.yaml file.
so I though the Start/Stop of the GUI button is equal docker run/stop , the option > build button is equal docker-compose -config compose.yml
Maybe I should attach more screenshot to make it easier to understand the "build" or "re-build"~
Anyway, thanks for your ask :D
paulmorabito
commented
9 months ago Ah yes, you make a good point. I use Portainer for managing my containers instead of QNAP's Container Manager.
In any case, the issue remains for me as it seems the global command for smartctl is not being read by the config.
Paul Morabito On 4 Jan 2024 at 19:17 +0100, Chrishg @.***>, wrote:
@chrisuhg Thanks for the info. Although, I'm not sure why you need to rebuild the container when my config files are stored outside of it and the container reads the config upon every start/restart? I knew the container will reads config when every start option, but the Container Manager of the Synology NAS app can not following after i edited the compose.yaml file. so I though the Start/Stop of the GUI button is equal docker run/stop , the option > build button is equal docker-compose -config compose.yml image.png (view on web) Maybe I should attach more screenshot to make it easier to understand the "build" or "re-build"~ Anyway, thanks for your ask :D — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>
pheetr
commented
8 months ago I also have a QNAP and had the same issue as you, @paulmorabito. The advice from @chrisuhg helped me get it working.
I just created the collector.yaml file in the config folder (where scrutiny.db is located) and specified all the drive types individually, as 'sat' in my case, as that was what yielded results in the scrutiny's docker console, with command smartctl --xall --device=sat /dev/sda
Restarting the container afterwards was enough to get things going in my case.
Note: I've initially attempted to set the global command arguments in the config, since all my drives are SATA, but that didn't work for me.
collector.yaml:
# Commented Scrutiny Configuration File
#
# The default location for this file is /opt/scrutiny/config/collector.yaml.
# In some cases to improve clarity default values are specified,
# uncommented. Other example values are commented out.
#
# When this file is parsed by Scrutiny, all configuration file keys are
# lowercased automatically. As such, Configuration keys are case-insensitive,
# and should be lowercase in this file to be consistent with usage.
######################################################################
# Version
#
# version specifies the version of this configuration file schema, not
# the scrutiny binary. There is only 1 version available at the moment
version: 1
# The host id is a label used for identifying groups of disks running on the same host
# Primiarly used for hub/spoke deployments (can be left empty if using all-in-one image).
host:
id: ""
# This block allows you to override/customize the settings for devices detected by
# Scrutiny via `smartctl --scan`
# See the "--device=TYPE" section of https://linux.die.net/man/8/smartctl
# type can be a 'string' or a 'list'
devices:
# # example for forcing device type detection for a single disk
- 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'Thanks for the reply @pheetr. I've taken a look with fresh eyes and my config was pointing to the wrong location. I don't check Scrutiny very often and perhaps at some point it was changed to opt/scrutiny/config?
In any case, I had "type: sat" previously set so pointing to the correct config sorted that. I also noticed on restarting that I now have 4 "[/DEV/ -" devices that can't be clicked on or deleted. There was quite a few DB migrations on restart so its perhaps a side effect of it?
Also noted that the global "commands" doesn't seem to work but that's a separate issue to this. I'll close for now as the reported issue is fixed.
Using scrutiny on my QNAP TS453BE and the latest version of scrutiny and QNAP firmware is once again giving smartctl errors. Compose and logs are below:
logs:
Please let me know if there is any further debugging or logging needed and I'll get to it.
Thanks,