Version 37 (modified by 7 years ago) ( diff ) | ,
---|
Jump to: | Download | Documentation | FAQ | Help | Device Support | Contribute | Links |
Smartmontools Help Page
Table of Contents
- Frequently asked questions (FAQ)
- Mailinglists
- Serious Problem Reports
-
Howto read
smartctl
reports - Distribution-specific bug reports
- No access to Sourceforge services?
- Problems with Trac registration?
Frequently asked questions (FAQ)
If you have problems or need support, first look at the page with answers to frequently asked questions.
Mailinglists
Note: On 2017-07-30 we started new mailing lists. We will need some time to setup searchable web archives for them.
- smartmontools-support - This is the support, discussion, bug report and suggestion mailing list for smartmontools
- smartmontools-database - List for contributions of info about drives that are not yet in smartmontools drive db
- smartmontools-announce - Announcement mailing list for the smartmontools package
If you don't find an answer in the FAQs, the next step is, to search the (old) support mailing list archives.
List of searchable archives on the internet:
smartmontools-support (Old List!): | SourceForge | | - | MARC | MarkMail | Nabble | Narkive |
smartmontools-database (Old List!): | SourceForge | | Mail-Archive | MARC | - | - | Narkive |
(Gmane is offline)
If you don't find an answer to your question in the archives, then please send an email to the smartmontools-support mailing list. This is a moderated forum: you are not required to subscribe to the list in order to post your question. You can ask all questions concerning the installation and use of smartmontools. Or perhaps you want to become a developer, or suggest some new extensions?
Serious Problem Reports
If you are worried about your disks Health
state, because smartctl
gave
critical warnings or reported strange attribute values:
Have a look at the FAQ page and consult the
section on how to read smartctl reports.
If the drive fails a self-test, but still has 'PASSED
' SMART health status,
this usually means that there is a corrupted (uncorrectable=UNC) sector on the disk.
See Bad block HOWTO for
instructions about how to force this sector to reallocate.
Howto read smartctl
reports
Annotated Reports
Example Output
- ATA HDD (Hitachi) thru AHCI controller (
smartctl 6.5
) - SSD (Intel) thru AHCI controller (
smartctl 6.5
) - SAS HDD (Hitachi) thru MegaRAID SAS 1078 controller (
smartctl 6.5
) - SAS HDD (HP) thru HP Smart Array controller (
smartctl 5.43
)
Faulty Disks
- SSD (Toshiba) - self test detected read failure (
smartctl 6.5
)
Distribution-specific bug reports
The smartmontools package supports a number of different operating systems. Some of those operating systems are also distributed by multiple sources, and some of these maintain a database of bug reports. Here are links:
- Debian Linux bug database
- Redhat/Fedora Linux bugzilla database
- Gentoo Linux bugzilla database
- Ubuntu Linux bug database
- FreeBSD bugzilla database
- NetBSD bug database
- MacPorts bug database
If you can provide additional distribution or OS-specific bug-database links, please send an email to smartmontools-support mailing list.
No access to Sourceforge services?
Our project offers File Download and SVN which are hosted in our project at SourceForge. SourceForge is a free service, which supports a very large number of users and projects. Please check SF.net Operations to see the maintenance schedule and to learn if SourceForge is experiencing unscheduled system outages or other problems.
For download purposes you can also use the SVN mirror and the daily builds on our own internet servers.
Problems with Trac registration?
In case of problems with your Trac registration write to the smartmontools team list. This is a private list. Postings from non-member addresses are held in moderation queue and need manual approvement to go to the list. So you have to take a delay into account until your mail reaches the smartmontools team members.
License
All content in this wiki is published under GNU GPL if not otherwise explicitly declared in context of a contributed section or page.