From owner-freebsd-current Mon Nov 9 21:21:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA11946 for freebsd-current-outgoing; Mon, 9 Nov 1998 21:21:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thelab.hub.org (nat0574.mpoweredpc.net [142.177.190.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA11940 for ; Mon, 9 Nov 1998 21:21:00 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.1/8.9.1) with ESMTP id BAA13322; Tue, 10 Nov 1998 01:20:32 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Tue, 10 Nov 1998 01:20:31 -0400 (AST) From: The Hermit Hacker To: Paul Saab cc: current@FreeBSD.ORG Subject: Re: 18gig drive's supported? In-Reply-To: <19981109140601.A2798@mu.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 9 Nov 1998, Paul Saab wrote: > did you upgrade this system from a pre-cam system? If you did I > think you need to upgrade sysinstall too. Yes...next question, how to upgrade sysinstall? Went into /usr/src/release/sysinstall, typed 'make cleandir;make depend'...it failed: file2c 'u_char boot0[] = {' '};' < /boot/boot0 >> makedevs.tmp cannot open /boot/boot0: no such file *** Error code 2 Am still an aout system...if that means anything/helps? > > paul > > The Hermit Hacker (scrappy@hub.org) wrote: > > I dont' know if there is anything special that the OS has to do as far as > > large drive support is concerneed, but we just added the following drive > > to our system, and can't get anywhere with it: > > > > a1 at ahc0 bus 0 target 1 lun 0 > > da1: 17366MB (35566000 512 byte sectors: 255H 63S/T 2213C) > > da1: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled > > da1: Fixed Direct Access SCSI3 device > > > > > > We currently have three controllers in that machine, with 2+ drives per > > controller...the other drives all work (4gig drives), but this new 18gig > > appears to be a problem. > > > > hub> dmesg | grep ahc > > ahc0: rev 0x01 int a irq 12 on pci0.9.0 > > ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs > > ahc1: rev 0x01 int a irq 9 on pci0.10.0 > > ahc1: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs > > ahc2: rev 0x01 int a irq 11 on pci0.12.0 > > ahc2: aic7860 Single Channel A, SCSI Id=7, 3/255 SCBs > > probe1:ahc0:0:1:0): Sending SDTR!! > > ub> dmesg | grep "^da" | sort > > da0 at ahc0 bus 0 target 0 lun 0 > > da0: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled > > da0: 4350MB (8910423 512 byte sectors: 255H 63S/T 554C) > > da0: Fixed Direct Access SCSI2 device > > da1 at ahc0 bus 0 target 1 lun 0 > > da1: 17366MB (35566000 512 byte sectors: 255H 63S/T 2213C) > > da1: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled > > da1: Fixed Direct Access SCSI3 device > > da2 at ahc1 bus 0 target 0 lun 0 > > da2: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enables > > da2: 4341MB (8890760 512 byte sectors: 255H 63S/T 553C) > > da2: Fixed Direct Access SCSI2 device > > da3 at ahc1 bus 0 target 1 lun 0 > > da3: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled > > da3: 4341MB (8890760 512 byte sectors: 255H 63S/T 553C) > > da3: Fixed Direct Access SCSI2 device > > da4 at ahc2 bus 0 target 1 lun 0 > > da4: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled > > da4: 4106MB (8410200 512 byte sectors: 255H 63S/T 523C) > > da4: Fixed Direct Access SCSI2 device > > da5 at ahc2 bus 0 target 2 lun 0 > > da5: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled > > da5: 4106MB (8410200 512 byte sectors: 255H 63S/T 523C) > > da5: Fixed Direct Access SCSI2 device > > da6 at ahc2 bus 0 target 3 lun 0 > > da6: 20.0MB/s transfers (20.0MHz, offset 15), Tagged Queueing Enabled > > da6: 4341MB (8890760 512 byte sectors: 255H 63S/T 553C) > > da6: Fixed Direct Access SCSI2 device > > da7 at ahc2 bus 0 target 4 lun 0 > > da7: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled > > da7: 4106MB (8410200 512 byte sectors: 255H 63S/T 523C) > > da7: Fixed Direct Access SCSI2 device > > da8 at ahc2 bus 0 target 5 lun 0 > > da8: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled > > da8: 4101MB (8399520 512 byte sectors: 255H 63S/T 522C) > > da8: Fixed Direct Access SCSI2 device > > > > If I run /stand/sysinstall->Configure->Label, I get back a message stating > > that 'No disks found! Please verify that your disk controller is being > > properly probed at boot time' > > > > The system comes out on uname -a as 3.0-CURRENT, dated November 4th... > > > > Thoughts and/or ideas? Its obvious that the kernel is finding all the drives, > > so I'm curious why /stand/sysinstall doesn't see them... > > > > Thanks... > > > > > > Marc G. Fournier > > Systems Administrator @ hub.org > > primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message