HDD ERRORS..... is this bad??


Recommended Posts

FRANK login: root

Linux 2.6.32.9-unRAID.

root@FRANK:~# cd /boot

root@FRANK:/boot# screen

-bash: screen: command not found

root@FRANK:/boot# screen

========================================================================1.11

==  SAMSUNG HD103SI    S1XGJ9BS804578

== Disk /dev/sdb has been successfully precleared

== with a starting sector of 63

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

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

                ATTRIBUTE  NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE

      Raw_Read_Error_Rate =    99      95          51        In_the_past 6417

    Read_Soft_Error_Rate =    99      95            0        ok          6269

  Airflow_Temperature_Cel =    76      75            0        ok          24

      Temperature_Celsius =    77      73            0        ok          23

  Current_Pending_Sector =  100      99            0        ok          0

No SMART attributes are FAILING_NOW

 

34 sectors were pending re-allocation before the start of the preclear.

37 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,

    a change of -34 in the number of sectors pending re-allocation.

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.

root@FRANK:/boot#

 

Link to comment

Looks like the disk had some pending sectors when the preclear started, but during the preclear the pending sectors were put back in service.  This may sound bad, but experience in the forums is that this happens sometimes, and does not indicate that the drive is bad.  You could run another preclear cycle and look for signs of reallocated sector activity.  If there is none, it would give added confidence that the drive is okay.

 

I am not as sure about the raw_read_error_rate.  It is indicating that the value failed at some point in the past, although at the current time it is at an acceptable value.  If this didn't recur maybe all is okay, but I would not be happy with this drive personally, and would be looking to RMA it, esp it if is brand new.  If it is used and you are looking at getting a refurb in exchange, I would not be as quick to return a disk with a minor problem.  But in this case, I'd likely return it.  If if failed in the past you deserve a new disk.  If nothing else, on resale this would significantly lower the marketability of the drive.

 

BTW, the drive will NEVER forget that this value failed at some point in the past.

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.