*BSD News Article 63425


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!newshost.telstra.net!act.news.telstra.net!psgrain!charnel.ecst.csuchico.edu!csusac!csus.edu!news.ucdavis.edu!agate!howland.reston.ans.net!gatech!newsfeed.internetmci.com!panix!cmcl2!newsserv.cs.sunysb.edu!news.cc.sunysb.edu!not-for-mail
From: cfanning@jingoro.prevmed.sunysb.edu (Chris Fanning)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: 2.1 Release NCR SCSI install problem (phase error)
Date: 8 Mar 1996 10:18:50 -0500
Organization: The Department of Preventive Medicine at SUNY Stony Brook
Lines: 38
Message-ID: <4hpj4q$hp9@jingoro.prevmed.sunysb.edu>
NNTP-Posting-Host: jingoro.prevmed.sunysb.edu
X-Newsreader: TIN [version 1.2 PL2]

I posted this yesterday but apparently it didn't go anywhere...

Anyway, I'm having a major problem installing 2.1 on this hardware:
Asus P55SP4 motherboard with P90
NCR810 SCSI controller
Quantum 2.1GB Atlas disk

I can reliably reproduce this problem by using a FreeBSD boot disk, running
the partition editor and then 'W'riting changes to the disk.  I get the
same error if I hold off writing changes until I commit later, so no
difference there.

When I hit 'W'rite a screen comes up and says that it's writing the partition
information and then it comes back with a write error followed by the message
"Going nowhere without my init!" and proceeds to reboot itself 15 seconds
later.

From the debug screen this is the info I have:

ncr0: SCSI phaser error fixup: CCB already dequeued (0xf0b24000)
ncr0:0: ERROR (80:100) (e-af-22) (8/13) @ (1214:0e000000)
    script cmd = c0000001
    reg: da 10 00 13 47 08 00 1f 00 0e 80 af 80 01 07 00
ncr0: handshake timeout
sd0(ncr0:0:0) COMMAND FAILED (6 ff) @ f0b23400
sd0(ncr0:0:0): UNIT ATTENTION asc:29,2
, retries 3
sd0(ncr0:0:0) FAST SCSI-2 100ns (10Mb/sec) offset 8
init died (signal 0, exit 1)

I've used a different NCR SCSI card, different cables, played with (even
removed for kicks) the termination... there's nothing wrong so far as
that's concerned.  This problem is driving me nuts, I've installed on
another disk with the same hardware ...

Any ideas?

Chris