Re: disk non-destructive bad-block write/fix?

From: David Christensen <dpchrist_at_holgerdanske.com>
Date: Tue, 20 Sep 2022 22:01:30 UTC
On 9/20/22 13:02, jin guojun wrote:
> On Tue, Sep 20, 2022 at 6:33 AM Christoph Brinkhaus <c.brinkhaus@t-online.de>
> wrote:
> 
>> Am Mon, Sep 19, 2022 at 09:40:42PM -0600 schrieb Gary Aitken:
>>
>> Hi Gary,
>>
>>> I have a system I need to back up and my only available backup disk is
>>> throwing a lot of errors like:
>>>
>>>     (da0:umass-sim0:0:0:0): WRITE(10). CDB: 2a 00 3c fd e5 68 00 00 40 00
>>>     (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an
>> error
>>>     (da0:umass-sim0:0:0:0): Retrying command
>>>     (da0:umass-sim0:0:0:0): WRITE(10). CDB: 2a 00 3c fd e6 68 00 00 20 00
>>>     (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an
>> error
>>
>> A different countermeasure could be to use an external power supply if
>> possible. I have a USB disk with does not work with the USB +5V supply
>> but performs well with an external +5V wall type supply.
>>
> 
> It also could be the USB controller. I have an older USB drive that works
> with many computers, but failed on a newer one. The newer computer usually
> has issues on its USB3 port, but later has issues on USB2 as well. The USB
> enclosure has an additional USB cable for getting power from the second USB
> port. Plugging in the second USB cable worked for some time, and the USB
> randomly spits out the above errors. The problem seems related to boot up.
> When this newer computer has USB issues, it will always have the issue till
> reboot.


USB HDD's are a problem.  I usually end up extracting the HDD and 
recycling the rest.  I can then test the drive and have confidence in 
the result.


David