WD Red SMART data reset itself












1















I have bought 4 used 6TB WD Red drives (WDC WD60EFRX-68MYMN1) for use in my HP Microserver Gen8. The server is running Debian Linux 9. The disk controller is using AHCI, no hardware RAID.



Initially I tested all drives, checked SMART values using smartctl (lifetime was around 2.5 years for all of them), ran some self tests (conveyance and long), read the entire surface, and I'm sure they're healthy.



During data migration, I unplugged and plugged back in all drives several times. The Microserver advises against that with "non hot-swap" written on the drive bays, but I ignore this as it tends to work regardless.



Once the migration was done and the dust had settled, I check the SMART values again. To my surprise, 2 of the 4 drives had their SMART values literally reset. All values were back to 0, and they're happily counting back up again (e.g. in the case of power on hours or start/stop count). Other than that, they seem to be working perfectly fine.



How is this possible? If it had just been one drive, I would chalk it up to a random fluke. But two drives?



Searching the 'tubes reveals no such occurences having happened before, and while certain Seagate drives apparently had, for a time, the ability to manually reset SMART, it always involved hooking up a serial interface to the extra pins next to the SATA connector and deliberately initiating the process.










share|improve this question



























    1















    I have bought 4 used 6TB WD Red drives (WDC WD60EFRX-68MYMN1) for use in my HP Microserver Gen8. The server is running Debian Linux 9. The disk controller is using AHCI, no hardware RAID.



    Initially I tested all drives, checked SMART values using smartctl (lifetime was around 2.5 years for all of them), ran some self tests (conveyance and long), read the entire surface, and I'm sure they're healthy.



    During data migration, I unplugged and plugged back in all drives several times. The Microserver advises against that with "non hot-swap" written on the drive bays, but I ignore this as it tends to work regardless.



    Once the migration was done and the dust had settled, I check the SMART values again. To my surprise, 2 of the 4 drives had their SMART values literally reset. All values were back to 0, and they're happily counting back up again (e.g. in the case of power on hours or start/stop count). Other than that, they seem to be working perfectly fine.



    How is this possible? If it had just been one drive, I would chalk it up to a random fluke. But two drives?



    Searching the 'tubes reveals no such occurences having happened before, and while certain Seagate drives apparently had, for a time, the ability to manually reset SMART, it always involved hooking up a serial interface to the extra pins next to the SATA connector and deliberately initiating the process.










    share|improve this question

























      1












      1








      1








      I have bought 4 used 6TB WD Red drives (WDC WD60EFRX-68MYMN1) for use in my HP Microserver Gen8. The server is running Debian Linux 9. The disk controller is using AHCI, no hardware RAID.



      Initially I tested all drives, checked SMART values using smartctl (lifetime was around 2.5 years for all of them), ran some self tests (conveyance and long), read the entire surface, and I'm sure they're healthy.



      During data migration, I unplugged and plugged back in all drives several times. The Microserver advises against that with "non hot-swap" written on the drive bays, but I ignore this as it tends to work regardless.



      Once the migration was done and the dust had settled, I check the SMART values again. To my surprise, 2 of the 4 drives had their SMART values literally reset. All values were back to 0, and they're happily counting back up again (e.g. in the case of power on hours or start/stop count). Other than that, they seem to be working perfectly fine.



      How is this possible? If it had just been one drive, I would chalk it up to a random fluke. But two drives?



      Searching the 'tubes reveals no such occurences having happened before, and while certain Seagate drives apparently had, for a time, the ability to manually reset SMART, it always involved hooking up a serial interface to the extra pins next to the SATA connector and deliberately initiating the process.










      share|improve this question














      I have bought 4 used 6TB WD Red drives (WDC WD60EFRX-68MYMN1) for use in my HP Microserver Gen8. The server is running Debian Linux 9. The disk controller is using AHCI, no hardware RAID.



      Initially I tested all drives, checked SMART values using smartctl (lifetime was around 2.5 years for all of them), ran some self tests (conveyance and long), read the entire surface, and I'm sure they're healthy.



      During data migration, I unplugged and plugged back in all drives several times. The Microserver advises against that with "non hot-swap" written on the drive bays, but I ignore this as it tends to work regardless.



      Once the migration was done and the dust had settled, I check the SMART values again. To my surprise, 2 of the 4 drives had their SMART values literally reset. All values were back to 0, and they're happily counting back up again (e.g. in the case of power on hours or start/stop count). Other than that, they seem to be working perfectly fine.



      How is this possible? If it had just been one drive, I would chalk it up to a random fluke. But two drives?



      Searching the 'tubes reveals no such occurences having happened before, and while certain Seagate drives apparently had, for a time, the ability to manually reset SMART, it always involved hooking up a serial interface to the extra pins next to the SATA connector and deliberately initiating the process.







      hard-drive smart






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Feb 16 at 22:24









      1N40011N4001

      62




      62






















          0






          active

          oldest

          votes












          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "3"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1406586%2fwd-red-smart-data-reset-itself%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Super User!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1406586%2fwd-red-smart-data-reset-itself%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Mouse cursor on multiple screens with different PPI

          Agildo Ribeiro

          Sometime when accessing a menu: “Ubuntu 16.04 has experienced an internal error”