NAS Doctor

NAS Doctor is a local diagnostic and monitoring dashboard for NAS and home servers that runs periodic SMART, ZFS, Docker, GPU, network, temperature, and power…

  • Infrastructure
  • Monitoring & Logging
  • Tools & Utilities
NAS Doctor is a local diagnostic and monitoring dashboard for NAS and home servers that runs periodic SMART, ZFS, Docker, GPU, network, temperature, and power health checks, then provides actionable recommendations backed by Backblaze failure-rate data without requiring a cloud account.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

58/100 Fair

Maintained
77last commit 9 days ago
Popular
2721 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data
Security check
82no serious findings, 3 minor, CI, tests

Based on 4 of 5 factors.

Availability: platform listings confirmed today, links checked 20 days ago

GitHub stars
21
Open issues
8
Last commit
2026-11-12
Latest release
v0.10.4
License
MIT
Activity
declining

Checked 6 days ago - source: GitHub (mcdays94/nas-doctor)

Resources & Compatibility

Requirements not published yet.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Start your VPN if you use remote access If you use a VPN (a secure tunnel for remote access), run the matching start command in the terminal (the text command window), such as `tailscale up` or `netbird up`. Without that step, the VPN is not connected and remote access can fail even if the app is installed. source
  • Keep pool mount scripts in the right place If you use custom startup scripts for storage pools (groups of disks), keep them under /boot/optional/scripts/pools/mounted/ with a name matching the pool, like media.sh. If the script is missing or in the wrong folder, that pool may not mount automatically after a reboot. source
  • Use a clear iSCSI storage name If you expose disk space over iSCSI (a way to make NAS storage available over the network), set a clear IQN (the storage target's unique name) like iqn.2026-01.net.mos-official:target1. A wrong or unclear name can make the storage hard to find when another device tries to connect. source
  • Docker deployment and beta support Deploy NAS Doctor as a Docker container on Unraid, TrueNAS, Synology, Proxmox, or Kubernetes. It is in beta; core features are stable on Unraid, while other platforms may have edge cases. source
  • Beta support NAS Doctor is in active beta; core features are stable and tested on Unraid, while other platforms may have edge cases. source

Fetched today - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Does NAS Doctor require a cloud account for basic use?

No. It is a local diagnostic and monitoring tool and does not require a cloud account.

Does NAS Doctor check ZFS storage health?

Yes. It runs periodic ZFS health checks as part of its local diagnostics.

Does NAS Doctor use external drive failure data for its recommendations?

Yes. Its recommendations are backed by Backblaze failure-rate data.

Answers sourced from github.com

Community

Collected 49 days ago - public community threads