From owner-freebsd-scsi Mon Mar 2 15:24:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA13734 for freebsd-scsi-outgoing; Mon, 2 Mar 1998 15:24:02 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA13678 for ; Mon, 2 Mar 1998 15:23:53 -0800 (PST) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id RAA12463; Mon, 2 Mar 1998 17:23:50 -0600 (CST) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id RAA20620; Mon, 2 Mar 1998 17:23:50 -0600 (CST) Message-ID: <19980302172350.11640@mcs.net> Date: Mon, 2 Mar 1998 17:23:50 -0600 From: Karl Denninger To: David Kelly Cc: scsi@FreeBSD.ORG Subject: Re: SCSI low level format, good or bad References: <199803021206.GAA26129@nospam.hiwaay.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <199803021206.GAA26129@nospam.hiwaay.net>; from David Kelly on Mon, Mar 02, 1998 at 06:06:27AM -0600 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Mar 02, 1998 at 06:06:27AM -0600, David Kelly wrote: > Karl Denninger writes: > > > > I've seen a non-trivial number of disks come off the factory line with > > non-optimal formats. I don't know if its a temperature tolerance thing or > > what, but this has been my experience. > > What do you consider a non-optimal format? One which generates errors after short periods of being online (small numbers of unrecoverable block errors), among other things. Then there is the entire mode page issue. > Does Adaptec's low level format mess with the SCSI mode pages? If so, > reformatting might "optimize" the disk. I've observed the default for > WCE and other options varies according to where the disk came from, not > by manufacturer. Yes. I have a rather old utility which works with Adaptec SCSI host adapters which can change most of the mode pages that are "interesting". Its not perfect, but it works for a lot of stuff that otherwise is "immutable" without a lot of screwing around. > I stick by the "if it ain't broke, don't fix it" reasoning. There is no > telling exactly how they format the drive at the factory. No telling > what additional hardware monitors are attached to the drive. You'll > notice most all drives have additional connectors and test points for > *something*. > > In fact there is no telling exactly what happens when you "low level" > format the drive yourself. With any luck it will take the factory defect > list (not block list, but lowest level bit error position from index, > remember MFM and RLL disks?) as gospel and try to arrange blocks around > that. The problem appears, in many cases, to be temperature tolerance. This is why its very, very important to run a drive in the final enclosure with all covers, etc in place for a couple of hours before you try to low-level format it. I know that with today's positioners and such this is never supposed to be necessary. Tell that to the disks that I've had to format, but once doing so have run for *years* without a single block error. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly to FULL DS-3 Service | NEW! K56Flex support on ALL modems Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message