Hello Everyone:
With the generous help from
John Deacon <star_at_star.ucl.ac.uk>
Stephen Dowdy <dowdy_at_cs.colorado.edu>
Alan Rollow <alan_at_nabeth.cxo.dec.com>
Fabio Bossi <fabio.bossi_at_jrc.it>,
I am able to make the Iomega zip drive work under DU 4.0. Here are the
steps involved:
1) connect the zip drive to external SCSI port, set SCSI id (#5), terminate
SCSI; (better do this when the machine is powered off :-) )
2) cd /dev; ./MAKEDEV rz13 (in my case with a DEC3000/400, add 8 to scsi
id for external connection)
3) John Deacon sent me a copy of his zip drive disklabel, and I put it
in a file (zipdrive.disklabel), then ran this:
disklabel -R -r rz13 zipdrive.disklabel /mdec/rzboot /mdec/bootrz
4) Now that the drive has a *label*, you can fine tune it to your like:
disklabel -re rz13
5) newfs /dev/rz13a (if you need a UFS); mount /dev/rz13a /mnt
From what I read in the replies, it is a new *feature* in DU 4.0 that
made life harder than it should be.
Thanks for your attention.
------------------------------------------
WU Wei, Supervisor of Scientific Computing
Physics Department, Washington University
St. Louis,MO 63130,USA wwu_at_thrym.wustl.edu
phone (1)314-935-4746 fax (1)314-935-6219
------------------------------------------
Attachment:
---------------------------------------------
# disklabel for zip drive, as provided by John Deacon
type: SCSI
disk: ZIP
label:
flags: removeable
bytes/sector: 512
sectors/track: 2048
tracks/cylinder: 1
sectors/cylinder: 2048
cylinders: 96
sectors/unit: 196608
rpm: 3600
# I doubt that zip box can spin at 3600rpm. Wu Wei
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0 # milliseconds
track-to-track seek: 0 # milliseconds
drivedata: 0
8 partitions:
# size offset fstype [fsize bsize cpg]
a: 196608 0 unused 1024 8192 # (Cyl. 0 - 95)
b: 0 0 unused 0 0 # (Cyl. 0 - -1)
c: 196608 0 4.2BSD 1024 8192 16 # (Cyl. 0 - 95)
d: 0 0 unused 0 0 # (Cyl. 0 - -1)
e: 0 0 unused 0 0 # (Cyl. 0 - -1)
f: 0 0 unused 0 0 # (Cyl. 0 - -1)
g: 0 0 unused 0 0 # (Cyl. 0 - -1)
h: 0 0 unused 0 0 # (Cyl. 0 - -1)
-------------------------------------------------------
Replies:
From: "Alan Rollow - Dr. File System's Home for Wayward Inodes."
<alan_at_nabeth.cxo.dec.com>
I have heard that V4.0 added what someone thought was feature
that it always ask the drive for its geometry information
even when a disktab entry is present. Previously it would
only go to the drive if no disktab entry was found. For
most drives this is fine, but the ZIP drive doesn't implement
the SCSI geometry mode pages. Thus, disklabel will fail to
get the geometry from the drive.
Please bring the problem to the attention of the CSC since
this isn't a feature. The work around would be to label
the drive on pre-V4.0 system.
**********************************
From: Stephen Dowdy <dowdy_at_cs.colorado.edu>
There's a bug (misfeature) in DU4.0's disklabel command. I haven't
officially reported it to DEC, so if you have support, please do. (at
least one person in DEC is aware of it since i emailed this list on it a
while back). Basically, DU4.0's disklabel will do a DEVGETGEOM ioctl call
to the device regardless of a 'disktab' entry that specifies geometry.
The only way i know of in DU4.0 to label the Jaz drive (it appears the Zip
also doesn't support Geometry mode pages, which you can determine in SCU
by doing a "show page" and see if the geometry mode page appears) is:
# grab yourself a disklabel template from your boot disk or anywhere
% cd /tmp
% disklabel -r rz0 > zip.label
# edit the template label to add the appropriate values. This should
# at least be to make the C partition the size of what you get from
# "scu -f /dev/rrz6c show capacity", and use that value for sectors/unit
# the rest of the fields can probably be wrong, or you can use whatever
# values Iomega supplied.
% vi zip.label
# now you can forcibly dump that label onto the zip media
% disklabel -R -r rz6 jaz.label rzboot bootrz
I've had to put bootblocks on (it complained if i didn't), but you may
find a way to not require bootblock info.
(it may also be possible to 'dd' a label onto the raw device, but i
haven't tried)
**********************************************
Fabio Bossi - ISIS CEC Ispra <fabio.bossi_at_jrc.it>
try first to use: disklabel -rw rz13 rzxx. If the disk drive is seen by
the HW
& contains a valid label it should work. (rzxx is the generic name for
hard-disk drives).
It is not enough in any case to modify /etc/disktab; I remember that I
had to
modify
/usr/sys/data/cam_data.c & re-generate the kernel to configure a disk
drive
not seen
by my system (obviously with the proper info supplied by the vendor of
the
disk itself).
Received on Wed Aug 07 1996 - 23:57:40 NZST