Date: Thu, 27 Feb 2014 15:07:15 +0100 From: Polytropon <freebsd@edvax.de> To: Matthias Apitz <guru@unixarea.de> Cc: freebsd-questions@freebsd.org Subject: Re: errors from external USB disk Message-ID: <20140227150715.e6aa0594.freebsd@edvax.de> In-Reply-To: <20140227115934.GA2006@La-Habana> References: <20140226121714.GA1532@tiny-r255948> <20140226145527.3cd8eb4b.freebsd@edvax.de> <20140227115934.GA2006@La-Habana>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 27 Feb 2014 12:59:34 +0100, Matthias Apitz wrote: > El d=EDa Wednesday, February 26, 2014 a las 02:55:27PM +0100, Polytropon = escribi=F3: >=20 > > On Wed, 26 Feb 2014 13:17:14 +0100, Matthias Apitz wrote: > > > Sometimes, after the dump finished, a re-read of the file to get the = MD5 > > > checksum results in errors and I was highly concerned about the integ= rity > > > of my dumps on this device. > >=20 > > What error? Can you post the error message and the command > > which caused it? >=20 > While copying big files from the failing disk to another with 'cp -Rp' > I saw: >=20 > Feb 23 18:48:07 La-Habana kernel: (da0:umass-sim0:0:0:0): READ(10). CDB: > 28 00 01 cf d9 cf 00 00 0e 00=20 > Feb 23 18:48:07 La-Habana kernel: (da0:umass-sim0:0:0:0): CAM status: > CCB request completed with an error > Feb 23 18:48:07 La-Habana kernel: (da0:umass-sim0:0:0:0): Retrying command So it's definitely a reading error here. > > > I bought another 2.5 TB disk and was able to copy all the files (arou= nd > > > 1TB) over, i.e. the device could now be owerwritte while testing. > > >=20 > > > What is the best way to run a test on the disk? I'm thinking in > > > something like reading/writing the block in place for many days > > > (it's around 1.5 TB). Any ideas? > >=20 > > You can start by looking at the S.M.A.R.T. data (sysutils/smartmontools > > and sysutils/smartcontrol), see "man smartctl" for "smartctl -a". > > This should help you to identify possible hardware errors. >=20 > I dis this already, but it does not show much: > [...]=20 > Error Counter logging not supported >=20 > Device does not support Self Test logging Sorry, I forgot to mention: SMART usually does not work over USB. Do you have the chance to attach the disk, probably a SATA drive, to a "native" SATA port and try again? --=20 Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140227150715.e6aa0594.freebsd>