Why does CrystalDiskInfo see my dying HDD as good?

Page 3 of 5 FirstFirst 12345 LastLast

  1. Posts : 1,223
    W10-Pro 22H2
       #21

    This report from Backblaze (8 years ago) says that error 187 is a reliable predictor of failure.
      My Computer


  2. Posts : 15,491
    Windows10
       #22

    mngerhold said:
    This report from Backblaze (8 years ago) says that error 187 is a reliable predictor of failure.
    Isn't a bit curious these old articles have never been properly checked out since?
      My Computer


  3. Posts : 7,607
    Windows 10 Home 20H2
    Thread Starter
       #23

    mngerhold said:
    This report from Backblaze (8 years ago) says that error 187 is a reliable predictor of failure.
    The same report was already quoted in post #1.
      My Computer


  4. Posts : 1,223
    W10-Pro 22H2
       #24

    Matthew Wai said:
    The same report was already quoted in post #1.
    oops! It does seem odd that there seems to be no recent news on this aspect.
      My Computer


  5. Posts : 15,491
    Windows10
       #25

    mngerhold said:
    oops! It does seem odd that there seems to be no recent news on this aspect.
    Frankly, it is all a bit of a moot point as HDDs are obsolescent technology.

    I gave up using HDDs since Windows 10 came out nearly 8 years ago as it soon became obvious W10 performed much better with SSDs.

    I only use them for data backups now and even then critical data is backed up elsewhere AS WELL (I use Onedrive).

    As an aside, there is now an app that requires an SSD - in particular Android for Window (WSA).

    I see this becoming a future trend.
      My Computer


  6. Posts : 7,607
    Windows 10 Home 20H2
    Thread Starter
       #26

    Why does CrystalDiskInfo see my dying HDD as good?-screenshot_select-area_20230202203543.png

    My PC just failed to boot into Windows. Linux is now running from the HDD in question.
    I have a backup of the BCD file.

    Why does CrystalDiskInfo see my dying HDD as good?-bcd.png
      My Computer


  7. Posts : 7,607
    Windows 10 Home 20H2
    Thread Starter
       #27

    cereberus said:
    All HDDs get some uncorrectable errors but things like CHKDSK mark those sections as such and OS knows not to write to them.
    Do you mean the disk will mark the "uncorrectable errors" sectors as unusable, and Windows will not write data onto those unusable sections?
      My Computer


  8. Posts : 41,475
    windows 10 professional version 1607 build 14393.969 64 bit
       #28

    0xc0000185 = I/O device error

    In the forums we see drives with excellent HD Sentinel / Crystal Disk scores that have failed.

    The scoring methods are proprietary.

    The above tests are primarily based on SMART which attempts to predict drive failure.

    How do I interpret SMART diagnostic utilities results? | Support Seagate US



    Drives that had been exposed to power outages may display excellent smart and may have failed using long generic or long drive self test.

    To best assess the status of a disk drive please use what Dell, HP, Lenovo, etc. use in their hardware diagnostics for warranty replacement:
    Long or short DST.

    SeaTools | Support Seagate US


    Sea Tools bootable:

    https://www.seagate.com/content/dam/...lsBootable.zip

    SeaTools Bootable | Seagate US
      My Computer


  9. Posts : 15,491
    Windows10
       #29

    Matthew Wai said:
    Do you mean the disk will mark the "uncorrectable errors" sectors as unusable, and Windows will not write data onto those unusable sections?
    Quote from a chkdsk description

    Chkdsk can also scan for bad sectors. Bad sectors come in two forms: soft bad sectors, that occur when data is written badly, and hard bad sectors that occur because of physical damage to the disk. Chkdsk attempts to fix these problems by repairing soft bad sectors and marking hard bad sectors so they won’t be used again.
      My Computer


  10. Posts : 7,607
    Windows 10 Home 20H2
    Thread Starter
       #30

    Chkdsk found no problems on the HDD.

    Code:
    Windows PowerShell
    Copyright (C) Microsoft Corporation. All rights reserved.
    
    Try the new cross-platform PowerShell https://aka.ms/pscore6
    
    PS C:\Windows\system32> CHKDSK C:
    The type of the file system is NTFS.
    Volume label is Windows 10.
    
    WARNING!  /F parameter not specified.
    Running CHKDSK in read-only mode.
    
    Stage 1: Examining basic file system structure ...
      292096 file records processed.
    File verification completed.
     Phase duration (File record verification): 13.00 seconds.
      6005 large file records processed.
     Phase duration (Orphan file record recovery): 0.00 milliseconds.
      0 bad file records processed.
     Phase duration (Bad file record checking): 1.17 milliseconds.
    
    Stage 2: Examining file name linkage ...
      1384 reparse records processed.
      422154 index entries processed.
    Index verification completed.
     Phase duration (Index verification): 1.40 minutes.
      0 unindexed files scanned.
     Phase duration (Orphan reconnection): 1.10 seconds.
      0 unindexed files recovered to lost and found.
     Phase duration (Orphan recovery to lost and found): 0.51 milliseconds.
      1384 reparse records processed.
     Phase duration (Reparse point and Object ID verification): 21.14 milliseconds.
    
    Stage 3: Examining security descriptors ...
    Security descriptor verification completed.
     Phase duration (Security descriptor verification): 89.18 milliseconds.
      65030 data files processed.
     Phase duration (Data attribute verification): 0.43 milliseconds.
    CHKDSK is verifying Usn Journal...
      14633288 USN bytes processed.
    Usn Journal verification completed.
     Phase duration (USN journal verification): 422.46 milliseconds.
    
    Windows has scanned the file system and found no problems.
    No further action is required.
    
      73819107 KB total disk space.
      24499872 KB in 202719 files.
        153144 KB in 65031 indexes.
             0 KB in bad sectors.
        379951 KB in use by the system.
         65536 KB occupied by the log file.
      48786140 KB available on disk.
    
          4096 bytes in each allocation unit.
      18454776 total allocation units on disk.
      12196535 allocation units available on disk.
    Total duration: 1.65 minutes (99162 ms).
    PS C:\Windows\system32>
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 05:42.
Find Us




Windows 10 Forums