Subject: Re: the plot thickens Re: can't boot MacBSD1.1 on Mac IIci
To: None <port-mac68k-outgoing@NetBSD.ORG>
From: Armen Babikyan <armenb@phish.nether.net>
List: port-mac68k
Date: 09/23/1996 20:12:37
  by netbsd1.cygnus.com with SMTP; 24 Sep 1996 00:14:09 -0000
Date: Mon, 23 Sep 1996 20:12:37 -0400 (EDT)
From: Armen Babikyan <armenb@phish.nether.net>
Reply-To: Armen Babikyan <armenb@phish.nether.net>
To: port-mac68k-outgoing@NetBSD.ORG
cc: armenb@Nether.Net
Subject: Re: the plot thickens Re: can't boot MacBSD1.1 on Mac IIci
Message-ID: <Pine.LNX.3.95.960922220121.30637B-100000@phish.nether.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

HELP!
that same "Error on SCSIRead(), # 5" happens to me, too.
i have a MacIIvx with 20MB RAM.
when i boot up, i am getting this error:
--cut here--
sd1 at scsibus0 targ 5 lun 0: <QUANTUM, PD425S, 535A> SCSI2 0/direct
fixed
sd1: ncrscsi0 : Resetting SCSI-bus (Timeout waiting for phase change)
ncrscsi0 : Resetting SCSI-bus (Timeout waiting for phase change)
sd1: could not mode sense (4); using fictitious geometry
406MB, 406 cyl, 64 head, 32 sec, 512 bytes/sec
--cut here--
and farther down, when i specify "sd1" as root device, and after it
tries to starts the network, i get this:
--cut here--
ncrscsi0 : Resetting SCSI-bus (Timeout waiting for phase-change)
sd1(ncrscsi0:5:0): not ready, data = 70 00 02 00 00 00 00 0a 00 00
/etc/netstart: cat: I/O error
sd1(ncrscsi0:5:0): not ready, data = 70 00 02 00 00 00 00 0a 00 00
/etc/netstart: hostname: I/O error
--cut here--
i get lots of the I/O error lines, and multiple timeout errors and not
ready errors in between, and after. later on, i get:
--cut here--
ncrscsi0 : No disconnected job for targetmask 20
ncrscsi0 : Resetting SCSI-bus (Failure to abort reselection)

and

uid 0 on /: out of inodes

/: create/symlink failed, no inodes free
--cut here--
the uid and symlink errors show up multiple times at the bottom of the
screen. right now, the system isn't doing anything, although i can type,
and the text appears on the screen.
i'd like to know if there's a way to fix that hardware timeout error,
or if there is possibly a way for the software to get around it.
thanks!
  - a