Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!howland.erols.net!newsxfer.itd.umich.edu!news.mtu.edu!msunews!gvsu!river.it.gvsu.edu!behrensm From: behrensm@river.it.gvsu.edu (Matt Behrens) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Peculiar SCSI messages Date: 17 Jul 1997 20:44:00 GMT Organization: Grand Valley State University Lines: 25 Message-ID: <5qm06g$nm8@news.gvsu.edu> NNTP-Posting-Host: river.it.gvsu.edu X-Newsreader: TIN [version 1.2 PL0] Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:44576 Hi all, We've been having troubles off and on with a SCSI subsystem on our FreeBSD/Samba server box. It's a NCR 53C825 card driving seven generic double-speed CD-ROM's, and it's given us precious little trouble in the past. This error has come up three times over the past few days, since we updated four of the CD's: Jul 17 10:22:21 server /kernel: ncr0: timeout ccb=f066d800 (skip) Jul 17 10:25:48 server /kernel: ncr0: timeout ccb=f066dc00 (skip) Because of its timing, I'm assuming that this is a bad CD or something similar. My question: how do I tell which CD is doing it from these errors? Or is there something else I'm overlooking? And why is it that shortly after these errors occur, all disk access (even to the IDE hard disks) is uninterruptably tied up? Thanks in advance. -- Matt Behrens <zigg@iserv.net> Support the anti-spam amendment! Zigg Computer Services Visit http://www.cauce.org/ http://www.iserv.net/~zigg/