309 | | few minutes for the test to complete. Then email |
310 | | the entire output from:[[BR]] |
311 | | {{{ |
312 | | smartctl -x /dev/sdX |
313 | | }}} |
314 | | |
315 | | to [https://lists.sourceforge.net/lists/listinfo/smartmontools-database smartmontools-database] |
316 | | as a plain-text ASCII email attachment (file type: ".txt"). The timestamp |
317 | | in the self-test log will help us to determine whether Attribute 9 is |
| 309 | few minutes for the test to complete. |
| 310 | Then create a full smartmontools report and redirect it to a text file: |
| 311 | {{{ |
| 312 | smartctl -x /dev/sdX > smartctl-VENDOR-MODEL.txt |
| 313 | }}} |
| 314 | The timestamp in the self-test log will help us to determine whether Attribute 9 is |
326 | | If you need to use any of the vendor-specific display options |
327 | | ({{{-v}}} options) with the drive, or if any of the Attributes are |
328 | | behaving strangely, please include that information as well. |
| 323 | Then either email the file to |
| 324 | [https://lists.sourceforge.net/lists/listinfo/smartmontools-database smartmontools-database] |
| 325 | mailing list or [//newticket create a ticket] here in trac. |
| 326 | Add the file as a plain-text ASCII attachment to avoid reformatting. |
| 327 | In tickets, [WikiFormatting#PreformattedText wiki markup for preformatted text] |
| 328 | could be used alternatively. |
| 329 | |
| 330 | Place the drive model name in the email subject or ticket summary. |
| 331 | To submit info about different drive models, please use separate emails or tickets. |
| 332 | |
| 333 | Further information about the drive is welcome |
| 334 | (link to device specification, output from a vendor specific SMART tool, |
| 335 | name of the SSD controller, an already tested drivedb.h entry, ...). |
| 336 | |
| 337 | Please note that there usually will be no feedback on the smartmontools-database |
| 338 | mailing list after a drive has been added to the database. |
| 339 | If such feedback is desired, please create a ticket instead. |