I tried the other person's (sorry, can't remember your name) of
reformatting the Zip drive. That didn't work. I still get the same
error...

Yes, I am using SBC. I forgot to mention that :) ncrscsi really screws up
the EZ drive, including the newer kernels...

SBC is giving no errors at all, only fsck is...

Thanks!

Josh

On Thu, 8 May 1997, David A. Gatwood wrote:

> On Thu, 8 May 1997, Josh Hope wrote:
> 
> > I've created a NetBSD Usr partition on my Zip drive. I've Mkfs'd using 32
> > sectors/track and 64 tracks/cylinder (as according to the instructions).
> > 
> > When I boot single user and attempt to run fsck -p, I get the following
> > error:
> > 
> > /dev/rsd2a: CANNOT READ: BLK 16
> > /dev/rsd2a: UNEXPECTED INCONSISTENCY; RUN fsck_ffs MANUALLY.
> > 
> > So, I run fsck with no arguments. Following is output:
> > 
> > CANNOT READ: BLK16
> > CONTINUE? [yn] y
> > THE FOLLOWING DISK SECTORS COULD NOT BE READ: 20, 21, 22, 23, 24, 25, 26,
> > 27, 28, 29, 30, 31,
> > /dev/rsd2a: NOT LABELED AS A BSD FILE SYSTEM (unknown)
> 
> Are you using sbc or ncrscsi?  If ncrscsi, try sbc (I wouldn't try ncrscsi
> with ez135's anyway, tho).  Otherwise, is the sbc driver giving any sort
> of errors, like medium errors or anything, or is it just fsck that's
> giving errors?
> 
> 
> David
> 
>