tool for mapping away bad blocks on an external disk
Warren Block
wblock at wonkity.com
Wed Apr 20 15:29:25 UTC 2016
On Wed, 20 Apr 2016, Matthias Apitz wrote:
> El día Monday, April 18, 2016 a las 08:55:34AM +0200, Matthias Apitz escribió:
>
>>
>> Thanks for all the hints; I started last night with overwriting the full
>> disk with:
>>
>> # dd conv=noerror if=/dev/zero of=/dev/da0 bs=1m
>>
>> ...
>
> The dd ended as. I issued from time to time a kill -INFO to the dd to
> see its progress:
>
> # tail nohup.out
> ...
> 885016+0 records in
> 885016+0 records out
> 928006537216 bytes transferred in 35244.495687 secs (26330538 bytes/sec)
> 980612+0 records in
> 980612+0 records out
> 1028246208512 bytes transferred in 39028.251450 secs (26346202 bytes/sec)
> dd: /dev/da0: Input/output error
> 1154078+0 records in
> 1154077+0 records out
> 1210137444352 bytes transferred in 45969.382123 secs (26324858 bytes/sec)
>
> Does this mean I could use the first 1154077 blocks of 1m as partition,
> i.e. shrink it to this size and just ignore the rest?
Maybe. Best to check the SMART data, then run a long test and see if
the reallocated blocks have grown. Don't count on the SMART data saying
the drive is good to be trustworthy. The manufacturers usually have it
set so the drive is long past safe use by the time the SMART data
actually admits it.
More information about the freebsd-questions
mailing list