回復主題

信息

<blockquote data-quote="Lilyandy" data-source="post: 25" data-attributes="member: 1">Synology NAS 進階教學：如何將 S.M.A.R.T. 視覺化？學習佈署 Scrutiny。由於DSM 7起，移除了 S.M.A.R.T. 詳細資訊，因此若需要查看 S.M.A.R.T. 有幾種方式：①SSH指令查看。②指令碼匯出檔案查看。③佈署Scrutiny視覺化介面。這裏以『佈署Scrutiny視覺化介面』為例，不過，使用前，必需是 Plus 等級以上機型，因為需要使用 Docker（Container Manager）佈署，因此若非 Plus 以上機型，請放棄此法！非 Plus 以上之機型，只能使用①②法囉~首先請先安裝 Container Manager，接下來，請在 docker&nbsp; 目錄，建立以下目錄結構：docker┼Scrutiny┐&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; ├config──┬collector.yaml&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; │&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; └scrutiny.yaml&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; ├influxdb&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; ├run&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; └docker-compose.yml檔名不能修改，如圖所示：[ATTACH=full]152[/ATTACH][ATTACH=full]153[/ATTACH]接下來編輯『docker-compose.yml』佈署安裝檔，=====================================================[CODE]version: &#039;3.5&#039;services:&nbsp; scrutiny:&nbsp; &nbsp; restart: unless-stopped&nbsp; &nbsp; container_name: scrutiny&nbsp; &nbsp; image: ghcr.io/analogj/scrutiny:master-omnibus&nbsp; &nbsp; deploy:&nbsp; &nbsp; &nbsp; resources:&nbsp; &nbsp; &nbsp; &nbsp; limits:&nbsp;#&nbsp; &nbsp; &nbsp; &nbsp;&nbsp; memory: 256M # 限制最多使用 256MB 記憶體（非必備）&nbsp; &nbsp; cap_add:&nbsp; &nbsp; &nbsp; - SYS_RAWIO&nbsp; &nbsp; &nbsp; - SYS_ADMIN&nbsp; &nbsp; ports:&nbsp; &nbsp; &nbsp; - &quot;8080:8080&quot; # webapp【前面是本機Port，可自訂；後面是容器Port，不可改。】&nbsp; &nbsp; &nbsp; - &quot;8086:8086&quot; # influxDB admin&nbsp; &nbsp; volumes:&nbsp; &nbsp; &nbsp; - /run/udev:/run/udev:ro&nbsp; &nbsp; &nbsp; - /volume1/docker/Scrutiny/config:/opt/scrutiny/config&nbsp; &nbsp; &nbsp; - /volume1/docker/Scrutiny/influxdb:/opt/scrutiny/influxdb&nbsp; &nbsp; devices:&nbsp; &nbsp; &nbsp; - /dev/sda:/dev/sda&nbsp; &nbsp; &nbsp; - /dev/sdb:/dev/sdb#&nbsp; &nbsp; &nbsp; - /dev/sdc:/dev/sdc#&nbsp; &nbsp; &nbsp; - /dev/sdd:/dev/sdd&nbsp; &nbsp; &nbsp; - /dev/sdi:/dev/sdi&nbsp; &nbsp; &nbsp; - /dev/sdj:/dev/sdj#&nbsp; &nbsp; &nbsp; - /dev/nvme0n1:/dev/nvme0n1#&nbsp; &nbsp; &nbsp; - /dev/nvme1n1:/dev/nvme1n1#&nbsp; &nbsp; &nbsp; - /dev/usb1:/dev/usb1#&nbsp; &nbsp; &nbsp; - /dev/usb2:/dev/usb2&nbsp; &nbsp; environment:&nbsp; &nbsp; &nbsp; # - SCRUTINY_WEB_INFLUXDB_TOKEN= #任意長字串（非必要）&nbsp; &nbsp; &nbsp; # - SCRUTINY_WEB_INFLUXDB_INIT_USERNAME= 用戶名（非必要）&nbsp; &nbsp; &nbsp; # - SCRUTINY_WEB_INFLUXDB_INIT_PASSWORD=密碼 #至少8字元的密碼（非必要）&nbsp; &nbsp; &nbsp; - TIMEZONE=Asia/Taipei&nbsp; &nbsp; security_opt:&nbsp; &nbsp; &nbsp; - no-new-privileges:true[/CODE]=====================================================【修改後，放在容器目錄下！如前截圖。】<a href="https://xf.lilyandy.com/attachments/170/?hash=82ea82ae272e33143dd6cc818da194f3" target="_blank">按我下載docker-compose.yml範例檔</a>請注意，不能照搬唷！這是筆者使用的設定檔！並不代表你也可以使用，因此需要先SSH查詢正確的裝置位置！SSH查詢指令：smartctl --scan若你不熟悉SSH指令，可將它直接加入『任務排程表』，新增→排程任務→使用者定義指令碼，如圖所示：【請注意，必需是管理員帳號！】[ATTACH=full]155[/ATTACH][ATTACH=full]156[/ATTACH][ATTACH=full]157[/ATTACH]建立完成後，先執行它，接下來收信！只要電郵是有效的，會得到以下類似的結果，[ATTACH=full]159[/ATTACH]這就是您目前的裝置，請記下！並且修改 docker-compose.yml 檔，需修改成目前已搜尋到的裝置，不存在的請勿輸入或『#』註解掉，否則會佈署失敗！請留意！以後若有增減裝置，則必需重新佈署唷！以下，看圖說說故事，依序佈署之~~[ATTACH=full]160[/ATTACH][ATTACH=full]161[/ATTACH][ATTACH=full]162[/ATTACH][ATTACH=full]163[/ATTACH][ATTACH=full]164[/ATTACH][ATTACH=full]165[/ATTACH][ATTACH=full]166[/ATTACH]佈署成功後，在網址列輸入：NAS IP<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite7" alt=":p" title="Stick out tongue&nbsp; &nbsp; :p" loading="lazy" data-shortname=":p" />ort範例：192.168.1.115:9090即出現以下畫面，代表成功了！[ATTACH=full]167[/ATTACH]若出現以下畫面，代表截取資料失敗！[ATTACH=full]168[/ATTACH]此時需要額外設定『collector.yaml』=====================================================[CODE]# 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 momentversion: 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:&nbsp; id: &quot;&quot;# This block allows you to override/customize the settings for devices detected by# Scrutiny via `smartctl --scan`# See the &quot;--device=TYPE&quot; section of https://linux.die.net/man/8/smartctl# type can be a &#039;string&#039; or a &#039;list&#039;devices:&nbsp; - device: /dev/sda&nbsp; &nbsp; type: &#039;sat&#039;&nbsp; - device: /dev/sdb&nbsp; &nbsp; type: &#039;sat&#039;#&nbsp; - device: /dev/sdc#&nbsp; &nbsp; type: &#039;sat&#039;#&nbsp; - device: /dev/sdd#&nbsp; &nbsp; type: &#039;sat&#039;&nbsp; - device: /dev/sde&nbsp; &nbsp; type: &#039;sat&#039;&nbsp; - device: /dev/sdf&nbsp; &nbsp; type: &#039;sat&#039;#&nbsp; - device: /dev/nvme0n1#&nbsp; &nbsp; type: &#039;nvme&#039;#&nbsp; - device: /dev/nvme1n1#&nbsp; &nbsp; type: &#039;nvme&#039;#&nbsp; - device: /dev/usb1#&nbsp; &nbsp; type: &#039;sat&#039;#&nbsp; - device: /dev/usb2#&nbsp; &nbsp; type: &#039;sat&#039;#&nbsp; # example for forcing device type detection for a single disk#&nbsp; - device: /dev/sda#&nbsp; &nbsp; type: &#039;sat&#039;##&nbsp; # example for using `-d sat,auto`, notice the square brackets (workaround for #418)#&nbsp; - device: /dev/sda#&nbsp; &nbsp; type: [&#039;sat,auto&#039;]##&nbsp; # example to show how to ignore a specific disk/device.#&nbsp; - device: /dev/sda#&nbsp; &nbsp; ignore: true##&nbsp; # examples showing how to force smartctl to detect disks inside a raid array/virtual disk#&nbsp; - device: /dev/bus/0#&nbsp; &nbsp; type:#&nbsp; &nbsp; &nbsp; - megaraid,14#&nbsp; &nbsp; &nbsp; - megaraid,15#&nbsp; &nbsp; &nbsp; - megaraid,18#&nbsp; &nbsp; &nbsp; - megaraid,19#&nbsp; &nbsp; &nbsp; - megaraid,20#&nbsp; &nbsp; &nbsp; - megaraid,21##&nbsp; - device: /dev/twa0#&nbsp; &nbsp; type:#&nbsp; &nbsp; &nbsp; - 3ware,0#&nbsp; &nbsp; &nbsp; - 3ware,1#&nbsp; &nbsp; &nbsp; - 3ware,2#&nbsp; &nbsp; &nbsp; - 3ware,3#&nbsp; &nbsp; &nbsp; - 3ware,4#&nbsp; &nbsp; &nbsp; - 3ware,5##&nbsp; # example to show how to override the smartctl command args (per device), see below for how to override these globally.#&nbsp; - device: /dev/sda#&nbsp; &nbsp; commands:#&nbsp; &nbsp; &nbsp; metrics_info_args: &#039;--info --json -T permissive&#039; # used to determine device unique ID &amp; register device with Scrutiny#&nbsp; &nbsp; &nbsp; metrics_smart_args: &#039;--xall --json -T permissive&#039; # used to retrieve smart data for each device.#log:#&nbsp; file: &#039;&#039; #absolute or relative paths allowed, eg. web.log#&nbsp; level: INFO##api:#&nbsp; endpoint: &#039;http://localhost:8080&#039;#&nbsp; endpoint: &#039;http://localhost:8080/custombasepath&#039;# if you need to use a custom base path (for a reverse proxy), you can add a suffix to the endpoint.#&nbsp; See docs/TROUBLESHOOTING_REVERSE_PROXY.md for more info,# example to show how to override the smartctl command args globally#commands:#&nbsp; &nbsp; metrics_info_args: &#039;--info --json -d ata&#039;#&nbsp; &nbsp; metrics_smart_args: &#039;--xall --json -d ata&#039;#&nbsp; metrics_smartctl_bin: &#039;smartctl&#039; # change to provide custom `smartctl` binary path, eg. `/usr/sbin/smartctl`#&nbsp; metrics_scan_args: &#039;--scan --json&#039; # used to detect devices#&nbsp; metrics_info_args: &#039;--info --json&#039; # used to determine device unique ID &amp; register device with Scrutiny#&nbsp; metrics_smart_args: &#039;--xall --json&#039; # used to retrieve smart data for each device.#&nbsp; metrics_smartctl_wait: 0 # time to wait in seconds between each disk&#039;s check######################################################################################################################### FEATURES COMING SOON## The following commented out sections are a preview of additional configuration options that will be available soon.##########################################################################################################################collect:#&nbsp; long:#&nbsp; &nbsp; enable: false#&nbsp; &nbsp; command: &#039;&#039;#&nbsp; short:#&nbsp; &nbsp; enable: false#&nbsp; &nbsp; command: &#039;&#039;[/CODE]=====================================================<a href="https://xf.lilyandy.com/attachments/169/?hash=b41cb5b24f8018c37174a85e5f027a14" target="_blank">按我下載collector.yaml範例檔</a>請找到 devices: ，並修改正確的裝置，例如：&nbsp; - device: /dev/sda&nbsp; &nbsp; type: &#039;sat&#039;這兩行為一組裝置參數，依此類推，需與『docker-compose.yml』安裝佈署檔上的裝置一致，設定完畢後，別急著啟動，請先至 config 目錄下，找到 scrutiny.db 刪除，並重新佈署，即可正常刷新。以上，只要修改設定檔，就必需刪除該容器，再重新佈署唷！</blockquote>

