Seek Error Rate question please.


Spuds

Recommended Posts

I'm very new to unRaid and have just finished preclearing (using the preclear plug-in) 3 6tb WD reds. 2 came back perfect but the third came back with some Seek Error Read info which I dont understand. Should I be concerned? I have express RMA for another 2 weeks on this drive so exchanging it shouldnt be a problem as long as this problem warrants an exchange, could this just be bad cable? maybe I can re do the test using a different cable, 56 hours to preclear though...... I appreciate any help I get, Thanks.

 

Also, am I finished with the preclear process or is there another step I should do before creating the array and starting a parity sync?

 

THANKS!

 

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

=                unRAID server Pre-Clear disk /dev/sdb

=              cycle 1 of 1, partition start on sector 1

= 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: 23C, Elapsed Time:  55:21:39

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

== WDCWD60EFRX

== Disk /dev/sdb has been successfully precleared

== with a starting sector of 1

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

** Changed attributes in files: /tmp/smart_start_sdb  /tmp/smart_finish_sdb

                ATTRIBUTE  NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE

          Seek_Error_Rate =  100    200            0        ok          0

      Temperature_Celsius =  129    126            0        ok          23

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.

 

Link to comment

Spuds,

 

Best to post your results in this thread here dedicated to the preclear results...

 

Sometimes takes a day or two before someone comments, but you may be able to find some more info on your issue by searching in that thread as well. 

 

trurl has a good link in his signature on how to best use the search function (It has some quirks)

 

Welcome to the forums.

 

EDIT: Here's the search post from trurl...

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.