CurrentPendingSector

Wed Jan 28 23:19:05 UTC 2015


===========================================================================
 Patrick DUPRÉ                                 | | email: pdupre at gmx.com
 Laboratoire de Physico-Chimie de l'Atmosphère | |
 Université du Littoral-Côte d'Opale           | |
 Tel.  (33)-(0)3 28 23 76 12                   | | Fax: 03 28 65 82 44
 189A, avenue Maurice Schumann                 | | 59140 Dunkerque, France
===========================================================================


> Sent: Wednesday, January 28, 2015 at 11:47 PM
> From: "Robert Nichols" <rnicholsNOSPAM at comcast.net>
> To: users at lists.fedoraproject.org
> Subject: Re: CurrentPendingSector
>
> On 01/28/2015 03:14 PM, Kevin Cummings wrote:
> > On 01/28/2015 04:06 PM, Patrick Dupre wrote:
> >> Hello,
> >>
> >> I get:
> >> Device: /dev/sdc [SAT], 1 Currently unreadable (pending) sectors
> >>
> >> How can I manage this issue?
> >
> > Buy a new disk drive?  Seriously, pending sectors are disk write errors
> > and the disk has run out of "extra" blocks to write/re-map them to.  The
> > error occurs later when you later attempt to read from them.  It is a
> > sign that the disk is is on its way out.
> 
> Quote from the FAQ at http://www.smartmontools.org/wiki/FAQ :
> 
>    "Normally when an uncorrectable sector is found, the disk puts this
>    onto a 'pending sector list' to indicate that it should be replaced
>    with a spare good sector. However this replacement won't take place
>    until either the disk can read the data on the bad sector, or is
>    instructed to write new data to that bad sector."
> 
> Pay attention to the "However ...".  First, if you can, look at the
> overall health of the drive by running "smartctl -A /dev/sdc".
> Attributes 5 (Reallocated_Sector_Ct) and 197 (Current_Pending_Sector)
> are of interest.  If the RAW_VALUE numbers for either of those is not
> small, it's time to replace the drive.
>
The result is:

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000b   100   100   016    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0005   122   122   054    Pre-fail  Offline      -       147
  3 Spin_Up_Time            0x0007   113   113   024    Pre-fail  Always       -       208 (Average 199)
  4 Start_Stop_Count        0x0012   100   100   000    Old_age   Always       -       1326
  5 Reallocated_Sector_Ct   0x0033   100   100   005    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000b   100   100   067    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0005   134   134   020    Pre-fail  Offline      -       33
  9 Power_On_Hours          0x0012   099   099   000    Old_age   Always       -       7046
 10 Spin_Retry_Count        0x0013   100   100   060    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       1326
192 Power-Off_Retract_Count 0x0032   099   099   000    Old_age   Always       -       1522
193 Load_Cycle_Count        0x0012   099   099   000    Old_age   Always       -       1522
194 Temperature_Celsius     0x0002   253   253   000    Old_age   Always       -       22 (Min/Max 9/39)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0022   100   100   000    Old_age   Always       -       1
198 Offline_Uncorrectable   0x0008   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x000a   200   200   000    Old_age   Always       -       0


> If those numbers _are_ small, the Bad Block HOWTO at
> http://smartmontools.sourceforge.net/badblockhowto.html has instructions
> for locating and fixing sectors that are pending reallocation.  If there
> are more than a handful of pending sectors, you probably won't want to
> go through that fairly tedious procedure for each one.  In that case you
> can back up all the data that is recoverable and simply overwrite the
> whole drive with zeros to get all those sectors reallocated.
> 
> If you continue to get new pending sectors or if the number of
> reallocated sectors continues to increase, then the drive should be
> replaced. SMART won't declare the drive as failing or near failing until
> it _has_used up nearly all its spare sectors, and by then it is long
> past the time it should have been replaced.
> 
> -- 
> Bob Nichols     "NOSPAM" is really part of my email address.
>                  Do NOT delete it.
> 
> -- 
> users mailing list
> users at lists.fedoraproject.org
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> Have a question? Ask away: http://ask.fedoraproject.org
>