From owner-freebsd-questions Thu Oct 12 19:19:41 1995 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id TAA09808 for questions-outgoing; Thu, 12 Oct 1995 19:19:41 -0700 Received: from hda.com (hda.com [199.232.40.182]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id TAA09801 for ; Thu, 12 Oct 1995 19:19:35 -0700 Received: (from dufault@localhost) by hda.com (8.6.11/8.6.9) id SAA03714; Thu, 12 Oct 1995 18:21:45 -0400 From: Peter Dufault Message-Id: <199510122221.SAA03714@hda.com> Subject: Re: More info on disk woes To: olsenc@smokey.ee.washington.edu (Clint Olsen) Date: Thu, 12 Oct 1995 18:21:44 -0400 (EDT) Cc: questions@freebsd.org In-Reply-To: <199510120633.XAA19754@smokey.ee.washington.edu> from "Clint Olsen" at Oct 11, 95 11:33:48 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1934 Sender: owner-questions@freebsd.org Precedence: bulk > Data in (64 of 64): > 00 00 00: The device might or might not comply to a standard. 01: Product designed prior to the SCSI-II and not SCSI-I 1f: Additional length 12 00: Reserved 00: Flags Vendor: 45 4d 55 4c 45 58 20 20 # ........EMULEX Product ID: > 4d 44 32 31 2f 53 32 20 20 20 20 20 45 53 44 49 # MD21/S2 ESDI Product revision: > 41 30 30 20 00 00 00 00 00 00 00 00 00 00 00 00 # A00 ............ > I am still not sure why the boot code cannot INQUIRE to my disks: > > % dmesg | grep aic > > aic0 at 0x340-0x35f irq 11 on isa > aic0 waiting for scsi devices to settle > (aic0:1:0): "CDC 94171-9 0045" type 0 fixed SCSI 1 > sd0(aic0:1:0): Direct-Access 312MB (640584 512 byte sectors) > (aic0:2:0): "unknown unknown ????" type 0 fixed SCSI 0 > sd1(aic0:2:0): Direct-Access 312MB (640500 512 byte sectors) Our probe code doesn't like that this doesn't claim to meet any standard, and prints out "unknown" and "unknown". That should be changed to try and print out the fields: If it had garbage I'd just as soon see > (aic0:2:0): "?-kdad??? ?03? &13 ?" type 0 fixed SCSI 0 as > (aic0:2:0): "unknown unknown ????" type 0 fixed SCSI 0 It seems to have gotten the right size for the disk. (It seems like it might be the matching ESDI CDC drive). Try booting with the verbose (-v) flag and verify that it is reading the disk geometry back OK. > So, scsi(8) works, but the driver is not talking to one of my drives > properly. Don't read much into that "unknown unknown" - it is a quick fix to have it print out EMULEX MD21 etc, so just ignore that for now. Once you've probed it what happens when you try to read the raw device? You can turn debugging on by compiling with SCSIDEBUG and then setting the debug level on the drive using "-d". -- Peter Dufault Real Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267