Date: Mon, 5 Jun 2000 10:50:23 +0100 From: Jose Monteiro <jm@sindigit.pt> To: "Kenneth D. Merry" <ken@kdm.org> Cc: John Lengeling <johnl@raccoon.com>, John <papalia@udel.edu>, freebsd-scsi@FreeBSD.ORG Subject: Re: Dying connection? Message-ID: <20000605105023.B44716@sindigit.pt> In-Reply-To: <20000601212248.A96817@panzer.kdm.org>; from ken@kdm.org on Thu, Jun 01, 2000 at 09:22:49PM -0600 References: <4.3.1.2.20000531193727.00ac2af0@mail.udel.edu> <3935DAA5.7859492B@raccoon.com> <20000531233754.A88537@panzer.kdm.org> <393724F1.B90D3283@raccoon.com> <20000601212248.A96817@panzer.kdm.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 02/06/00 04:22 WEST, Kenneth D. Merry wrote: > 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. i've had a similar problem like this one (same simptoms and messages) and did all the checks you mentioned plus some others with no luck. after testing and testing (different disks, new controller, etc...) the problem turned out to be a faulty motherboard. Specificaly, one of the pci slots (curiously, an unused one) had electrical problems and thus the bus resets and master aborts. hope this helps, Jose Monteiro 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?20000605105023.B44716>