Date: Fri, 02 Jun 2000 01:30:21 -0400 From: John <papalia@udel.edu> To: "Kenneth D. Merry" <ken@kdm.org>, John Lengeling <johnl@raccoon.com> Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Dying connection? Message-ID: <4.3.1.2.20000602012826.00ad4e90@mail.udel.edu> In-Reply-To: <20000601212248.A96817@panzer.kdm.org> References: <393724F1.B90D3283@raccoon.com> <4.3.1.2.20000531193727.00ac2af0@mail.udel.edu> <3935DAA5.7859492B@raccoon.com> <20000531233754.A88537@panzer.kdm.org> <393724F1.B90D3283@raccoon.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > > > Wow! I was going to post this same thing tonight... I got the same > type > > > > of error message today on one of my machines. I run 4.0-RELEASE, > > > > Adaptec 2940 v1.11 firmware, and a Seagate ST34371N. I haven't had any > > > > problems with the drive over the past 10 days since I installed it. > > > > > > > > I recieved the error, while I was hitting the drive hard doing a > 1GM ftp > > > > and processing a 400M http log file using urchin. I was wondering > it if > > > > might be a firmware problem on the 2940 or the drive revolving around > > > > tag queueing. > > > > > > I kinda doubt it's a tagged queueing problem with your drives, I > think both > > > of those Seagates are known good. > > > > > > As for the controller, we don't use Adaptec's firmware, and no one > else has > > > reported Adaptec driver problems. > > > > > > You'll have to post the error messages you got. While they may look > > > similar, there are many different types of timeout messages, and > we'll only > > > be able to speculate on what the problem is if you post the errors. > > > > I wrote down the following error message: > > > > SCB 0x25 - timed out while idle, SEQADDR - 0xc > > Queueing a BDR SCB > > Bus Device Reset Message Sent > > no longer in timout, status = 34b > > Bus Device Reset on A:0 18 SCBs aborted > > Invalidating Pack > >Then the messages are somewhat similar. > >It could be drive firmware, or perhaps cabling and termination. I haven't >seen bad drive firmware on a Barracuda, so you might want to check your >cabling and termination first. (I even have the same model 4G Barracuda, >with slightly newer firmware.) > >Look for bent pins, crimped cables, cables that are too long, go too close >to a power supply, etc. > >It could also be that the drive is going bad. You might want to check and >see how many defects are in the grown defect list. (camcontrol defects >will do it, see the camcontrol(8) manual for details.) Well, this kinda brings up another question that I had posted to freebsd-questions a few weeks back.... I found info describing *what* CAM is and is supposed to do (http://people.freebsd.org/~gibbs), but is there a read-me or a txt file or *anything* someplace to describe how to set it up and configure it correctly. Just point me in the right direction :) Thanks again, John P. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4.3.1.2.20000602012826.00ad4e90>