From owner-freebsd-scsi Tue Oct 8 13:44:26 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8857137B401 for ; Tue, 8 Oct 2002 13:44:24 -0700 (PDT) Received: from mcomail01.maxtor.com (mcomail01.maxtor.com [134.6.76.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0351343E42 for ; Tue, 8 Oct 2002 13:44:24 -0700 (PDT) (envelope-from stephen_byan@maxtor.com) Received: from mcoexc03.mlm.maxtor.com (localhost.localdomain [127.0.0.1]) by mcomail01.maxtor.com (8.11.6/8.11.6) with ESMTP id g98KcC626163; Tue, 8 Oct 2002 14:38:12 -0600 Received: from mmans02.mma.maxtor.com ([134.6.232.101]) by mcoexc03.mlm.maxtor.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id T6WTLFJG; Tue, 8 Oct 2002 14:44:24 -0600 Received: from maxtor.com by mmans02.mma.maxtor.com (8.8.8/1.1.22.3/08May01-0432PM) id QAA0000018748; Tue, 8 Oct 2002 16:43:49 -0400 (EDT) Date: Tue, 8 Oct 2002 16:43:45 -0400 Subject: Re: SCSI bad block remapping doesn't work!?#@$ Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v546) Cc: freebsd-scsi@FreeBSD.ORG To: Gunther Schadow From: Steve Byan In-Reply-To: <3DA30E67.8000206@aurora.regenstrief.org> Message-Id: Content-Transfer-Encoding: 7bit X-Mailer: Apple Mail (2.546) 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 Tuesday, October 8, 2002, at 12:57 PM, Gunther Schadow wrote: > Hi, > > I can't seem to be able to make my SCSI disk map bad blocks. Can > someone > please look over my shoulder and see what I may be doing wrong? I have > > $ uname -a > FreeBSD ... 4.4-RELEASE FreeBSD 4.4-RELEASE ... i386 > > $ camcontrol inquiry da1 > pass1: Fixed Direct Access SCSI-2 device > pass1: Serial Number WS7010556513 > pass1: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing > Enabled > I don't recognize the ID string here. Is this by any chance a Quantum or Maxtor drive? If so, I will help you get to the bottom of this. I've forgotten the details, but if I recall correctly, Quantum and Maxtor drives need to see the hard read error multiple times, with the block being overwritten each time) before reallocating, since the most likely cause of hard read errors is a transient write error (off-track write or high-fly write) rather than a grown media defect. (If you do get a grown media defect, then it's most likely that there is particulate contamination in the drive, and it will quickly experience a cascade of failures.) From your description, it sounds like you have most likely met the drive's criteria for remapping the block. If it's not one of ours, I dunno. Regards, -Steve -------- Steve Byan Design Engineer Maxtor Corp. MS 1-3/E23 333 South Street Shrewsbury, MA 01545 (508) 770-3414 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message