Changes between Version 83 and Version 84 of FAQ


Ignore:
Timestamp:
Jun 23, 2025, 2:48:21 PM (9 months ago)
Author:
Christian Franke
Comment:

Prefer PRs for drive database requests, discourage database mailing list

Legend:

Unmodified
Added
Removed
Modified
  • FAQ

    v83 v84  
    342342Then create a full smartmontools report and redirect it to a text file:
    343343{{{
    344 smartctl -x /dev/sdX > smartctl-VENDOR-MODEL.txt
     344smartctl -x -a /dev/sdX > smartctl-VENDOR-MODEL.txt
    345345}}}
    346346'''Note:''' Replace `VENDOR-MODEL` in the above file name with some actual identify information for the drive.
     
    351351Alternatively you could use:
    352352{{{
    353 smartctl -q noserial -x /dev/sdX > smartctl-VENDOR-MODEL.txt
     353smartctl -q noserial -x -a /dev/sdX > smartctl-VENDOR-MODEL.txt
    354354}}}
    355355This report does not contain the "{{{Serial Number}}}" and "{{{LU WWN Device Id}}}" output lines.
    356356
    357 Then either email the file to
    358 [https://listi.jpberlin.de/mailman/listinfo/smartmontools-database smartmontools-database]
    359 mailing list or [//newticket create a ticket] here in trac.
    360 Add the file as a plain-text ASCII attachment to avoid reformatting.
    361 In tickets, [WikiFormatting#PreformattedText wiki markup for preformatted text]
    362 could be used alternatively.
    363 
    364 Place the drive model name in the email subject or ticket summary.
    365 To submit info about different drive models, please use separate emails or tickets.
     357'''Please always use `-x -a` instead of `-a`.''' The latter only prints legacy SMART information and in
     358particular lacks `Device Statistics`.
     359
     360If possible, please provide a [https://github.com/smartmontools/smartmontools/pulls pull requests] for an
     361addition to `drivedb.h` file at !GitHub.
     362Make sure to fork the `main` branch as the `master` branch from former R/O mirroring has been retired.
     363
     364Otherwise [https://github.com/smartmontools/smartmontools/issues create an issue] at !GitHub or
     365[//newticket create a ticket] here in trac.
     366
     367In each case, provide the sample output described above.
     368Add the file as a plain-text ASCII attachment to avoid reformatting or use proper markup for preformatted comments.
     369
     370Include the drive model name in the title or summary.
     371To submit info about different drive models, please use separate issues or tickets.
    366372
    367373Further information about the drive is welcome
     
    369375name of the SSD controller, an already tested drivedb.h entry, ...).
    370376
    371 Please note that there usually will be no feedback on the smartmontools-database
    372 mailing list after a drive has been added to the database.
    373 If such feedback is desired, please create a ticket instead.
    374 
     377'''Please note that the use of the ''smartmontools-database'' mailing list to request new entries is now discouraged.'''
    375378----
    376379