|
From: Christian F. <Chr...@t-...> - 2013-06-30 12:42:50
|
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 |