From owner-freebsd-scsi Tue Sep 14 23:47:19 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 1EB3914CE4 for ; Tue, 14 Sep 1999 23:47:16 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id AAA40575; Wed, 15 Sep 1999 00:47:14 -0600 (MDT) (envelope-from ken) Message-Id: <199909150647.AAA40575@panzer.kdm.org> Subject: Re: Reformatting a 520-byte-per-sector drive In-Reply-To: <37DF402B.BEA5086E@airnet.net> from Kris Kirby at "Sep 15, 1999 01:43:55 am" To: kris@airnet.net (Kris Kirby) Date: Wed, 15 Sep 1999 00:47:14 -0600 (MDT) Cc: scsi@freebsd.org From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (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 Kris Kirby wrote... > Kenneth D. Merry wrote: > > > As of now, it is running this command. Until the machine hangs... (I > > > have a bad widdle 1542CF. But three good 1542Bs. Well, the CF is the > > > only one with a BIOS more intelligent than mud. :-) > > > > I'm not sure I understand. Is the drive doing anything? Does the > > machine/card normally hang? > > This card will crash any machine. It's known to be broken, but it gets > the job done sometimes. I usually just use a 1542B instead. It's less > painful. Mind, I'm not saying _all_ 1542CF's are broken, just the one I > have in my possession. Hmm, that's strange indeed. > > I would expect the blocksize change to go pretty quickly, unless the drive > > automatically does a format or something similar when you change the > > blocksize. (With other drives, you change the blocksize and then format.) > > > > Can you tell if the drive is doing anything? > > It doesn't have a led output, so no. I can hear what I think is > accessing, but it may just be the bearings. That's a good sign. > > The other problem you may have with this is that if the drive does format > > itself when you change the blocksize, the timeout for the mode select is > > likely too short. In fact, the default timeout for generic SCSI commands > > like the one you issued is 5 seconds, which is way too short for a format. > > I'm chasing them on the command line ; one right after the other. > (That's not _just_ a grammatical > example!) So, like the energizer bunny, it keeps right on going, > formatting. Ahh, okay. I thought that the mode select was hanging somehow. But, of course, the format should take a while. I'm curious to see whether the sector size change will stick after the format. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message