From owner-freebsd-questions@FreeBSD.ORG Mon Nov 16 18:24:08 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B64A21065695 for ; Mon, 16 Nov 2009 18:24:08 +0000 (UTC) (envelope-from rsmith@xs4all.nl) Received: from smtp-vbr10.xs4all.nl (smtp-vbr10.xs4all.nl [194.109.24.30]) by mx1.freebsd.org (Postfix) with ESMTP id 64F658FC18 for ; Mon, 16 Nov 2009 18:24:07 +0000 (UTC) Received: from slackbox.xs4all.nl (slackbox.xs4all.nl [213.84.242.160]) by smtp-vbr10.xs4all.nl (8.13.8/8.13.8) with ESMTP id nAGINwog022392; Mon, 16 Nov 2009 19:23:58 +0100 (CET) (envelope-from rsmith@xs4all.nl) Received: by slackbox.xs4all.nl (Postfix, from userid 1001) id 45664BAC3; Mon, 16 Nov 2009 19:23:58 +0100 (CET) Date: Mon, 16 Nov 2009 19:23:58 +0100 From: Roland Smith To: "Ronald F. Guilmette" Message-ID: <20091116182358.GA95918@slackbox.xs4all.nl> References: <42307.1258330015@tristatelogic.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="bp/iNruPH9dso1Pn" Content-Disposition: inline In-Reply-To: <42307.1258330015@tristatelogic.com> X-GPG-Fingerprint: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 X-GPG-Key: http://www.xs4all.nl/~rsmith/pubkey.txt X-GPG-Notice: If this message is not signed, don't assume I sent it! User-Agent: Mutt/1.5.20 (2009-06-14) X-Virus-Scanned: by XS4ALL Virus Scanner Cc: freebsd-questions@freebsd.org Subject: Re: Bad Blocks... Should I RMA? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Nov 2009 18:24:08 -0000 --bp/iNruPH9dso1Pn Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Nov 15, 2009 at 04:06:55PM -0800, Ronald F. Guilmette wrote: >=20 > In one of my systems, I've got a Seagate SATA 500GB drive (ST3500320AS) > which is actually not very old... purchased 12/11/2008. > same single block. Here's the relevant lines from /var/log/messages: >=20 > Nov 15 15:24:17 coredump kernel: ad4: FAILURE - READ_DMA status=3D51 error=3D40 LBA=3D256230591 > Nov 15 15:24:43 coredump kernel: ad4: FAILURE - READ_DMA status=3D51 error=3D40 LBA=3D256230591 > Nov 15 15:24:46 coredump kernel: ad4: FAILURE - READ_DMA status=3D51 error=3D40 LBA=3D256230591 >=20 > (Don't be confused... The name of the host system here is "coredump"... my > lame attempt at humor.) Install the smartmontools port, and check the drive with=20 'smartctl -a /dev/ad4'. If you see a non-zero Reallocated_Sector_Ct, RMA it immediately, as it is about to fail. If see other errors reported, RMA it. (S)ATA disk have spare sectors available. If a sector fails, it is replaced= by one of the spares by the firmware. If you see a non-zero Reallocated_Sector_Ct, it means that the drive has run out of spares. This = is bad news. > P.S. If I _do_ end up RMA'ing the thing back, do I need to worry about > scrubing the drive squeaky clean first... you know... using one of these > multiple write-over progs (like `wipe') if I am paranoid... as I am... > about the possibility of old credit card numbers lying around in unalloca= ted > sectors on the drive? (The drive is empty _now_, but earlier it was in > serious/heavy use.) No. Just fill it with zeros. There was a paper presented at Usenix 1996 that you could potentially read erased data from the sidebands. But that was looking at disks make in the early nineties using MFM and RLL encoding. The encoding on todays disks is very different. The author of te original paper thinks it is almost impossible to recover overwritten data on a current harddisk. To quote from the epilogue from [http://www.cs.auckland.ac.nz/~pgut001/pubs/secure_del.html]: Any modern drive will most likely be a hopeless task, what with ultra-high densities and use of perpendicular recording... > I guess what I'm asking is: Do Segate and the other manufacturers care > enough about their customer's privacy to securely wipe old drives/platters > that come in to them for RMA? Or do I need to worry 'bout that for my own > self? I would always wipe them myself. You cannot guarantee that the manufacturer will do it. But I was under the impression that the information on a platter can only be properly read by the same arm/head it was written with. Roland --=20 R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) --bp/iNruPH9dso1Pn Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.13 (FreeBSD) iEYEARECAAYFAksBmL4ACgkQEnfvsMMhpyUZAQCfcswnMriwAplITWaMz0LzI22w jtsAnjnucdmrCoHeoM6/5ulkJoLyOz/A =dWDB -----END PGP SIGNATURE----- --bp/iNruPH9dso1Pn--