From owner-freebsd-questions  Sat Jan 25 18:42:31 1997
Return-Path: <owner-questions>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id SAA10882
          for questions-outgoing; Sat, 25 Jan 1997 18:42:31 -0800 (PST)
Received: from whqvax.picker.com (whqvax.picker.com [144.54.1.1])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id SAA10877
          for <questions@freebsd.org>; Sat, 25 Jan 1997 18:42:29 -0800 (PST)
Received: from ct.picker.com by whqvax.picker.com with SMTP;
          Sat, 25 Jan 1997 21:41:13 -0500 (EST)
Received: from elmer.ct.picker.com ([144.54.57.34]) by ct.picker.com (4.1/SMI-4.1)
	id AA26010; Sat, 25 Jan 97 21:41:12 EST
Received: by elmer.ct.picker.com (SMI-8.6/SMI-SVR4)
	id VAA19276; Sat, 25 Jan 1997 21:39:30 -0500
Message-Id: <19970125213930.UI18083@ct.picker.com>
Date: Sat, 25 Jan 1997 21:39:30 -0500
From: rhh@ct.picker.com (Randall Hopper)
To: richardl@Adobe.COM (Richard Levenberg)
Cc: questions@freebsd.org
Subject: Re: SCSI ZIP drive woes
References: <3.0.32.19970124091242.007b0ea0@elroy>
X-Mailer: Mutt 0.59
Mime-Version: 1.0
In-Reply-To: <3.0.32.19970124091242.007b0ea0@elroy>; from Richard Levenberg on Jan 24, 1997 09:12:43 -0800
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Richard Levenberg:
 |I have a SCSI IoMega ZIP drive.  I am trying to put a file system on it and
 |am having trouble.
 |
 |I have an NCR SCSI controller which sees the ZIP and gives the standard
 |error that everyone is getting and which I am not worrying about. The
 |identification string says IOMEGA ZIP 100 D.08. I formatted the disk in
 |WIN95 and booted FreeBSD 3.0-970118-SNAP.  Ran FDISK and changed the sysid
 |to 165.
 |
 |I have a disktab entry of:
 |
 |zip100|Iomega Zip 100: \
 |        :ty=winchester:dt=SCSI:se#512:nt#64:ns#32:nc#96:rm#3600:\
 |        :pa#196576:oa#0:ba#4096:fa#512:ta=4.2BSD: \
 |        :pc#196576:oc#0:

I'm using the same disktab entry on an NCR-SC200 with a SCSI ZIP on
2.2-ALPHA.  I don't know enough about disklabel and newfs to know for
certain what's wrong with your procedure, though I'd hazard a guess it's
because you're newfsing on the block and not the character (raw) slice
device.  Let me just list what I'm doing that works for me:

I also create my UFSs in compatibility slices, though I put mine on slice 1
instead of slice 4.  Here's what I'm using:


 |        disklabel -w -r /dev/sd0s4 zip100
 |                                ^^<-- this is from fdisk

          disklabel -w -B /dev/sd0s1 zip100

 |        newfs -Tzip100 /dev/sd0s4

          newfs -Tzip100 /dev/rsd0s1

If you want to get a little more space for your UFS, you can dedicate the
disk to the UFS (i.e. not work within within compatibility slices).  Here's
the procedure posted by Bruce Evens, expanded for use with sd0:

        dd if=/dev/zero of=/dev/rsd0 count=2
        disklabel /dev/rsd0 | disklabel -B -R -r sd0 /dev/stdin
        newfs /dev/rsd0c
        mount /dev/sd0c /mnt

Randall Hopper