Jump to content

aspik

Members
  • Posts

    36
  • Joined

  • Last visited

Posts posted by aspik

  1. Hi,

    I want to replace a smaller disk with a new bigger one. To be sure that everything is OK I started a parity sync (write corrections to parity enabled). The parity sync finished with one error. I then started second run of parity check (also write corrections to parity enabled). After an approximately an hour one error was found/corrected. This second run of the parity check finished with just that one error.

    How can two parity checks result with one (same?) error?

    How can I find the root cause? 

    In the past I never had parity errors. Recently I moved the server to a new case, could it be a cable problem?

    Please find attached diagnostic logs.

     

    Thanks in advance for any help.

    fractal-diagnostics-20240423-2203.zip

  2. Hi Joe,

    Thank you for the latest check on my drivers.

    Now I have precleared my WD AV-GP 2TB disk and have a question about ATA Errors. I guess the smart attributes looks OK? There are no pending sectors to be re-allocated. 

    But the preclear start and finish reports have ATA Errors. As far I could find out, these are cable problems, right? Both Errors occurred on 159 day of use, the disk has currently power on of 408 days, which would mean that the errors occurred quite time ago (where the disk was used in my htpc).

    What I don’t understand is:

     

    SMART Error Log Version: 1
    ATA Error Count: 2
    CR = Command Register [HEX]
    FR = Features Register [HEX]
    SC = Sector Count Register [HEX]
    SN = Sector Number Register [HEX]
    CL = Cylinder Low Register [HEX]
    CH = Cylinder High Register [HEX]
    DH = Device/Head Register [HEX]
    DC = Device Command Register [HEX]
    ER = Error register [HEX]
    ST = Status register [HEX]
    Powered_Up_Time is measured from power on, and printed as
    DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
    SS=sec, and sss=millisec. It "wraps" after 49.710 days.
    
    Error 2 occurred at disk power-on lifetime: 3834 hours (159 days + 18 hours)
      When the command that caused the error occurred, the device was active or idle.
    
      After command completion occurred, registers were:
      ER ST SC SN CL CH DH
      -- -- -- -- -- -- --
      04 51 01 00 00 00 a0  Error: ABRT
      Commands leading to the command that caused the error were:
      CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
      -- -- -- -- -- -- -- --  ----------------  --------------------
      b0 d6 01 e0 4f c2 a0 00      00:22:17.056  SMART WRITE LOG
      ec 00 00 00 00 00 a0 00      00:22:17.054  IDENTIFY DEVICE
      ef 02 00 00 00 00 00 00      00:22:16.633  SET FEATURES [Enable write cache]
      ec 00 00 00 00 00 a0 00      00:22:16.630  IDENTIFY DEVICE
      b0 d6 01 e0 4f c2 a0 00      00:22:06.756  SMART WRITE LOG
    
    Error 1 occurred at disk power-on lifetime: 3834 hours (159 days + 18 hours)
      When the command that caused the error occurred, the device was active or idle.
    
      After command completion occurred, registers were:
      ER ST SC SN CL CH DH
      -- -- -- -- -- -- --
      04 51 01 00 00 00 a0  Error: ABRT
      Commands leading to the command that caused the error were:
      CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
      -- -- -- -- -- -- -- --  ----------------  --------------------
      b0 d6 01 e0 4f c2 a0 00      00:22:06.756  SMART WRITE LOG
      ec 00 00 00 00 00 a0 00      00:22:06.752  IDENTIFY DEVICE
      ef 02 00 00 00 00 00 00      00:22:06.722  SET FEATURES [Enable write cache]
      ec 00 00 00 00 00 a0 00      00:22:06.719  IDENTIFY DEVICE
      ec 00 00 00 00 00 a0 00      00:21:35.933  IDENTIFY DEVICE

     

    What does mean: Error: ABRT?

    Attached start, finish and rpt files. Thanks!

    WD_AV-GP_2TB.zip

  3. Hello everybody!

     

    I'm about to build my first unraid server based on Lian Li Q25 and SP X7SPA-HF-D525. Currently I have 4 HDDs preclear and wanted to share the results, so that the experts can tell me, if the disks are suitable for unRAID.

    Below the results for 2 old WD RE4-GP 2TB and 2 refurbished WD RED 3TB

     

    Drive1 WD RE4-GP 2TB

    ========================================================================1.14
    == invoked as: ./preclear_disk.sh -c 3 -r 65536 -w 65536 -b 2000 -A /dev/sde
    == WDCWD2002FYPS-01U1B1
    == Disk /dev/sde has been successfully precleared
    == with a starting sector of 64 
    == Ran 3 cycles
    ==
    == Using :Read block size = 65536 Bytes
    == Last Cycle's Pre Read Time  : 7:59:46 (69 MB/s)
    == Last Cycle's Zeroing time   : 6:17:28 (88 MB/s)
    == Last Cycle's Post Read Time : 16:52:26 (32 MB/s)
    == Last Cycle's Total Time     : 23:10:57
    ==
    == Total Elapsed Time 78:04:25
    ==
    == Disk Start Temperature: 30C
    ==
    == Current Disk Temperature: 33C, 
    ==
    ============================================================================
    ** Changed attributes in files: /tmp/smart_start_sde  /tmp/smart_finish_sde
                    ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
          Temperature_Celsius =   119     122            0        ok          33
    No SMART attributes are FAILING_NOW
    
    0 sectors were pending re-allocation before the start of the preclear.
    0 sectors were pending re-allocation after pre-read in cycle 1 of 3.
    0 sectors were pending re-allocation after zero of disk in cycle 1 of 3.
    0 sectors were pending re-allocation after post-read in cycle 1 of 3.
    0 sectors were pending re-allocation after zero of disk in cycle 2 of 3.
    0 sectors were pending re-allocation after post-read in cycle 2 of 3.
    0 sectors were pending re-allocation after zero of disk in cycle 3 of 3.
    0 sectors are pending re-allocation at the end of the preclear,
        the number of sectors pending re-allocation did not change.
    0 sectors had been re-allocated before the start of the preclear.
    0 sectors are re-allocated at the end of the preclear,
        the number of sectors re-allocated did not change. 

     

    Drive2 WD RE4-GP 2TB

    ========================================================================1.14
    == invoked as: ./preclear_disk.sh -c 3 -r 65536 -w 65536 -b 2000 -A /dev/sdd
    == WDCWD2002FYPS-01U1B1
    == Disk /dev/sdd has been successfully precleared
    == with a starting sector of 64 
    == Ran 3 cycles
    ==
    == Using :Read block size = 65536 Bytes
    == Last Cycle's Pre Read Time  : 8:01:11 (69 MB/s)
    == Last Cycle's Zeroing time   : 6:21:07 (87 MB/s)
    == Last Cycle's Post Read Time : 16:55:36 (32 MB/s)
    == Last Cycle's Total Time     : 23:17:46
    ==
    == Total Elapsed Time 78:12:19
    ==
    == Disk Start Temperature: 32C
    ==
    == Current Disk Temperature: 36C, 
    ==
    ============================================================================
    ** Changed attributes in files: /tmp/smart_start_sdd  /tmp/smart_finish_sdd
                    ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
          Temperature_Celsius =   116     120            0        ok          36
    No SMART attributes are FAILING_NOW
    
    0 sectors were pending re-allocation before the start of the preclear.
    0 sectors were pending re-allocation after pre-read in cycle 1 of 3.
    0 sectors were pending re-allocation after zero of disk in cycle 1 of 3.
    0 sectors were pending re-allocation after post-read in cycle 1 of 3.
    0 sectors were pending re-allocation after zero of disk in cycle 2 of 3.
    0 sectors were pending re-allocation after post-read in cycle 2 of 3.
    0 sectors were pending re-allocation after zero of disk in cycle 3 of 3.
    0 sectors are pending re-allocation at the end of the preclear,
        the number of sectors pending re-allocation did not change.
    0 sectors had been re-allocated before the start of the preclear.
    0 sectors are re-allocated at the end of the preclear,
        the number of sectors re-allocated did not change. 

     

    Drive3 WD RED 3TB

    ========================================================================1.14
    == invoked as: ./preclear_disk.sh -c 3 -r 65536 -w 65536 -b 2000 /dev/sdb
    == WDCWD30EFRX-68EUZN0
    == Disk /dev/sdb has been successfully precleared
    == with a starting sector of 1 
    == Ran 3 cycles
    ==
    == Using :Read block size = 65536 Bytes
    == Last Cycle's Pre Read Time  : 9:44:50 (85 MB/s)
    == Last Cycle's Zeroing time   : 7:07:01 (117 MB/s)
    == Last Cycle's Post Read Time : 19:00:28 (43 MB/s)
    == Last Cycle's Total Time     : 26:08:31
    ==
    == Total Elapsed Time 94:20:29
    ==
    == Disk Start Temperature: 24C
    ==
    == Current Disk Temperature: 26C, 
    ==
    ============================================================================
    ** Changed attributes in files: /tmp/smart_start_sdb  /tmp/smart_finish_sdb
                    ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
          Temperature_Celsius =   124     126            0        ok          26
    No SMART attributes are FAILING_NOW
    
    0 sectors were pending re-allocation before the start of the preclear.
    0 sectors were pending re-allocation after pre-read in cycle 1 of 3.
    0 sectors were pending re-allocation after zero of disk in cycle 1 of 3.
    0 sectors were pending re-allocation after post-read in cycle 1 of 3.
    0 sectors were pending re-allocation after zero of disk in cycle 2 of 3.
    0 sectors were pending re-allocation after post-read in cycle 2 of 3.
    0 sectors were pending re-allocation after zero of disk in cycle 3 of 3.
    0 sectors are pending re-allocation at the end of the preclear,
        the number of sectors pending re-allocation did not change.
    0 sectors had been re-allocated before the start of the preclear.
    0 sectors are re-allocated at the end of the preclear,
        the number of sectors re-allocated did not change.

     

    Drive4 WD RED 3TB

    ========================================================================1.14
    == invoked as: ./preclear_disk.sh -c 3 -r 65536 -w 65536 -b 2000 /dev/sdc
    == WDCWD30EFRX-68EUZN0
    == Disk /dev/sdc has been successfully precleared
    == with a starting sector of 1 
    == Ran 3 cycles
    ==
    == Using :Read block size = 65536 Bytes
    == Last Cycle's Pre Read Time  : 9:51:34 (84 MB/s)
    == Last Cycle's Zeroing time   : 7:17:55 (114 MB/s)
    == Last Cycle's Post Read Time : 19:01:48 (43 MB/s)
    == Last Cycle's Total Time     : 26:20:47
    ==
    == Total Elapsed Time 95:24:51
    ==
    == Disk Start Temperature: 25C
    ==
    == Current Disk Temperature: 28C, 
    ==
    ============================================================================
    ** Changed attributes in files: /tmp/smart_start_sdc  /tmp/smart_finish_sdc
                    ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
          Temperature_Celsius =   122     125            0        ok          28
    No SMART attributes are FAILING_NOW
    
    0 sectors were pending re-allocation before the start of the preclear.
    0 sectors were pending re-allocation after pre-read in cycle 1 of 3.
    0 sectors were pending re-allocation after zero of disk in cycle 1 of 3.
    0 sectors were pending re-allocation after post-read in cycle 1 of 3.
    0 sectors were pending re-allocation after zero of disk in cycle 2 of 3.
    0 sectors were pending re-allocation after post-read in cycle 2 of 3.
    0 sectors were pending re-allocation after zero of disk in cycle 3 of 3.
    0 sectors are pending re-allocation at the end of the preclear,
        the number of sectors pending re-allocation did not change.
    0 sectors had been re-allocated before the start of the preclear.
    0 sectors are re-allocated at the end of the preclear,
        the number of sectors re-allocated did not change.

     

    Attached are also the start/finish reports.

    Are the OK for unRAID?

    Thanks for your help!

    preclear_reports.zip

×
×
  • Create New...