From owner-freebsd-scsi Sun Mar 1 07:56:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA28207 for freebsd-scsi-outgoing; Sun, 1 Mar 1998 07:56:53 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA28182 for ; Sun, 1 Mar 1998 07:56:50 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: by uni4nn.gn.iaf.nl with UUCP id AA10536 (5.67b/IDA-1.5 for scsi@FreeBSD.ORG); Sun, 1 Mar 1998 16:56:38 +0100 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.7/8.6.12) id OAA04743; Sun, 1 Mar 1998 14:15:28 +0100 (MET) From: Wilko Bulte Message-Id: <199803011315.OAA04743@yedi.iaf.nl> Subject: Re: timeout when formatting 9GB Barracuda, scsi errors is missing time In-Reply-To: <19980301125933.11291@klemm.gtn.com> from Andreas Klemm at "Mar 1, 98 12:59:33 pm" To: andreas@klemm.gtn.com (Andreas Klemm) Date: Sun, 1 Mar 1998 14:15:28 +0100 (MET) Cc: scsi@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL32 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Andreas Klemm wrote... > Hi ! > > Encountered two problems with -current, which might be in -STABLE > as well: > > a) scsiformat returned an timeout, when I formatted a Seagate > Barracuda. I don't know exactly, but it lasts a very long > time to preformat this beast. > Using scsiformat I wasn't able to preformat it. > I had to use Adaptecs scsiformat tool from DOS. It think you need to change: # formatting may take a huge amount of time, set timeout to 2 hours echo "Formatting... this may take a while." scsi -s 7200 -f $RAW -c "4 0 0 0 0 0" in the scsiformat script. 7200 is too low for big disks. > b) Tonight the Barracuda got some things to do, a make release ... > > sd3: RECOVERED ERROR info:0x3900a7 asc:17,2 Recovered data with positive head offset field replaceable unit: ea sks:80,c > , retries:4 > sd3: RECOVERED ERROR info:0x3900a7 asc:17,2 Recovered data with positive head offset field replaceable unit: ea sks:80,c > , retries:3 > sd3: RECOVERED ERROR info:0x3900a7 asc:17,2 Recovered data with positive head offset field replaceable unit: ea sks:80,c > , retries:2 > What's the exact meaning of these messages ? I think the harddisk > has discovered a bad sector or such and repaired it ... Or what > do you think ? What is asc: 17,2 ??? Guessing mode: maybe the drive has trackfollowing errors and is trying to go slightly off-track to get better signals on it's heads. ASC: additional sense code The 17,2 reads in the scsi spec as: Recovered data with positive head offset Great huh? ;-) > And here a suggestion from me ... would it be possible, that such > SCSI messages get a "date stamp" ?! Might be very useful, but not only for SCSI messages I suppose. W/ _ ______________________________________________________________________ | / o / / _ Bulte email: wilko @ yedi.iaf.nl http://www.tcja.nl/~wilko |/|/ / / /( (_) Arnhem, The Netherlands - Do, or do not. There is no 'try' --------------- Support your local daemons: run [Free,Net,Open]BSD Unix -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message