From owner-freebsd-current@FreeBSD.ORG Mon Feb 9 13:38:42 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DB0D616A4CE for ; Mon, 9 Feb 2004 13:38:42 -0800 (PST) Received: from smtp-gw-cl-c.dmv.com (smtp-gw-cl-c.dmv.com [216.240.97.41]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9AB2043D2F for ; Mon, 9 Feb 2004 13:38:42 -0800 (PST) (envelope-from sven@dmv.com) Received: from lanshark.dmv.com (lanshark.dmv.com [216.240.97.46]) i19LYgW1018384; Mon, 9 Feb 2004 16:34:43 -0500 (EST) (envelope-from sven@dmv.com) From: Sven Willenberger To: Doug White In-Reply-To: <20040209114753.L48001@carver.gumbysoft.com> References: <1076192961.18071.10.camel@lanshark.dmv.com> <1076338994.19845.10.camel@lanshark.dmv.com> <20040209114753.L48001@carver.gumbysoft.com> Content-Type: text/plain Message-Id: <1076362711.19842.65.camel@lanshark.dmv.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Mon, 09 Feb 2004 16:38:31 -0500 Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.39 cc: freebsd-current@freebsd.org Subject: Re: 5.2 Install CD doesn't detect all scsi drives X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Feb 2004 21:38:43 -0000 On Mon, 2004-02-09 at 14:51, Doug White wrote: > Try this. At the sysinstall menu, hit scroll lock, then arrow up and check > out the asr probe messages. It'd be extra neat if you could capture them > with a serial console. > Having issues outputting to console (minicom on another FreeBSD box) from the install CD so here is the output I copied instead: asr0: mem 0xfc000000-0xfdffffff,0xfb000000-0xfbffffff,0xf8300000-0xf82fffff irq24 at device 1.0 on pci3 asr0: major=154 pcib3: device asr0 requested decoded memory range 0xf8300000-0xf83fffff pcib1: device asr0 requested decoded memory range 0xf8300000-0xf83fffff pcib3: device asr0 requested decoded memory range 0xfb000000-0xfb400000 pcib1: device asr0 requested decoded memory range 0xfb000000-0xfb400000 . . --other devices listed here . . (probe0:asr0:0:0:0): Data Overrun (probe0:asr0:0:0:0): Retrying Command (probe0:asr0:0:0:0): Data Overrun (probe0:asr0:0:0:0): Retrying Command (probe0:asr0:0:0:0): Data Overrun (probe0:asr0:0:0:0): Retrying Command (probe0:asr0:0:0:0): Data Overrun (probe0:asr0:0:0:0): Retrying Command (probe0:asr0:0:0:0): Data Overrun (probe0:asr0:0:0:0): error 5 (probe0:asr0:0:0:0): Retries Exhausted pass0 at asr0 bus 1 target 1 lun 0 pass0: Fixed DirectAccess SCSI-2 Device pass0: Serial Number + pass0: Tagged Queueing Enabled GEOM: create disk da0 dp=0xc6fd0850 GEOM: new disk da0 da0 at asr0 bus 1 target 1 lun 0 da0: Fixed DirectAccess SCSI-2 Device da0: Serial Number + > Next, hit scroll lock to get the screen back, then go to Fixit, then > Shell. Run '/stand/camcontrol devlist -v' and paste us the output. That > should show the two disk devices. > /stand/camcontrol devlist -v scbus0 on asr0 bus 0: < > at scbus0 target -1 lun -1 () scbus1 on asr0 bus 1: at scbus1 target 1 lun 0 (da0,pass0) < > at scbus1 target -1 lun -1 () scbus-1 on xpt0 < > at scbus-1 target -1 lun -1 (xpt0) in the above: the lone SCSI drive is the one at asr0 bus 0 and is where I want the majority of the install to take place. The RAID located on bus1 is for a data spool. > Why it can't open the device is curious, and better yet is the bug where > sysinstall doesn't print errno. :-) >