| Newsgroups |
gmane.linux.utilities.smartmontools |
| Message-ID |
<[email protected]> |
Replies are inline.
> On 06/02/2014 02:28 PM, Alex Samorukov wrote:
>> This attribute will back to 0 after successful remap. This could happens
>> if write occur to the failing sector. And error log in your report also
>> showing that something bad was happening. I would recommend to run long
>> test on this drive.
>
> Just finished testing the entire drive with badblocks (read-only); no
> errors reported and no change to Reallocated_Sector_Ct,
> Reallocated_Event_Count, Current_Pending_Sector, or
> Offline_Uncorrectable.
>
A read-only test does NOT cause a remap. Only writes will cause a remap.
You will have to write to the sector in question. This does have the side
effect of destroying whatever data, if any, is already there. A
non-destructive write test by badblocks also won't cause a remap, since it
is by design non-destructive. If badblocks can't read the data to back it
up temporarily, it won't write to the sector.
If it's only one sector, I would suggest using hdparm (assuming you are on
Linux). That can write to a specific sector.
>>> Error 1 occurred at disk power-on lifetime: 6249 hours (260 days + 9
>>> hours)
>>> When the command that caused the error occurred, the device was
>>> active or idle.
>
>> 9 Power_On_Hours 0x0012 098 098 000 Old_age Always
>> - 15014
>
> Doesn't this indicate that the error occurred almost exactly 1 year
> ago?
A qualified yes. Remember that if the drive is powered off, that time
doesn't count. So it would be more accurate to say it occurred AT LEAST
almost a year ago.
>
> Thanks!
>
> --
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/NeoTech