| Version 211 (modified by , 11 months ago) ( diff ) |
|---|
Jump to: | Download | Documentation | FAQ | Help | Device Support | Contribute | Links |
News
2024-01-03: Project Trac and Wiki upgraded to the latest 1.6 version.2023-09-16: The CI builds at builds.smartmontools.org are now reproducible if the same SOURCE_DATE_EPOCH, build recipes and toolchains are used.2023-08-01: We released version 7.4 of Smartmontools. See the NEWS file and the ticket report to get a summary of the changes and new features.2023-06-30: CI builds (builds.smartmontools.org) for macOS now support arm64 and x86_64 architectures, i386 requires build from source. This will also be the case for future release builds.2022-10-10: 20th anniversary of smartmontools first release - see also smartmontools history.2022-02-28: We released version 7.3 of Smartmontools.2022-02-04: Alexander Shaduri released version 1.1.4 of GSmartControl (a graphical user interface for smartctl). Available for Linux, FreeBSD, MacOS X and Windows.2021-10-23: There is a security issue ifsmartdis used conjunction with GNU mailutils < 3.13. See ticket #1535 for details and various possible fixes.2020-12-30: We released version 7.2 of Smartmontools.2019-12-30: We released version 7.1 of Smartmontools.2019-12-01: Smartmontools website migrated to the new server. Please let us know in case of any issues.2018-12-30: We released version 7.0 of Smartmontools.2018-10-17: In the past we offered daily builds on builds.smartmontools.org. Now we do automated builds on every commit to the repository. Read more about it in section GitHub mirror and Circle CI integration below.2017-11-12: Alexander Shaduri released version 1.1.3 of GSmartControl (a graphical user interface for smartctl). Available for Linux, FreeBSD, MacOS X and Windows.2017-07-30: Our mailing lists moved from sourceforge to JPBerlin. (!) Please subscribe on the new mailing lists.2017-04-11: We moved the Bad block HOWTO for smartmontools from the svn repository to the Trac wiki. So it is open now for your contributions of further recipes, case studies and comments.- ...see here for further news
About Smartmontools
The smartmontools package contains two utility programs (smartctl and smartd)
to control and monitor storage systems using the Self-Monitoring, Analysis and
Reporting Technology System (SMART) built into most modern ATA/SATA, SCSI/SAS and NVMe disks.
In many cases, these utilities will provide advanced warning of disk degradation and failure.
Smartmontools was originally derived from the Linux smartsuite package and actually supports ATA/SATA, SCSI/SAS and NVMe disks and also SCSI/SAS tape devices.
It should run on any modern Linux, FreeBSD, NetBSD, OpenBSD, Darwin (macOS), Solaris, Windows, Cygwin, OS/2, eComStation or QNX system.
Smartmontools can also be run from one of many different Live CDs/DVDs.
Sourcecode tarballs and precompiled packages for Darwin (macOS) and Windows are available at the project page at Sourceforge.
Precompiled packages are available from the repositories of various distributions, see the Packages page or Repology.org. Some examples:
...
Due to OS-specific issues and also depending on the different state of smartmontools development on the platforms, device support is not the same for all OS platforms. See info about RAID-controller, USB and NVMe support here on the homepage and of course in the manpages.
Thanks to Alexander Shaduri, there is also a graphical user interface for smartctl available.
Go to the Homepage of GSmartControl to get all info and the software itself.
Have a look at the screenshots
and the feature list to get an impression of this nice tool.
Contribute to Smartmontools
Device Information
If your drive is not in the current version of smartmontools drive database, you can help to improve smartmontools information by sending a report about your drive to our mailinglist smartmontools-database.
We collect info about USB devices that have been successfully or unsuccessfully tested with smartmontools. If you have a device not listed there, please tell us the test result, by editing the wiki page, and/or by sending an email to the smartmontools-database mailinglist.
Bug Reports
To submit a bug report or propose an enhancement for smartmontools create a new ticket here in trac. Login is needed for that. If you don't want to register an account, you can also send the info to our smartmontools-support mailing list.
Patches
Patches are welcome! The most convenient way for us is, when you attach them to a new ticket here in trac. But it's also possible to submit patches for code review to developers mailinglist. You don't need to be member of the mailinglist for it. Our list moderator will approve posting requests in these cases. Your patches should refer to our recent code base in SVN. You should also have a look at the documents in the developers area here in the wiki. You will find info about smartmontools software architecture and tutorials and guidelines from our developers there.
GitHub mirror and Circle CI integration
For those who prefer to use git and GitHub we maintain an official mirror of the smartmontools project. Feel free to fork, submit PR-s and issues. The mirror is updated every 15 minutes from our sourceforge SVN. Also a Circle CI Continuous Integration and Delivery system has been setup, see builds page for the details. Every commit to the GitHub triggers a new build and provides a source tarball and various binaries as artifacts.
- GitHub:
- Trunk build status:
- CodeQL scanning:
Incident Reports
If you see a failure or have a problem with our project facilities you may report it to
smartmontools-devel@listi.jpberlin.de. You don't need to be subscribed for that. Your mail will then go to the list moderator and she will take action to solve the issue. Project uptime is monitored on the status page hosted by BetterStack service.
License
Smartmontools (and content in this wiki) are published under GNU GPL.
