{ "created": "2015-12-20T19:57:07Z", "hierarchy": [ { "name": "ROOT", "type": "folder", "uri": "/ROOT" }, { "name": "Testing New Hard Drives", "type": "article", "uri": "Testing_New_Hard_Drives" } ], "html": "\n\n \n \n \n \n \n \n \n \n \n \n \n Testing New Hard Drives – Nikhil's Personal Wiki\n \n \n \n \n \n
\n
\n \n
\n
\n \n \n\n

Testing New Hard Drives\n \n

\n

Find out the disks on the system

\n
cat /var/run/dmesg.boot\n
\n

Run the short test in the background1.

\n
smartctl -t short /dev/ada0\n
\n

Then run a conveyance test (for any damage during shipping)

\n
smartctl -t conveyance /dev/ada0\n
\n

Then check for bad blocks23.

\n
badblocks -ws /dev/ada0\n
\n

Then run a long test4.

\n
smartctl -t long /dev/ada0\n
\n

The -a flag shows you everything about the drives

\n
smartctl -a /dev/ada0\n
\n

including the time remaining for the tests

\n
Self-test execution status:      ( 249) Self-test routine in progress...\n                                        90% of test remaining.\n
\n

and the time it would take to run the tests:

\n
Short self-test routine\nrecommended polling time:    (   2) minutes.\nExtended self-test routine\nrecommended polling time:    ( 529) minutes.\nConveyance self-test routine\nrecommended polling time:    (   5) minutes.\n
\n

To see the results after the tests have run

\n
smartctl -l selftest /dev/ada0\n
\n

References

\n\n

Footnotes

\n
\n
\n
    \n
  1. \n

    Use -C to run in foreground. But then again, why would you? ↩︎

    \n
    2. \n
  2. \n

    The non-destructive version is badblocks -ns. ↩︎

    \n
    3. \n
  3. \n

    This is a 2-phase, 4-pass command that will take a long time. On
    \na 4TB WD Red, the whole process was done in about 75 hours. ↩︎

    \n
    4. \n
  4. \n

    This took about 8 hours on a 4TB WD Red. ↩︎

    \n
    5. \n
\n
\n\n\n
\n \n
\n \n \n \n \n \n\n", "id": "e5006eb8-4a3b-5ad7-8757-47709303770f", "modified": "2026-05-28T13:06:24Z", "revisions": [ { "authorEmail": "mail@nikhil.io", "authorName": "Nikhil Anand", "date": "2026-05-28T13:06:24Z", "id": "775dab2e0ac6d0d00b6aa3e283bd67833cd08cea", "shortId": "775dab2e", "subject": "Formatting fixes -- Claude\n", "content": "Find out the disks on the system\n\n cat /var/run/dmesg.boot\n\nRun the short test in the background[^1].\n\n smartctl -t short /dev/ada0\n\nThen run a conveyance test (for any damage during shipping)\n\n smartctl -t conveyance /dev/ada0\n\nThen check for [bad blocks](https://wiki.archlinux.org/index.php/Badblocks)[^2][^3].\n\n badblocks -ws /dev/ada0\n\nThen run a long test[^4].\n\n smartctl -t long /dev/ada0\n\nThe `-a` flag shows you everything about the drives\n\n smartctl -a /dev/ada0\n\nincluding the time remaining for the tests\n\n Self-test execution status:      ( 249) Self-test routine in progress...\n                                         90% of test remaining.\n\nand the time it would take to run the tests:\n\n Short self-test routine\n recommended polling time:    (   2) minutes.\n Extended self-test routine\n recommended polling time:    ( 529) minutes.\n Conveyance self-test routine\n recommended polling time:    (   5) minutes.\n\nTo see the results *after* the tests have run\n\n smartctl -l selftest /dev/ada0\n\n## References\n\n* [Interpreting `badblocks` data](https://forums.freenas.org/index.php?threads/interpreting-badblocks-output.27421/).\n\n## Footnotes\n\n[^1]: Use `-C` to run in foreground. But then again, why would you?\n\n[^2]: The non-destructive version is `badblocks -ns`.\n\n[^3]: This is a 2-phase, 4-pass command that will take a *long* time. On\n a 4TB WD Red, the whole process was done in about 75 hours.\n\n[^4]: This took about 8 hours on a 4TB WD Red.\n" }, { "authorEmail": "mail@nikhil.io", "authorName": "Nikhil Anand", "date": "2026-01-13T18:47:28Z", "id": "2436477560f26e23d00a24add1cbfeafdca4af78", "shortId": "24364775", "subject": "No compression\n", "content": "Find out the disks on the system\n\n cat /var/run/dmesg.boot\n\nRun the short test in the background[^1].\n\n smartctl -t short /dev/ada0\n\nThen run a conveyance test (for any damage during shipping)\n\n smartctl -t conveyance /dev/ada0\n\nThen check for [bad\nblocks](https://wiki.archlinux.org/index.php/Badblocks)[^2][^3].\n\n badblocks -ws /dev/ada0\n\nThen run a long test[^4].\n\n smartctl -t long /dev/ada0\n\nThe `-a` flag shows you everything about the drives\n\n smartctl -a /dev/ada0\n\nincluding the time remaining for the tests\n\n Self-test execution status:      ( 249) Self-test routine in progress... \n                                         90% of test remaining.\n\nand the time it would take to run the tests:\n\n Short self-test routine \n recommended polling time:    (   2) minutes. \n Extended self-test routine \n recommended polling time:    ( 529) minutes. \n Conveyance self-test routine \n recommended polling time:    (   5) minutes.\n\nTo see the results *after* the tests have run\n\n smartctl -l selftest /dev/ada0\n\nReferences\n----------\n\n* [Interpreting `badblocks` data](https://forums.freenas.org/index.php?threads/interpreting-badblocks-output.27421/).\n\nFootnotes\n---------\n\n[^1]: Use `-C` to run in foreground. But then again, why would you?\n\n[^2]: The non-destructive version is `badblocks -ns`.\n\n[^3]: This is a 2-phase, 4-pass command that will take a *long* time. On\n a 4TB WD Red, the whole process was done in about 75 hours.\n\n[^4]: This took about 8 hours on a 4TB WD Red.\n" }, { "authorEmail": "mail@nikhil.io", "authorName": "Nikhil Anand", "date": "2015-12-27T07:27:56Z", "id": "1aa29105a45aa67523ffb61e73bcc415f935a47e", "shortId": "1aa29105", "subject": "Fix Markdown conversion\n\nSaw half a season of The Office\n", "content": "Find out the disks on the system\n\n cat /var/run/dmesg.boot\n\nRun the short test in the background[^1].\n\n smartctl -t short /dev/ada0\n\nThen run a conveyance test (for any damage during shipping)\n\n smartctl -t conveyance /dev/ada0\n\nThen check for [bad\nblocks](https://wiki.archlinux.org/index.php/Badblocks)[^2][^3].\n\n badblocks -ws /dev/ada0\n\nThen run a long test[^4].\n\n smartctl -t long /dev/ada0\n\nThe `-a` flag shows you everything about the drives\n\n smartctl -a /dev/ada0\n\nincluding the time remaining for the tests\n\n Self-test execution status:      ( 249) Self-test routine in progress... \n                                         90% of test remaining.\n\nand the time it would take to run the tests:\n\n Short self-test routine \n recommended polling time:    (   2) minutes. \n Extended self-test routine \n recommended polling time:    ( 529) minutes. \n Conveyance self-test routine \n recommended polling time:    (   5) minutes.\n\nTo see the results *after* the tests have run\n\n smartctl -l selftest /dev/ada0\n\nReferences\n----------\n\n* [Interpreting `badblocks` data](https://forums.freenas.org/index.php?threads/interpreting-badblocks-output.27421/).\n\nFootnotes\n---------\n\n[^1]: Use `-C` to run in foreground. But then again, why would you?\n\n[^2]: The non-destructive version is `badblocks -ns`.\n\n[^3]: This is a 2-phase, 4-pass command that will take a *long* time. On\n a 4TB WD Red, the whole process was done in about 75 hours.\n\n[^4]: This took about 8 hours on a 4TB WD Red.\n" }, { "authorEmail": "mail@nikhil.io", "authorName": "Nikhil Anand", "date": "2015-12-21T02:30:47Z", "id": "d658e80d1ecb97b196531c7b15a0f9af709c05de", "shortId": "d658e80d", "subject": "Incremental\n", "content": "Find out the disks on the system\n\n` cat /var/run/dmesg.boot`\n\nRun the short test in the background[^1].\n\n` smartctl -t short /dev/ada0`\n\nThen run a conveyance test (for any damage during shipping)\n\n` smartctl -t conveyance /dev/ada0`\n\nThen check for [bad\nblocks](https://wiki.archlinux.org/index.php/Badblocks)[^2][^3].\n\n` badblocks -ws /dev/ada0`\n\nThen run a long test[^4].\n\n` smartctl -t long /dev/ada0`\n\nThe `-a` flag shows you everything about the drives\n\n` smartctl -a /dev/ada0`\n\nincluding the time remaining for the tests\n\n` Self-test execution status:      ( 249) Self-test routine in progress...` \n`                                         90% of test remaining.`\n\nand the time it would take to run the tests:\n\n` Short self-test routine` \n` recommended polling time:    (   2) minutes.` \n` Extended self-test routine` \n` recommended polling time:    ( 529) minutes.` \n` Conveyance self-test routine` \n` recommended polling time:    (   5) minutes.`\n\nTo see the results *after* the tests have run\n\n` smartctl -l selftest /dev/ada0`\n\nReferences\n----------\n\n- [Interpreting `badblocks`\n data](https://forums.freenas.org/index.php?threads/interpreting-badblocks-output.27421/).\n\nFootnotes\n---------\n\n[^1]: Use `-C` to run in foreground. But then again, why would you?\n\n[^2]: The non-destructive version is `badblocks -ns`.\n\n[^3]: This is a 2-phase, 4-pass command that will take a *long* time. On\n a 4TB WD Red, the whole process was done in about 75 hours.\n\n[^4]: This took about 8 hours on a 4TB WD Red.\n" }, { "authorEmail": "mail@nikhil.io", "authorName": "Nikhil Anand", "date": "2015-12-20T19:57:08Z", "id": "98df4c4dcadea017ceca30ffc5632ff916229edc", "shortId": "98df4c4d", "subject": "Testing New Hard Drives : v8\n", "content": "Find out the disks on the system\n\n` cat /var/run/dmesg.boot`\n\nRun the short test in the background[^1].\n\n` smartctl -t short /dev/ada0`\n\nThen run a conveyance test (for any damage during shipping)\n\n` smartctl -t conveyance /dev/ada0`\n\nThen check for [bad\nblocks](https://wiki.archlinux.org/index.php/Badblocks)[^2][^3].\n\n` badblocks -ws /dev/ada0`\n\nThen run a long test[^4].\n\n` smartctl -t long /dev/ada0`\n\nThe `-a` flag shows you everything about the drives\n\n` smartctl -a /dev/ada0`\n\nincluding the time remaining for the tests\n\n` Self-test execution status:      ( 249) Self-test routine in progress...` \n`                                         90% of test remaining.`\n\nand the time it would take to run the tests:\n\n` Short self-test routine` \n` recommended polling time:    (   2) minutes.` \n` Extended self-test routine` \n` recommended polling time:    ( 529) minutes.` \n` Conveyance self-test routine` \n` recommended polling time:    (   5) minutes.`\n\nTo see the results *after* the tests have run\n\n` smartctl -l selftest /dev/ada0`\n\nReferences\n----------\n\n- [Interpreting `badblocks`\n data](https://forums.freenas.org/index.php?threads/interpreting-badblocks-output.27421/).\n\nFootnotes\n---------\n\n\n[Category: Nikhil's Notes](Category:_Nikhil's_Notes \"wikilink\")\n[Category: FreeNAS](Category:_FreeNAS \"wikilink\")\n\n[^1]: Use `-C` to run in foreground. But then again, why would you?\n\n[^2]: The non-destructive version is `badblocks -ns`.\n\n[^3]: This is a 2-phase, 4-pass command that will take a *long* time. On\n a 4TB WD Red, the whole process was done in about 75 hours.\n\n[^4]: This took about 8 hours on a 4TB WD Red.\n" }, { "authorEmail": "mail@nikhil.io", "authorName": "Nikhil Anand", "date": "2015-12-20T19:57:08Z", "id": "f4b80202d22188b0d56e5f2be0a24ea96cacc747", "shortId": "f4b80202", "subject": "Testing New Hard Drives : v7\n", "content": "Find out the disks on the system\n\n` cat /var/run/dmesg.boot`\n\nRun the short test in the background[^1].\n\n` smartctl -t short /dev/ada0`\n\nThen run a conveyance test (for any damage during shipping)\n\n` smartctl -t conveyance /dev/ada0`\n\nThen check for [bad\nblocks](https://wiki.archlinux.org/index.php/Badblocks)[^2]. This is a\n2-phase, 4-pass command that will take a *long* time. On a 4TB WD Red,\nthe whole process was done in about 75 hours.\n\n` badblocks -ws /dev/ada0`\n\nThen run a long test\n\n` smartctl -t long /dev/ada0`\n\nThe `-a` flag shows you everything about the drives\n\n` smartctl -a /dev/ada0`\n\nincluding the time remaining for the tests\n\n` Self-test execution status:      ( 249) Self-test routine in progress...` \n`                                         90% of test remaining.`\n\nand the time it would take to run the tests:\n\n` Short self-test routine` \n` recommended polling time:    (   2) minutes.` \n` Extended self-test routine` \n` recommended polling time:    ( 529) minutes.` \n` Conveyance self-test routine` \n` recommended polling time:    (   5) minutes.`\n\nTo see the results *after* the tests have run\n\n` smartctl -l selftest /dev/ada0`\n\nReferences\n----------\n\n- [Interpreting `badblocks`\n data](https://forums.freenas.org/index.php?threads/interpreting-badblocks-output.27421/).\n\nFootnotes\n---------\n\n\n[Category: Nikhil's Notes](Category:_Nikhil's_Notes \"wikilink\")\n[Category: FreeNAS](Category:_FreeNAS \"wikilink\")\n\n[^1]: Use `-C` to run in foreground. But then again, why would you?\n\n[^2]: The non-destructive version is `badblocks -ns`.\n" }, { "authorEmail": "mail@nikhil.io", "authorName": "Nikhil Anand", "date": "2015-12-20T19:57:08Z", "id": "a687eb68ec97a32b62c37cec060db0af2bca38bb", "shortId": "a687eb68", "subject": "Testing New Hard Drives : v6\n", "content": "Find out the disks on the system\n\n` cat /var/run/dmesg.boot`\n\nRun the short test in the background[^1].\n\n` smartctl -t short /dev/ada0`\n\nThen run a conveyance test (for any damage during shipping)\n\n` smartctl -t conveyance /dev/ada0`\n\nThen check for [bad\nblocks](https://wiki.archlinux.org/index.php/Badblocks)[^2]. This is a\n2-phase, 4-pass command that will take a *long* time. On a 4TB WD Red,\neach phase took \\~8 hours.\n\n` badblocks -ws /dev/ada0`\n\nThen run a long test\n\n` smartctl -t long /dev/ada0`\n\nThe `-a` flag shows you everything about the drives\n\n` smartctl -a /dev/ada0`\n\nincluding the time remaining for the tests\n\n` Self-test execution status:      ( 249) Self-test routine in progress...` \n`                                         90% of test remaining.`\n\nand the time it would take to run the tests:\n\n` Short self-test routine` \n` recommended polling time:    (   2) minutes.` \n` Extended self-test routine` \n` recommended polling time:    ( 529) minutes.` \n` Conveyance self-test routine` \n` recommended polling time:    (   5) minutes.`\n\nTo see the results *after* the tests have run\n\n` smartctl -l selftest /dev/ada0`\n\nReferences\n----------\n\n- [Interpreting `badblocks`\n data](https://forums.freenas.org/index.php?threads/interpreting-badblocks-output.27421/).\n\nFootnotes\n---------\n\n\n[Category: Nikhil's Notes](Category:_Nikhil's_Notes \"wikilink\")\n[Category: FreeNAS](Category:_FreeNAS \"wikilink\")\n\n[^1]: Use `-C` to run in foreground. But then again, why would you?\n\n[^2]: The non-destructive version is `badblocks -ns`.\n" }, { "authorEmail": "mail@nikhil.io", "authorName": "Nikhil Anand", "date": "2015-12-20T19:57:08Z", "id": "696b09b2496e0e060463d798743ea87e61f48071", "shortId": "696b09b2", "subject": "Testing New Hard Drives : v5\n", "content": "Find out the disks on the system\n\n` cat /var/run/dmesg.boot`\n\nRun the short test in the background[^1].\n\n` smartctl -t short /dev/ada0`\n\nThen run a conveyance test (for any damage during shipping)\n\n` smartctl -t conveyance /dev/ada0`\n\nThen check for [bad\nblocks](https://wiki.archlinux.org/index.php/Badblocks)[^2]\n\n` badblocks -ws /dev/ada0`\n\nThen run a long test\n\n` smartctl -t long /dev/ada0`\n\nThe `-a` flag shows you everything about the drives\n\n` smartctl -a /dev/ada0`\n\nincluding the time remaining for the tests\n\n` Self-test execution status:      ( 249) Self-test routine in progress...` \n`                                         90% of test remaining.`\n\nand the time it would take to run the tests:\n\n` Short self-test routine` \n` recommended polling time:    (   2) minutes.` \n` Extended self-test routine` \n` recommended polling time:    ( 529) minutes.` \n` Conveyance self-test routine` \n` recommended polling time:    (   5) minutes.`\n\nTo see the results *after* the tests have run\n\n` smartctl -l selftest /dev/ada0`\n\nReferences\n----------\n\n- [Interpreting `badblocks`\n data](https://forums.freenas.org/index.php?threads/interpreting-badblocks-output.27421/).\n\nFootnotes\n---------\n\n\n[Category: Nikhil's Notes](Category:_Nikhil's_Notes \"wikilink\")\n[Category: FreeNAS](Category:_FreeNAS \"wikilink\")\n\n[^1]: Use `-C` to run in foreground. But then again, why would you?\n\n[^2]: The non-destructive version is `badblocks -ns`.\n" }, { "authorEmail": "mail@nikhil.io", "authorName": "Nikhil Anand", "date": "2015-12-20T19:57:08Z", "id": "ba1b9e19cdf23b4ceb3f876a63a03abf84dcd976", "shortId": "ba1b9e19", "subject": "Testing New Hard Drives : v4\n", "content": "Find out the disks on the system\n\n` cat /var/run/dmesg.boot`\n\nRun the short test in the background[^1].\n\n` smartctl -t short /dev/ada0`\n\nThen run a conveyance test (for any damage during shipping)\n\n` smartctl -t conveyance /dev/ada0`\n\nThen check for [bad\nblocks](https://wiki.archlinux.org/index.php/Badblocks)[^2]\n\n` badblocks -ws /dev/ada0`\n\nThen run a long test\n\n` smartctl -t long /dev/ada0`\n\nThe `-a` flag shows you everything about the drives\n\n` smartctl -a /dev/ada0`\n\nincluding the time remaining for the tests\n\n` Self-test execution status:      ( 249) Self-test routine in progress...` \n`                                         90% of test remaining.`\n\nand the time it would take to run the tests:\n\n` Short self-test routine` \n` recommended polling time:    (   2) minutes.` \n` Extended self-test routine` \n` recommended polling time:    ( 529) minutes.` \n` Conveyance self-test routine` \n` recommended polling time:    (   5) minutes.`\n\nTo see the results *after* the tests have run\n\n` smartctl -l selftest /dev/ada0`\n\nFootnotes\n---------\n\n\n[Category: Nikhil's Notes](Category:_Nikhil's_Notes \"wikilink\")\n[Category: FreeNAS](Category:_FreeNAS \"wikilink\")\n\n[^1]: Use `-C` to run in foreground. But then again, why would you?\n\n[^2]: The non-destructive version is `badblocks -ns`.\n" }, { "authorEmail": "mail@nikhil.io", "authorName": "Nikhil Anand", "date": "2015-12-20T19:57:08Z", "id": "06ce9e9f64032516f2663f2a557d66040fdf20d4", "shortId": "06ce9e9f", "subject": "Testing New Hard Drives : v3\n", "content": "Find out the disks on the system\n\n` cat /var/run/dmesg.boot`\n\nRun the short test in the background[^1].\n\n` smartctl -t short /dev/ada0`\n\nThen run a conveyance test (for any damage during shipping)\n\n` smartctl -t conveyance /dev/ada0`\n\nThen check for bad blocks[^2]\n\n` badblocks -ws /dev/ada0`\n\nThen run a long test\n\n` smartctl -t long /dev/ada0`\n\nThe `-a` flag shows you everything about the drives\n\n` smartctl -a /dev/ada0`\n\nincluding the time remaining for the tests\n\n` Self-test execution status:      ( 249) Self-test routine in progress...` \n`                                         90% of test remaining.`\n\nand the time it would take to run the tests:\n\n` Short self-test routine` \n` recommended polling time:    (   2) minutes.` \n` Extended self-test routine` \n` recommended polling time:    ( 529) minutes.` \n` Conveyance self-test routine` \n` recommended polling time:    (   5) minutes.`\n\nTo see the results *after* the tests have run\n\n` smartctl -l selftest /dev/ada0`\n\nFootnotes\n---------\n\n\n[Category: Nikhil's Notes](Category:_Nikhil's_Notes \"wikilink\")\n[Category: FreeNAS](Category:_FreeNAS \"wikilink\")\n\n[^1]: Use `-C` to run in foreground. But then again, why would you?\n\n[^2]: The non-destructive version is `badblocks -ns`.\n" }, { "authorEmail": "mail@nikhil.io", "authorName": "Nikhil Anand", "date": "2015-12-20T19:57:07Z", "id": "c0e76a0c86e1ca2b6a167beef90af4ebac633ef7", "shortId": "c0e76a0c", "subject": "Testing New Hard Drives : v2\n", "content": "Find out the disks on the system\n\n` cat /var/run/dmesg.boot`\n\nRun the short test in the background[^1].\n\n` smartctl -t short /dev/ada0`\n\nThen run a conveyance test (for any damage during shipping)\n\n` smartctl -t conveyance /dev/ada0`\n\nThen run a long test\n\n` smartctl -t long /dev/ada0`\n\nThe `-a` flag shows you everything about the drives\n\n` smartctl -a /dev/ada0`\n\nincluding the time remaining for the tests\n\n` Self-test execution status:      ( 249) Self-test routine in progress...` \n`                                         90% of test remaining.`\n\nand the time it would take to run the tests:\n\n` Short self-test routine` \n` recommended polling time:    (   2) minutes.` \n` Extended self-test routine` \n` recommended polling time:    ( 529) minutes.` \n` Conveyance self-test routine` \n` recommended polling time:    (   5) minutes.`\n\nTo see the results *after* the tests have run\n\n` smartctl -l selftest /dev/ada0`\n\nFootnotes\n---------\n\n\n[Category: Nikhil's Notes](Category:_Nikhil's_Notes \"wikilink\")\n[Category: FreeNAS](Category:_FreeNAS \"wikilink\")\n\n[^1]: Use `-C` to run in foreground. But then again, why would you?\n" }, { "authorEmail": "mail@nikhil.io", "authorName": "Nikhil Anand", "date": "2015-12-20T19:57:07Z", "id": "148056bc3c0738f711d5d2f7cb5cb79fd3974630", "shortId": "148056bc", "subject": "Testing New Hard Drives : First Draft\n", "content": "Find out the disks on the system\n\n` cat /var/run/dmesg.boot`\n\nRun the short test in the background[^1].\n\n` smartctl -t short /dev/ada0`\n\nThen run a conveyance test (for any damage during shipping)\n\n` smartctl -t conveyance /dev/ada0`\n\nThen run a long test\n\n` smartctl -t long /dev/ada0`\n\nThe `-a` flag shows you everything about the drives\n\n` smartctl -a long /dev/ada0`\n\nincluding the time remaining for the tests\n\n` Self-test execution status:      ( 249) Self-test routine in progress...` \n`                                         90% of test remaining.`\n\nand the time it would take to run the tests:\n\n` Short self-test routine` \n` recommended polling time:    (   2) minutes.` \n` Extended self-test routine` \n` recommended polling time:    ( 529) minutes.` \n` Conveyance self-test routine` \n` recommended polling time:    (   5) minutes.`\n\nTo see the results *after* the tests have run\n\n` smartctl -l selftest /dev/ada0`\n\nFootnotes\n---------\n\n\n[Category: Nikhil's Notes](Category:_Nikhil's_Notes \"wikilink\")\n[Category: FreeNAS](Category:_FreeNAS \"wikilink\")\n\n[^1]: Use `-C` to run in foreground. But then again, why would you?\n" } ], "sizeInBytes": 1616, "source": "Find out the disks on the system\n\n cat /var/run/dmesg.boot\n\nRun the short test in the background[^1].\n\n smartctl -t short /dev/ada0\n\nThen run a conveyance test (for any damage during shipping)\n\n smartctl -t conveyance /dev/ada0\n\nThen check for [bad blocks](https://wiki.archlinux.org/index.php/Badblocks)[^2][^3].\n\n badblocks -ws /dev/ada0\n\nThen run a long test[^4].\n\n smartctl -t long /dev/ada0\n\nThe `-a` flag shows you everything about the drives\n\n smartctl -a /dev/ada0\n\nincluding the time remaining for the tests\n\n Self-test execution status:      ( 249) Self-test routine in progress...\n                                         90% of test remaining.\n\nand the time it would take to run the tests:\n\n Short self-test routine\n recommended polling time:    (   2) minutes.\n Extended self-test routine\n recommended polling time:    ( 529) minutes.\n Conveyance self-test routine\n recommended polling time:    (   5) minutes.\n\nTo see the results *after* the tests have run\n\n smartctl -l selftest /dev/ada0\n\n## References\n\n* [Interpreting `badblocks` data](https://forums.freenas.org/index.php?threads/interpreting-badblocks-output.27421/).\n\n## Footnotes\n\n[^1]: Use `-C` to run in foreground. But then again, why would you?\n\n[^2]: The non-destructive version is `badblocks -ns`.\n\n[^3]: This is a 2-phase, 4-pass command that will take a *long* time. On\n a 4TB WD Red, the whole process was done in about 75 hours.\n\n[^4]: This took about 8 hours on a 4TB WD Red.\n", "title": "Testing New Hard Drives", "untracked": false, "uri": "/Testing_New_Hard_Drives", "relativePath": "Testing New Hard Drives.md" }