From owner-freebsd-scsi Sat Oct 27 9:57:23 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from mout0.freenet.de (mout0.freenet.de [194.97.50.131]) by hub.freebsd.org (Postfix) with ESMTP id 51F5C37B406 for ; Sat, 27 Oct 2001 09:57:17 -0700 (PDT) Received: from [194.97.50.136] (helo=mx3.freenet.de) by mout0.freenet.de with esmtp (Exim 3.33 #1) id 15xWln-00079f-00; Sat, 27 Oct 2001 18:57:15 +0200 Received: from a34dd.pppool.de ([213.6.52.221] helo=Magelan.Leidinger.net) by mx3.freenet.de with esmtp (Exim 3.33 #3) id 15xWln-0000GL-00; Sat, 27 Oct 2001 18:57:15 +0200 Received: from Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.11.6/8.11.6) with ESMTP id f9RGxFr03949; Sat, 27 Oct 2001 18:59:16 +0200 (CEST) (envelope-from netchild@Leidinger.net) Message-Id: <200110271659.f9RGxFr03949@Magelan.Leidinger.net> Date: Sat, 27 Oct 2001 18:59:14 +0200 (CEST) From: Alexander Leidinger Subject: Re: repeating medium errors and error from "camcontrol defects" To: ken@kdm.org Cc: scsi@FreeBSD.ORG In-Reply-To: <20011026111106.A52864@panzer.kdm.org> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On 26 Okt, Kenneth D. Merry wrote: (Please keep me in the CC.) [...] >> What did I wrong with camcontrol and what can I do to get rid of those >> errors? Do I have to replace the disk or the cable? > > As someone else already suggested, you should try using the 'phys' defect > format, as many drives don't support the block format. Yes, this works. > As for the errors, they mean you have a bad block. Replacing the cable > won't really affect the problem. You may want to look into getting a new > drive, though, since medium errors typically indicate the drive is on its > way out. It shows 285 defects with -P and 0 with -G. I thougth I have to replace it, when the -G list grows too fast, and not already if it just shows one error. > To fix this particular bad block, what you should do is make sure read > and write reallocation are turned on in mode page 1: > > camcontrol modepage da0 -m 1 -e -P 3 > > will allow you to edit the saved parameters and enable read and write > reallocation. Already turned on. > Then, write zeroes to the bad block to force the drive to remap it. Is there a way to determine the file which is affected? I didn't want just wrote zeros to it if I didn't know which file this affects. Maybe I'm able to replace the file from a backup after or before overwritting the block . Bye, Alexander. -- The best things in life are free, but the expensive ones are still worth a look. http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message