[QUOTE="Lilyandy, post: 25, member: 1"] Synology NAS 進階教學：如何將 S.M.A.R.T. 視覺化？學習佈署 Scrutiny。由於DSM 7起，移除了 S.M.A.R.T. 詳細資訊，因此若需要查看 S.M.A.R.T. 有幾種方式： ①SSH指令查看。 ②指令碼匯出檔案查看。 ③佈署Scrutiny視覺化介面。這裏以『佈署Scrutiny視覺化介面』為例，不過，使用前，必需是 Plus 等級以上機型，因為需要使用 Docker（Container Manager）佈署，因此若非 Plus 以上機型，請放棄此法！非 Plus 以上之機型，只能使用①②法囉~ 首先請先安裝 Container Manager，接下來，請在 docker 目錄，建立以下目錄結構： docker┼Scrutiny┐ ├config──┬collector.yaml │ └scrutiny.yaml ├influxdb ├run └docker-compose.yml 檔名不能修改，如圖所示： [ATTACH type="full" alt="2026-02-19_124358.png"]152[/ATTACH] [ATTACH type="full" alt="2026-02-19_124420.png"]153[/ATTACH]接下來編輯『docker-compose.yml』佈署安裝檔， ===================================================== [CODE]version: '3.5' services: scrutiny: restart: unless-stopped container_name: scrutiny image: ghcr.io/analogj/scrutiny:master-omnibus deploy: resources: limits: # memory: 256M # 限制最多使用 256MB 記憶體（非必備） cap_add: - SYS_RAWIO - SYS_ADMIN ports: - "8080:8080" # webapp【前面是本機Port，可自訂；後面是容器Port，不可改。】 - "8086:8086" # influxDB admin volumes: - /run/udev:/run/udev:ro - /volume1/docker/Scrutiny/config:/opt/scrutiny/config - /volume1/docker/Scrutiny/influxdb:/opt/scrutiny/influxdb devices: - /dev/sda:/dev/sda - /dev/sdb:/dev/sdb # - /dev/sdc:/dev/sdc # - /dev/sdd:/dev/sdd - /dev/sdi:/dev/sdi - /dev/sdj:/dev/sdj # - /dev/nvme0n1:/dev/nvme0n1 # - /dev/nvme1n1:/dev/nvme1n1 # - /dev/usb1:/dev/usb1 # - /dev/usb2:/dev/usb2 environment: # - SCRUTINY_WEB_INFLUXDB_TOKEN= #任意長字串（非必要） # - SCRUTINY_WEB_INFLUXDB_INIT_USERNAME= 用戶名（非必要） # - SCRUTINY_WEB_INFLUXDB_INIT_PASSWORD=密碼 #至少8字元的密碼（非必要） - TIMEZONE=Asia/Taipei security_opt: - no-new-privileges:true[/CODE] ===================================================== 【修改後，放在容器目錄下！如前截圖。】 [URL='https://xf.lilyandy.com/attachments/170/?hash=82ea82ae272e33143dd6cc818da194f3']按我下載docker-compose.yml範例檔[/URL] 請注意，不能照搬唷！這是筆者使用的設定檔！並不代表你也可以使用，因此需要先SSH查詢正確的裝置位置！ SSH查詢指令： smartctl --scan 若你不熟悉SSH指令，可將它直接加入『任務排程表』，新增→排程任務→使用者定義指令碼，如圖所示：【請注意，必需是管理員帳號！】 [ATTACH type="full" alt="2026-02-19_134348.png"]155[/ATTACH] [ATTACH type="full" alt="2026-02-19_134629.png"]156[/ATTACH] [ATTACH type="full" alt="2026-02-19_134802.png"]157[/ATTACH] 建立完成後，先執行它，接下來收信！只要電郵是有效的，會得到以下類似的結果， [ATTACH type="full" alt="2026-02-19_135254.png"]159[/ATTACH] 這就是您目前的裝置，請記下！並且修改 docker-compose.yml 檔，需修改成目前已搜尋到的裝置，不存在的請勿輸入或『#』註解掉，否則會佈署失敗！請留意！以後若有增減裝置，則必需重新佈署唷！以下，看圖說說故事，依序佈署之~~ [ATTACH type="full" alt="2026-02-19_124511.png"]160[/ATTACH] [ATTACH type="full" alt="2026-02-19_124609.png"]161[/ATTACH] [ATTACH type="full" alt="2026-02-19_124649.png"]162[/ATTACH] [ATTACH type="full" alt="2026-02-19_125029.png"]163[/ATTACH] [ATTACH type="full" alt="2026-02-19_125044.png"]164[/ATTACH] [ATTACH type="full" alt="2026-02-19_125455.png"]165[/ATTACH] [ATTACH type="full" alt="2026-02-19_125522.png"]166[/ATTACH] 佈署成功後，在網址列輸入： NAS IP:port 範例： 192.168.1.115:9090 即出現以下畫面，代表成功了！ [ATTACH type="full" alt="2026-02-19_131501.png"]167[/ATTACH] 若出現以下畫面，代表截取資料失敗！ [ATTACH type="full" alt="2026-02-14_133207.png"]168[/ATTACH] 此時需要額外設定『collector.yaml』 ===================================================== [CODE]# 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: '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/nvme0n1 # type: 'nvme' # - device: /dev/nvme1n1 # type: 'nvme' # - device: /dev/usb1 # type: 'sat' # - device: /dev/usb2 # type: 'sat' # # example for forcing device type detection for a single disk # - device: /dev/sda # type: 'sat' # # # example for using `-d sat,auto`, notice the square brackets (workaround for #418) # - device: /dev/sda # type: ['sat,auto'] # # # example to show how to ignore a specific disk/device. # - device: /dev/sda # ignore: true # # # examples showing how to force smartctl to detect disks inside a raid array/virtual disk # - device: /dev/bus/0 # type: # - megaraid,14 # - megaraid,15 # - megaraid,18 # - megaraid,19 # - megaraid,20 # - megaraid,21 # # - device: /dev/twa0 # type: # - 3ware,0 # - 3ware,1 # - 3ware,2 # - 3ware,3 # - 3ware,4 # - 3ware,5 # # # example to show how to override the smartctl command args (per device), see below for how to override these globally. # - device: /dev/sda # commands: # metrics_info_args: '--info --json -T permissive' # used to determine device unique ID & register device with Scrutiny # metrics_smart_args: '--xall --json -T permissive' # used to retrieve smart data for each device. #log: # file: '' #absolute or relative paths allowed, eg. web.log # level: INFO # #api: # endpoint: 'http://localhost:8080' # endpoint: 'http://localhost:8080/custombasepath' # if you need to use a custom base path (for a reverse proxy), you can add a suffix to the endpoint. # See docs/TROUBLESHOOTING_REVERSE_PROXY.md for more info, # example to show how to override the smartctl command args globally #commands: # metrics_info_args: '--info --json -d ata' # metrics_smart_args: '--xall --json -d ata' # metrics_smartctl_bin: 'smartctl' # change to provide custom `smartctl` binary path, eg. `/usr/sbin/smartctl` # 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 --json' # used to retrieve smart data for each device. # metrics_smartctl_wait: 0 # time to wait in seconds between each disk's check ######################################################################################################################## # FEATURES COMING SOON # # The following commented out sections are a preview of additional configuration options that will be available soon. # ######################################################################################################################## #collect: # long: # enable: false # command: '' # short: # enable: false # command: ''[/CODE] ===================================================== [URL='https://xf.lilyandy.com/attachments/169/?hash=b41cb5b24f8018c37174a85e5f027a14']按我下載collector.yaml範例檔[/URL] 請找到 [COLOR=rgb(226, 80, 65)]devices:[/COLOR] ，並修改正確的裝置，例如： [COLOR=rgb(226, 80, 65)] - device: /dev/sda type: 'sat'[/COLOR] 這兩行為一組裝置參數，依此類推，需與『docker-compose.yml』安裝佈署檔上的裝置一致，設定完畢後，別急著啟動，請先至 [COLOR=rgb(44, 130, 201)]config[/COLOR] 目錄下，找到 [COLOR=rgb(41, 105, 176)]scrutiny.db[/COLOR] 刪除，並重新佈署，即可正常刷新。以上，只要修改設定檔，就必需刪除該容器，再重新佈署唷！ [/QUOTE]

驗證

設定  通知

選項