From owner-freebsd-scsi Sun Feb 21 16:41: 8 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from gjp.erols.com (alex-va-n008c079.moon.jic.com [206.156.18.89]) by hub.freebsd.org (Postfix) with ESMTP id 9076710FA6 for ; Sun, 21 Feb 1999 16:41:02 -0800 (PST) (envelope-from gjp@gjp.erols.com) Received: from gjp.erols.com (localhost.erols.com [127.0.0.1]) by gjp.erols.com (8.9.1/8.8.7) with ESMTP id TAA42499; Sun, 21 Feb 1999 19:40:58 -0500 (EST) (envelope-from gjp@gjp.erols.com) To: "Kenneth D. Merry" Cc: freebsd-scsi@FreeBSD.ORG From: "Gary Palmer" Subject: Re: bad drive? In-reply-to: Your message of "Fri, 12 Feb 1999 20:38:20 MST." <199902130338.UAA38390@panzer.plutotech.com> Date: Sun, 21 Feb 1999 19:40:58 -0500 Message-ID: <42495.919644058@gjp.erols.com> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Kenneth D. Merry" wrote in message ID <199902130338.UAA38390@panzer.plutotech.com>: > I suppose it is possible that this could be caused by bad termination or > something similar. > > The problem is that we're queueing transactions to the drive, but it isn't > responding before the timeout fires. The I/O timeout for da devices is 60 > seconds. > > So, take that however you will. I would first try to make sure that the > cable is okay, as well as termination. Make sure there are no bent pins or > anything like that. > > If everything checks out in the cabling/termination department, I would > probably start to suspect that the drive is having trouble. Well, I guess it was a bad drive. It crashed the server and wiped out the boot record a few days later. Drive was replaced and machine seems to be much happier (I Hope :) ) Thanks Ken, Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message