From owner-freebsd-questions Tue Apr 10 14:39:44 2001 Delivered-To: freebsd-questions@freebsd.org Received: from guru.mired.org (okc-65-26-235-186.mmcable.com [65.26.235.186]) by hub.freebsd.org (Postfix) with SMTP id 23AFE37B422 for ; Tue, 10 Apr 2001 14:39:41 -0700 (PDT) (envelope-from mwm@mired.org) Received: (qmail 42749 invoked by uid 100); 10 Apr 2001 21:39:39 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15059.32155.948821.511055@guru.mired.org> Date: Tue, 10 Apr 2001 16:39:39 -0500 To: David Dooley Cc: questions@freebsd.org Subject: Re: Putting a UFS filesystem in a JAZ Disk In-Reply-To: <75982640@toto.iv> X-Mailer: VM 6.90 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Dooley types: > --==_Exmh_-462485028P > Content-Type: text/plain; charset=us-ascii > > The subject said it all really. > > I am trying to format a 2GB JAZ disk with a UFS filesystem. I can > label and partition the disk, I only want a single c partition, but > when I come to newfs'ing the disk I get an error and the system locks > up solid, I can get in via the network, but it takes between 2 and 3 > mins for a telnet prompt to appear or for my shell prompt to appear > if I use ssh, then it generates an error and every thing appears to > be ok once again. I have tried to do this on 3 different disks that > all work flawlessly under WinDose. > > I apologise for not having the actual error message to hand. > > The procedure I followed was to run /stand/sysinstall > > select 'Configure' > select 'Fdisk' and select 'da2' > select 'Label' and create a single label for partition c > > Exit from sysinstall > > I ran disklabel -r da2 and saw the correct label so went on to > > run 'newfs /dev/da2c' and at this point every thing hangs. I've been using a 1GB JAZ drive exactly that way for over two years with no problems, and everything you've described looks ok from the software side. This makes me think the problem is elsewhere. In particular, if your JAZ drive is SCSI and was recently added, the failure under heavy activity could be caused by problem with the SCSI subsystem. However, without real error messages, this is a shot in the dark. http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message