Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!newshost.telstra.net!act.news.telstra.net!psgrain!iafrica.com!pipex-sa.net!plug.news.pipex.net!pipex!tube.news.pipex.net!pipex!dish.news.pipex.net!pipex!tank.news.pipex.net!pipex!news.mathworks.com!fu-berlin.de!news.belwue.de!news.uni-stuttgart.de!news.rhrz.uni-bonn.de!RRZ.Uni-Koeln.DE!zpr.uni-koeln.de!se From: se@ZPR.Uni-Koeln.DE (Stefan Esser) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: 2.1 Release NCR SCSI install problem (phase error) Date: 8 Mar 1996 22:31:25 GMT Organization: Institute for Mathematics, University of Cologne, Germany Lines: 87 Sender: se@Sisyphos (Stefan Esser) Message-ID: <4hqcft$114@news.rrz.uni-koeln.de> References: <4hpj4q$hp9@jingoro.prevmed.sunysb.edu> NNTP-Posting-Host: sisyphos.mi.uni-koeln.de To: cfanning@jingoro.prevmed.sunysb.edu (Chris Fanning) Bcc: se In article <4hpj4q$hp9@jingoro.prevmed.sunysb.edu>, cfanning@jingoro.prevmed.sunysb.edu (Chris Fanning) writes: |> I posted this yesterday but apparently it didn't go anywhere... Well, at least I didn't see it ... :) |> 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 The Quantum should work fine. I'm using exactly this drive as the reference for the NCR driver ... |> 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 The handshake timer has been disabled in more recent kernels, since it caused problems with scanners and CD-R writers. But it shouldn't cause any trouble with the Atlas! The timeout handler is triggered after 1.6 seconds of SCSI bus inactivity ... The status indicates no other error than the delayed ACK. |> 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) The command failure status (6) indicates the SCSI bus reset caused error status to be returned, same is true for the ASC(Q) of 29h (02h) ... |> 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? Well, either the disk is broken or has problems with bad blocks in the area being written by the install, I suppose. This could lead to a long delay due to error diagnostics or recovery procedures. Can you turn on AWRE and ARRE using the other system ? These will enable automatic bad block replacement ... (Use the "scsi -m 1 -P 3 -f /dev/sd0 -e" command to permanently change the values.) Please let me know what you find. Regards, STefan -- Stefan Esser, Zentrum fuer Paralleles Rechnen Tel: +49 221 4706021 Universitaet zu Koeln, Weyertal 80, 50931 Koeln FAX: +49 221 4705160 ============================================================================== http://www.zpr.uni-koeln.de/~se <se@ZPR.Uni-Koeln.DE>