Date: Thu, 1 Jun 2000 21:22:49 -0600 From: "Kenneth D. Merry" <ken@kdm.org> To: John Lengeling <johnl@raccoon.com> Cc: John <papalia@udel.edu>, freebsd-scsi@FreeBSD.ORG Subject: Re: Dying connection? Message-ID: <20000601212248.A96817@panzer.kdm.org> In-Reply-To: <393724F1.B90D3283@raccoon.com>; from johnl@raccoon.com on Thu, Jun 01, 2000 at 10:07:30PM -0500 References: <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
On Thu, Jun 01, 2000 at 22:07:30 -0500, John Lengeling wrote: > "Kenneth D. Merry" wrote: > > On Wed, May 31, 2000 at 22:38:13 -0500, John Lengeling wrote: > > > > > > 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.) So, there are any number of things that could be wrong. Sorry I can't give you a better answer. About all you can do is check the things you can, and make sure you have a backup in case the drive is going bad. Ken -- Kenneth Merry ken@kdm.org 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?20000601212248.A96817>