Announcement

Collapse
No announcement yet.

"Smart Threshold exceding condition detected" erro

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • "Smart Threshold exceding condition detected" erro

    We use passmark Burn in 4.0 for testing 250g SATA Western digital drives and WD recently discontinued the SD model (WD2500SD) with YD models (WD2500YD) and we began getting numerous "Smart Threshold exceding condition detected" errors and subsequently a failure on the test. We thought maybe it was the 4.0 burn in software, since it is a few years old, so we purchased 5.0 version hoping that maybe 5.0 was more up to date with current hardware and would not fail the test. This was not the case, we still are getting the error.

    After using Passmark Diskcheckup utility we found an "BE (Unknown attribute)" that was failing the test.

    We called Western Digital and they said this is a known issue with the Burn in software: apparently "BE (Unknown attribute)" is an air flow sensor that Burn in is looking for that these drives dont have, so it fails the test.

    Is there a way to get Burn in to not look for this attribute during the SMART test? Maybe a setting or update to the software that resolves this?

    Otherwise we are going to continue to get failures on all of our Hard Drive testing.

    Thanks for your assistance,

    Mike

  • #2
    The Pass / Fail indication comes from the hard drive (and WD knows this).

    So WD are being disingenuous. Their drive shouldn't being reporting on a sensor that doesn't exist. If they do insist on reporting on non existent hardware, they should report a pass. Not a fail.

    On the other hand at least they were honest enough to actually tell you about the missing sensor. In the past they just ignore E-Mails.

    You can,

    1) Turn off the entire SMART threshold detection function in BurnInTest (from the preferences window). But you might also miss real errors.

    2) Reclassify the error in BurnInTest. This can be done by editing the BITErrorClassification.txt file in the BurnInTest install directory.

    ------
    David

    Comment


    • #3
      Thanks for the response. Hopefully Western Digital fixes the issue and we wont need to edit the Burn In software.


      Thanks

      Comment

      Working...
      X