Re: [smartmontools-support] strange error

[Milos R. <mil...@dc...>]

Good point.

Yes this is very important
including "seek" option is must under the solution a)

:)

Anyway this means that smart tools can make wrong judgement about sector 
state under some conditions.
May be it would be good to implement an option to be able to somehow 
force reset log in such situations instead of doing any writing to 
sectors which can be somehow dangerous.

Thanks for note.

Milos Rajsic
Business Development Director
Dynamic Communications Group
Cara Nikolaja II 90
11000 Beograd, Serbia
Tel: +381 11 3515122
Fax: +381 11 3515122
Mob: +381 63 267589
E-mail: mil...@dc...
http://www.dcg.rs
http://www.belre.org

On 06/30/2013 02:42 PM, Christian Franke wrote:
> Milos Rajsic wrote:
>> Thanks this looks logical
>> Since the disk is working in raid 1.
>>
>> Even the sector is readable I am thinking of two possible solutions:
>>
>> a) dd if=/dev/sda of=/dev/sdb count=1 bs=512 skip=502093169
>
> Don't forget to add 'seek=502093169', otherwise this would copy sector 
> 502093169 from sda to sector 0 of sdb :-)
>
>> b) remove from raid and then return to raid for synchronization
>
> Yes, this may help.
>
>
>> Somehow I am close to believe that only somekind of writing to that
>> sector will make changes in the smart log.
>
> In the past, I've seen a similar behavior with some Samsung F1 disk: 
> There were no actual read errors, but attribute 197 raw value reports 
> 40 sectors. Zero-filling the whole disk helped to clear the attribute.
>
> Thanks,
> Christian
>