Re: How to fix Current_Pending_Sector?

["Stefan /*St0fF*/ Hübner" <stefan.huebner@stud.tu-ilmenau.de>]

Hi Greg,

Am 18.03.2010 22:47, schrieb Greg Freemyer:
> On Thu, Mar 18, 2010 at 3:37 PM, David Rees <drees76@gmail.com> wrote:
>> On Mon, Mar 15, 2010 at 4:20 AM, Iain Rauch
>> <groups@email.iain.rauch.co.uk> wrote:
>>> The 'Current_Pending_Sector' was still 1, so I dd zero onto the whole drive.
>>> I guess I could have just done part of it, but I suppose that verified the
>>> whole drive 'works'. It only took ~5 hours. Funnily enough this did fix the
>>> Current_pending_sectors count back to zero. Still no error reports in the
>>> SMART data, and 'Reallocated_Event_Count' didn't go up - shouldn't that have
>>> gone up to one?
>>
>> No - the drive was able to successfully write to the sector it was
>> unable to read from.  If the write had failed, it would have
>> reallocated the sector.
>>
>> -Dave
> 
> Dave,
> 
> Most sector writes are blind (ie. non-verified).

That is certainly right!

> 
> Is your theory that if the sector is marked as a Pending_Bad_Sector a
> write is done, but it is verified, and a reallocate only occurs if the
> verify fails?

If the drives has noted errorneous behaviour on a sector (i.e. marked it
pending), it will try to resolve the problem by verify.  It just only
makes sense that way, doesn't it?
> 
> I've never heard that theory, but it makes great sense.

IC, it does ;)
> 
> Greg

Stefan