understanding smart logs

Suvayu Ali fatkasuvayu+linux at gmail.com
Mon Aug 16 01:55:16 UTC 2010

Hi Robert,

On Sunday 15 August 2010 06:46 PM, Robert Nichols wrote:
> Your problem is the 172 sectors pending reallocation.  Those are sectors
> that are currently unreadable and will be reallocated to spare sectors
> the next time they are written.  The problem is that the drive has no
> way to know whether the current contents are important (part of some
> file, or file system metadata) or irrelevant (part of file system free
> space), so the drive_must_  continue to return an error on any attempted
> read of those sectors.
> The most straightforward way to recover is to back up all of the data
> now on the drive while making note of any files that have read errors,
> write zeros to the entire drive, then re-make the file system(s) and
> restore the data, hopefully having some other source for any important
> files that could not be read when backing up.

Thank you for the advise. I used the disk diagnostic tool provided by WD 
to check and fix errors on the disk. It seemed to reduce the 
Current_Pending_Sector count from 172 to 78. I will take up on your 
suggestion over the next weekend. Thanks a lot again.


Open source is the future. It sets us free.

More information about the users mailing list