Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 20 Sep 2022 08:21:46 +0100
From:      Steve O'Hara-Smith <steve@sohara.org>
To:        questions@freebsd.org
Cc:        freebsd@dreamchaser.org
Subject:   Re: disk non-destructive bad-block write/fix?
Message-ID:  <20220920082146.b329d714666d44d960c764d1@sohara.org>
In-Reply-To: <d687eb29-a3fb-7d91-a2c6-c1e4e1dc7e31@dreamchaser.org>
References:  <d687eb29-a3fb-7d91-a2c6-c1e4e1dc7e31@dreamchaser.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 19 Sep 2022 21:40:42 -0600
Gary Aitken <freebsd@dreamchaser.org> wrote:

> 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

	Check cables - if it's not cables get a new disk. There is no point
in trying to use a disk that throws a lot of errors like that, but disks
are more reliable than cables.

-- 
Steve O'Hara-Smith <steve@sohara.org>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20220920082146.b329d714666d44d960c764d1>