What Was Scrutiny Doing on ZimaOS 1.5?
In November 2025, a user installed Scrutiny on ZimaOS 1.5 and initially saw the connected USB 3.0 hard drives in the dashboard. After additional drives were attached, Scrutiny did not add them. Even removing a previously detected drive did not refresh the displayed list.
The user restarted ZimaOS and reinstalled Scrutiny, but the original dashboard state still appeared. That led to two different questions: where Scrutiny's persistent state is stored, and how USB drives behind a bridge or controller should be presented to Scrutiny.
Why Can Reinstalling Scrutiny Keep the Old State?
A community reply explained that application data remains in the app-data area on the drive where the application is installed. This is consistent with the broader ZimaOS behavior seen with other applications: removing a container does not always mean all persistent application data has been deleted.
That distinction matters because Scrutiny stores more than a live browser view. A reinstall can reuse persisted configuration or database state if the mapped app-data directory remains.
Why Might a USB Drive Need an Explicit Device Type?
The original poster later concluded that the affected drive needed an explicit device type such as sat. USB-to-SATA bridges can hide or translate SMART commands differently from a directly attached SATA disk, so a monitoring tool may need additional device information before it can query SMART data correctly.
The thread did not contain an official IceWhale instruction showing exactly how to inject that Scrutiny device configuration through the ZimaOS 1.5 interface. For that reason, this page does not present the user's YAML fragment as an official ZimaOS procedure.
What Should You Verify Before Resetting Scrutiny?
- Confirm the drive is visible to ZimaOS itself before troubleshooting Scrutiny.
- Check whether the problem affects only USB-attached drives or also directly attached SATA/NVMe devices.
- Identify the USB-to-SATA bridge or enclosure because different bridges expose SMART data differently.
- Record the Scrutiny and ZimaOS versions before reinstalling or deleting persistent data.
- Do not delete Scrutiny's persistent app data unless you are prepared to lose its stored configuration and history.
Can ZimaOS Currently Expose Arbitrary YAML App Settings?
The 2025 user specifically noted that the ZimaOS app settings did not expose the device-type option they needed. ZimaOS continues to expand app configuration controls, but the current product roadmap lists native YAML configuration support as a Version 1.7x capability rather than something that should be assumed for every earlier release.
Until a configuration option is exposed by the installed app package or current ZimaOS interface, treat manual container or YAML changes as an advanced customization that can be affected by app updates.
You can review the current ZimaOS release timeline before relying on a workaround written for ZimaOS 1.5.
What If Scrutiny and ZimaOS Disagree About Drive Health?
Drive discovery and drive-health interpretation are separate problems. Later community discussions show that users can also see differences between ZimaOS health status and Scrutiny SMART results. If a drive is physically visible but Scrutiny reports a SMART failure, preserve the SMART evidence and treat the disk cautiously instead of assuming the dashboard status alone is definitive.
Frequently Asked Questions
Where does Scrutiny keep the dashboard state?
The community discussion points to persistent application data in the app-data area on the drive where the app is installed. Removing the app container alone may not remove that stored state.
Why does Scrutiny see one USB drive but not another?
USB storage bridges can expose SMART capabilities differently. The original poster believed an explicit SAT device type was needed for the affected drive.
Did IceWhale provide an official ZimaOS 1.5 YAML procedure in this thread?
No. The thread did not include an official step-by-step method for adding the Scrutiny device-type setting through ZimaOS 1.5.
Should I delete the Scrutiny app-data folder to force a reset?
Only if you intentionally want to remove the application's persistent state and have backed up anything you need. Deleting persistent app data is different from simply restarting the app.
