Announcement

Collapse
No announcement yet.

SMART bad status not detected

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

  • Thomas
    replied
    Thanks you for the proposal but I have handled the case differently.
    So on I don't need a custom development.

    I may have detected a bug and will open another thread soon.

    Leave a comment:


  • David (PassMark)
    replied
    The next major release will be V7. We have just started work on it. There is no release date as yet, but definitely won't be in the next 4 months. We could do it as paid custom development if you want it sooner.

    what could we do for SMART statuses that can't be detected
    If the SMART status can't be detected (for example becuase the drive is in a hardware RAID set) then it won't be possible to take any action nor flag an error.

    Leave a comment:


  • Thomas
    replied
    Thanks a lot for your quick reply Ian.

    It is a major "missing feature" on my side actually.
    What does "the next major release" mean ?
    Build 1021 ??


    On another side, what could we do for SMART statuses that can't be detected on some computers ? (maybe I should open another topic for that..?)

    Leave a comment:


  • Ian (PassMark)
    replied
    Currently no. I will add this to the candidate feature list for the next major release of BurnInTest.

    Leave a comment:


  • Thomas
    started a topic SMART bad status not detected

    SMART bad status not detected

    Hello!

    I'm a BurnInTest Pro (always latest release) user.
    One computer is displaying a smart bad status at boot time but BurnInTest doesn't fail...

    I configured sripts including Processor/RAM/Network card/HDD tests on WinPE.
    "Log SMART errors" and "Log bad sector increase" are ticked in the Prefrences.
    File size is set to 0.02%, Block size at 4Kb.

    The hard drive is a Toshiba MK5055GSX (500Gb)

    Can read those few lines in the "Event log" tab:

    ******************
    DETAILED EVENT LOG
    ******************
    LOG NOTE: 2010-04-15 10:53:34, Status, PassMark BurnInTest V6.0 Pro 1020
    LOG NOTE: 2010-04-15 10:53:35, Status, Main Tests started
    LOG NOTE: 2010-04-15 10:53:36, CPU, Starting 32-bit SSE2 heat test 2
    LOG NOTE: 2010-04-15 10:53:36, CPU, Starting 32-bit SSE2 heat test 2
    LOG NOTE: 2010-04-15 10:53:38, Disk, Drive C: SMART attribute data
    LOG NOTE: 2010-04-15 10:53:38, Disk, Model TOSHIBA MK5055GSX, Serial# 79TCF5T4S
    LOG NOTE: 2010-04-15 10:53:38, Disk, Power on hours count: 1617
    LOG NOTE: 2010-04-15 10:53:38, Disk, Power cycle count: 622
    LOG NOTE: 2010-04-15 10:53:38, Disk, All other SMART attributes within thresholds.
    LOG NOTE: 2010-04-15 10:54:43, Disk, C, SMART Reallocated Sector Count start value: 1851, current value 1851
    LOG NOTE: 2010-04-15 10:55:55, Disk, C, SMART Reallocated Sector Count start value: 1851, current value 1851
    LOG NOTE: 2010-04-15 10:57:12, Disk, C, SMART Reallocated Sector Count start value: 1851, current value 1851
    LOG NOTE: 2010-04-15 10:58:27, Disk, C, SMART Reallocated Sector Count start value: 1851, current value 1851
    LOG NOTE: 2010-04-15 10:59:44, Disk, C, SMART Reallocated Sector Count start value: 1851, current value 1851
    LOG NOTE: 2010-04-15 11:00:56, Disk, C, SMART Reallocated Sector Count start value: 1851, current value 1851
    LOG NOTE: 2010-04-15 11:02:09, Disk, C, SMART Reallocated Sector Count start value: 1851, current value 1851
    LOG NOTE: 2010-04-15 11:03:22, Disk, C, SMART Reallocated Sector Count start value: 1851, current value 1851

    -> Is there any way to create a BurnInTest failure result even if the reallocated sectors don't increase ?


    Thank you for your support


    PS: I've done a 10min test w/ trace file detail level activity 1 and activity 2 if you're interested in...
    Last edited by Thomas; 04-15-2010, 09:42 AM.
Working...
X