From owner-freebsd-scsi Mon May 8 13:14:31 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from larryboy.graphics.cornell.edu (larryboy.graphics.cornell.edu [128.84.247.48]) by hub.freebsd.org (Postfix) with ESMTP id 9E4F537BBFF; Mon, 8 May 2000 13:14:26 -0700 (PDT) (envelope-from mkc@larryboy.graphics.cornell.edu) Received: from larryboy.graphics.cornell.edu (mkc@localhost) by larryboy.graphics.cornell.edu (8.9.3/8.9.3) with ESMTP id QAA70043; Mon, 8 May 2000 16:14:17 -0400 (EDT) (envelope-from mkc@larryboy.graphics.cornell.edu) Message-Id: <200005082014.QAA70043@larryboy.graphics.cornell.edu> To: ddw@NSMA.Arizona.EDU Cc: freebsd-scsi@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: Problems with 36GB SCSI drives... In-Reply-To: Message from Doug Wellington of "Mon, 08 May 2000 12:50:35 PDT." <200005081950.MAA16581@cortex.NSMA.Arizona.EDU> Date: Mon, 08 May 2000 16:14:17 -0400 From: Mitch Collinsworth Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >OK, I've been working on various incarnations of this problem for a week >now... I have another day or two and then I'm gonna have to go back to >NT... Sigh... [Help me, PLEASE...!] NO, anything but that! I hope you won't feel insulted if I ask if you've made extra certain that you don't have 2 devices using the same scsi address. Not just by looking at the switch or jumper settings, but reading through the boot messages to make sure they're all registering differently. Maybe even try disconnecting power from the ones not currently being used to see if that gets you through disklabel. And double-check termination and cabling distance rules. (Somehow this doesn't sound like the sort of thing NT is going to solve.) -Mitch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message