Subject: Re: Booter won't recognize my drive...
To: David A. Gatwood <marsmail@globegate.utm.edu>
From: Capt. Avram Dorfman <dorfman@pentagon.mil>
List: port-mac68k
Date: 05/05/1998 18:25:19
I tried the SBC kernel, and it did the same thing as the ncr kernel, 
excep the message said "sbc0:2:0..." instead of "ncrscsi0:2:0...".

The cables are attached solid, and the active termination light is on on 
the drive, and it's the last device in the chain.

I had a major filesystem problem which is what started this all off. I 
had a crash into the debugger, complaining of an fs problem. Then I 
rebooted, and it made me run fsck, and fsck wanted to remove about 100 
files, including the kernel itself. I told it not to remvoe the files, 
but I let it fix everything else. It said I had to reboot, and rucn fsck 
again. So I did, and it didn't recognize the drive as a scsi device.

It does seem like we could be looking at a physical problem on the disk, 
but I'm not quite sure how an fsck could cause a scsi device to fail to 
be recognized. Also, it just really seems that since I can mount this 
device in the installer, I ought to be able to somehow get to it w/in 
netbsd. Then I could at least recover it onto another disk. The 
installer's capabilities are a little too weak to be recovering hundreds 
of files.

-Capt Avram Dorfman
Chief, Network Operations
email: dorfman@pentagon.mil
(last resort email: avram@pobox.com)

:%s/\(do|-<\)/\1\1/g
:1,$d

On Tue, 5 May 1998, David A. Gatwood wrote:

> On Mon, 4 May 1998 18:23:00 -0400 (EDT),
> "Capt. Avram Dorfman" <dorfman@pentagon.mil> wrote:
> > 
> >    probe(ncrscsi0:2:0): Medium error, data - 00 00 00 00 82 00 00 00 00
> 
> Is this referring to the ncrscsi driver?  I'm a bit confused about why a
> message about ncrscsi would pop up in the booter....  I'll assume for the
> moment that either this is a message from the kernel rather than the
> booter, or that this the booter is calling code in the kernel for whatever
> reason.
> 
> This could be a read/write error, but it could also probably be either a
> driver bug or a SCSI termination problem.  Besides checking your
> termination, you might also try an sbc kernel.
> 
> 
> David
> 
> -----BEGIN GEEK CODE BLOCK-----
> Version: 3.1
> GCS/CC/FA/H/L/MC/M/MU/PA/TW d-@ s:>- a-- C++++>$ UBLAS*++++>$
> P+?>$ L+++>$ !E--- W+++>$ N++(+++)>+++$ !o? K-? !w--- !O
> M++>$ !V-- PS+>$ !PE- Y+>$ PGP+>$ t+++>$ 5+>++++$ !X- !R tv+>$
> b++>$ !DI !D- G++(+++)>$ e>++++ h--! r--- !y-
> ------END GEEK CODE BLOCK------
>