Skip to content

[FEAT] Update bundled smartmontools for newer JMB39x/QNAP TR-004 SMART support #944

Open

Description

@peedub

Is your feature request related to a problem?

The collector/omnibus image bundles smartmontools 7.5 (2025-04-30 r5714), which cannot retrieve some diagnostic data from QNAP TR-004 enclosure disks. Newer upstream smartmontools main includes JMB39x self-test command support and reconstruction of the self-test-log index lost through protocol truncation.

Describe the solution you'd like

Please update smartmontools in the collector/omnibus images to a release or pinned upstream revision containing the newer JMB39x support.

Upstream context: smartmontools/smartmontools#64

Activity

  1. Starosdev commented on Oct 12, 2026

    @Starosdev
    Owner

    Thanks for the report and the upstream link.

    The JMB39x self-test support is merged on smartmontools main (commits daa557089a, a93ab7845f, 4d0d6ab4ed and 0a78084d74, June 2026), but no smartmontools release contains it yet. The latest release is still 7.5, and upstream main is now versioned 8.0 with no release date set. Debian packages 7.5 in every suite, including trixie-backports, which is what our images install.

    We will not ship a build of unreleased smartmontools main in the default images. The collector images install smartmontools from trixie-backports without a version pin, so they move to 8.0 on the first image rebuild after Debian packages it. We will keep this issue open until a released image reports 8.0 and the TR-004 self-test log shows up in Scrutiny.

    If you want to try the upstream changes before then, the collector can use a different smartctl binary through COLLECTOR_COMMANDS_METRICS_SMARTCTL_BIN (config key commands.metrics_smartctl_bin). You would build smartctl from smartmontools main on Debian trixie so its shared libraries match the image, mount it into the collector container read-only, and point that variable at the mounted path. We have not tested this with a TR-004, and it means running an unreleased smartctl, so treat it as experimental.

    If you do try it, the output of smartctl -d jmb39x-q,0 -l selftest --json /dev/sdX from inside the container would help us confirm the self-test log comes through and that Scrutiny parses it correctly.

    The bay setup itself is unchanged and is described under "USB/SATA Enclosures (JMicron JMB39x - QNAP TR-004/TR-002)" in docs/TROUBLESHOOTING_DEVICE_COLLECTOR.md.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions