Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Interpreting Pre-Clear Results

Featured Replies

I just finished a pre-clear on an SSD.  Here's the report.  Is there a guide on how to interpret the results?  This one looks like it surfaced a few new errors, but not over a SMART threshold?

 

================================================================== 1.15

=                unRAID server Pre-Clear disk /dev/sdd

=              cycle 1 of 1, partition start on sector 64

= Disk Pre-Clear-Read completed                                DONE

= Step 1 of 10 - Copying zeros to first 2048k bytes            DONE

= Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE

= Step 3 of 10 - Disk is now cleared from MBR onward.          DONE

= Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4      DONE

= Step 5 of 10 - Clearing MBR code area                        DONE

= Step 6 of 10 - Setting MBR signature bytes                    DONE

= Step 7 of 10 - Setting partition 1 to precleared state        DONE

= Step 8 of 10 - Notifying kernel we changed the partitioning  DONE

= Step 9 of 10 - Creating the /dev/disk/by* entries            DONE

= Step 10 of 10 - Verifying if the MBR is cleared.              DONE

= Disk Post-Clear-Read completed                                DONE

Disk Temperature: 30C, Elapsed Time:  0:55:11

========================================================================1.15

== OCZ-AGILITY3  OCZ-2W4T6Y3445O71DAW

== Disk /dev/sdd has been successfully precleared

== with a starting sector of 64

============================================================================

** Changed attributes in files: /tmp/smart_start_sdd  /tmp/smart_finish_sdd

                ATTRIBUTE  NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE

      Raw_Read_Error_Rate =  118    120          50        ok          /179224189

  Power_On_Hours_and_Msec =    0      0            0        near_thresh 3845h+52m+48.240s

      Program_Fail_Count =    0      0            0        near_thresh 0

        Erase_Fail_Count =    0      0            0        near_thresh 0

  Unexpect_Power_Loss_Ct =    0      0            0        near_thresh 100

        Wear_Range_Delta =    0      0            0        near_thresh 0

      Program_Fail_Count =    0      0            0        near_thresh 0

        Erase_Fail_Count =    0      0            0        near_thresh 0

  ECC_Uncorr_Error_Count =  120    100            0        ok          /179224189

  Unc_Soft_Read_Err_Rate =  120    100            0        ok          /179224189

    Soft_ECC_Correct_Rate =  120    100            0        ok          /179224189

      SandForce_Internal =    0      0            0        near_thresh 499

      SandForce_Internal =    0      0            0        near_thresh 1209

      Lifetime_Writes_GiB =    0      0            0        near_thresh 1209

      Lifetime_Reads_GiB =    0      0            0        near_thresh 2813

No SMART attributes are FAILING_NOW

    the number of sectors pending re-allocation did not change.

    the number of sectors re-allocated did not change.

root@HunterNAS2:/usr/local/emhttp#

  • Community Expert

Known ATA S.M.A.R.T. attributes

 

The SMART attributes are much easier to read in a code block.

================================================================== 1.15
=                unRAID server Pre-Clear disk /dev/sdd
=               cycle 1 of 1, partition start on sector 64
= Disk Pre-Clear-Read completed                                 DONE
= Step 1 of 10 - Copying zeros to first 2048k bytes             DONE
= Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE
= Step 3 of 10 - Disk is now cleared from MBR onward.           DONE
= Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4       DONE
= Step 5 of 10 - Clearing MBR code area                         DONE
= Step 6 of 10 - Setting MBR signature bytes                    DONE
= Step 7 of 10 - Setting partition 1 to precleared state        DONE
= Step 8 of 10 - Notifying kernel we changed the partitioning   DONE
= Step 9 of 10 - Creating the /dev/disk/by* entries             DONE
= Step 10 of 10 - Verifying if the MBR is cleared.              DONE
= Disk Post-Clear-Read completed                                DONE
Disk Temperature: 30C, Elapsed Time:  0:55:11
========================================================================1.15
== OCZ-AGILITY3   OCZ-2W4T6Y3445O71DAW
== Disk /dev/sdd has been successfully precleared
== with a starting sector of 64
============================================================================
** Changed attributes in files: /tmp/smart_start_sdd  /tmp/smart_finish_sdd
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
      Raw_Read_Error_Rate =   118     120           50        ok          /179224189
  Power_On_Hours_and_Msec =     0       0            0        near_thresh 3845h+52m+48.240s
       Program_Fail_Count =     0       0            0        near_thresh 0
         Erase_Fail_Count =     0       0            0        near_thresh 0
   Unexpect_Power_Loss_Ct =     0       0            0        near_thresh 100
         Wear_Range_Delta =     0       0            0        near_thresh 0
       Program_Fail_Count =     0       0            0        near_thresh 0
         Erase_Fail_Count =     0       0            0        near_thresh 0
   ECC_Uncorr_Error_Count =   120     100            0        ok          /179224189
   Unc_Soft_Read_Err_Rate =   120     100            0        ok          /179224189
    Soft_ECC_Correct_Rate =   120     100            0        ok          /179224189
       SandForce_Internal =     0       0            0        near_thresh 499
       SandForce_Internal =     0       0            0        near_thresh 1209
      Lifetime_Writes_GiB =     0       0            0        near_thresh 1209
       Lifetime_Reads_GiB =     0       0            0        near_thresh 2813
No SMART attributes are FAILING_NOW
    the number of sectors pending re-allocation did not change.
    the number of sectors re-allocated did not change.
root@HunterNAS2:/usr/local/emhttp#[/quote]

These look OK but you should post the preclear_rpt file like this one I got recently for example

========================================================================1.15

== invoked as: /boot/config/plugins/preclear.disk/preclear_disk.sh -M 4 -o 7 -c 1 -f -J /dev/sdj

