Path: utzoo!attcan!uunet!zephyr.ens.tek.com!tektronix!percy!nerd
From: nerd@percy.uucp (Michael Galassi)
Newsgroups: comp.sys.next
Subject: Re: Connecting a disk
Message-ID: <1990Dec13.051854.13587@percy.uucp>
Date: 13 Dec 90 05:18:54 GMT
References: <13687@uswat.UUCP>
Distribution: comp.sys.next
Organization: Percy's UNIX, Portland, OR.
Lines: 31

In article <13687@uswat.UUCP> hern@uswat.uswest.com (Steve Herndon) writes:
>...  I've connected a 100MB Rodime drive to the internal
>connectors and run scsimodes with the following results:

> Drive type: Rodime RO3000T
>  0 bytes per sector
>  0 sectors per track
>  0 tracks per cylinder
>  0 cylinder per volume
>  0 spare sectors per cylinder
>  0 alternate tracks per volume
>  0 useable sectors on volume

My first guess is that you are passing the block device to scsimodes,
if this is the case try the character device instead.  i.e. /dev/rsdXa
rather than /dev/sdXa (where X is the device id you have set the drive
to).  I ran into the same problem and could have kicked myself after
having done a low level format on another machine 4 times.  :-(

>...  Builddisk gets to the mkfs stage and then dies with
>an error number that is always sa-1.  That is, if I set the partition size to
>100000, mkfs says it failed with error 99999.  If I set sa to 1000, mkfs dies
>with error 999, etc.

The error #returned is the block # on which the mkfs failed.
I hope I've been of help, if not, I hope I haven't wasted too much of
your time.
-- 
      Michael Galassi    | If my opinions happen to be the same as
...!tektronix!percy!nerd | my employer's it is ONLY a coincidence,
...!sun!nosun!percy!nerd | of course coincidences OFTEN DO happen.