== WDCWD60EFRX-68MYMN1  WD-WXA1D65E3NPR

== Disk /dev/sdj has been successfully precleared

== with a starting sector of 1

== Ran 1 cycle

==

== Using :Read block size = 1000448 Bytes

== Last Cycle's Pre Read Time  : 15:00:58 (111 MB/s)

== Last Cycle's Zeroing time  : 12:06:53 (137 MB/s)

== Last Cycle's Post Read Time : 15:48:47 (105 MB/s)

== Last Cycle's Total Time    : 42:57:55

==

== Total Elapsed Time 42:57:55

==

== Disk Start Temperature: 19C

==

== Current Disk Temperature: 31C,

==

============================================================================

** Changed attributes in files: /tmp/smart_start_sdj  /tmp/smart_finish_sdj

                ATTRIBUTE  NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE

      Temperature_Celsius =  121    133            0        ok          31

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 1.

0 sectors were pending re-allocation after zero of disk in cycle 1 of 1.

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.

============================================================================

This one is a perfect score.

 

And you should post them in this sticky thread instead of starting a new topic.

  • Author

Right, unfortunately, there appears to be a hitch in getting this information - until you've started the array.  I'm not able to see the flash drive as a share until the array has been started.  I started the array, but then the disks are not available in preclear (because the array started).  I suppose I could start the array, then stop, do a new config, then only the flash drive should be active when I do the start array...  right?

  • Community Expert

Right, unfortunately, there appears to be a hitch in getting this information - until you've started the array.  I'm not able to see the flash drive as a share until the array has been started.  I started the array, but then the disks are not available in preclear (because the array started).  I suppose I could start the array, then stop, do a new config, then only the flash drive should be active when I do the start array...  right?

Don't know what you are talking about. The flash share is the only share that is available with the array stopped.
  • Community Expert

Right, unfortunately, there appears to be a hitch in getting this information - until you've started the array.  I'm not able to see the flash drive as a share until the array has been started.  I started the array, but then the disks are not available in preclear (because the array started).  I suppose I could start the array, then stop, do a new config, then only the flash drive should be active when I do the start array...  right?

Don't know what you are talking about. The flash share is the only share that is available with the array stopped.

Also, disks not in the array are available for preclear with the array started. The whole point of preclear is to allow you to continue to use your server while you clear a disk.
  • Author

Here's the report...not the same as yours...?

 

[code========================================================================1.15

== invoked as: /boot/config/plugins/preclear.disk/preclear_disk.sh -c 1 /dev/sdd

== OCZ-AGILITY3  OCZ-2W4T6Y3445O71DAW

== Disk /dev/sdd has been successfully precleared

== with a starting sector of 64

== Ran 1 cycle

==

== Using :Read block size = 1000448 Bytes

== Last Cycle's Pre Read Time  : 0:12:40 (315 MB/s)

== Last Cycle's Zeroing time  : 0:08:24 (476 MB/s)

== Last Cycle's Post Read Time : 0:33:07 (120 MB/s)

== Last Cycle's Total Time    : 0:55:11

==

== Total Elapsed Time 0:55:11

==

== Disk Start Temperature: 30C

==

== Current Disk Temperature: 30C,

==

============================================================================

** Changed attributes in files: /tmp/smart_start_sdd  /tmp/smart_finish_sdd

                ATTRIBUTE  NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE

      Raw_Read_Error_Rate =  118    120          50        ok          /179224189

  Power_On_Hours_and_Msec =    0      0            0        near_thresh 3845h+52m+48.240s

      Program_Fail_Count =    0      0            0        near_thresh 0

        Erase_Fail_Count =    0      0            0        near_thresh 0

  Unexpect_Power_Loss_Ct =    0      0            0        near_thresh 100

        Wear_Range_Delta =    0      0            0        near_thresh 0

      Program_Fail_Count =    0      0            0        near_thresh 0

        Erase_Fail_Count =    0      0            0        near_thresh 0

  ECC_Uncorr_Error_Count =  120    100            0        ok          /179224189

  Unc_Soft_Read_Err_Rate =  120    100            0        ok          /179224189

    Soft_ECC_Correct_Rate =  120    100            0        ok          /179224189

      SandForce_Internal =    0      0            0        near_thresh 499

      SandForce_Internal =    0      0            0        near_thresh 1209

      Lifetime_Writes_GiB =    0      0            0        near_thresh 1209

      Lifetime_Reads_GiB =    0      0            0        near_thresh 2813

No SMART attributes are FAILING_NOW

 

 

    the number of sectors pending re-allocation did not change.

    the number of sectors re-allocated did not change.

============================================================================

 

[/code][/code]

  • Author
Don't know what you are talking about. The flash share is the only share that is available with the array stopped.

 

Yeah, its weird.  I've got the server up and running, can access the GUI (IP address only!, not the server name), ran preclear on a couple disks using trial while I waited for the USB stick to arrive.  It came today, I purchased the key and installed.  I've setup Date and Time, Disk Settings, Identification, Network Settings,

Network Services (SMB), set the correct Workgroup, etc...

 

SMB Settings (both the same)

20151220-pjrb-9kb.jpg

 

SMB Workgroup - HunterNAS

20151220-36e5-9kb.jpg

SMB Workgroup - HunterNAS2

20151220-3zaw-9kb.jpg

 

The only difference is that HunterNAS2 has Local Master turned off.  Did I miss something?  I tried just typing the server name (//hunternas2) in windows explorer and it shows up, but DOES NOT show up in the Network panel.  So very odd...

 

20151220-bmdn-92kb.jpg

 

  • Author

Quick bump on this one, not seeing the new server through SMB services.

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.