Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 9 Nov 1998 14:06:01 -0600
From:      Paul Saab <paul@mu.org>
To:        The Hermit Hacker <scrappy@hub.org>
Cc:        current@FreeBSD.ORG
Subject:   Re: 18gig drive's supported?
Message-ID:  <19981109140601.A2798@mu.org>
In-Reply-To: <Pine.BSF.4.05.9811091514160.9466-100000@thelab.hub.org>; from The Hermit Hacker on Mon, Nov 09, 1998 at 03:26:52PM -0400
References:  <Pine.BSF.4.05.9811091514160.9466-100000@thelab.hub.org>

next in thread | previous in thread | raw e-mail | index | archive | help
did you upgrade this system from a pre-cam system?  If you did I
think you need to upgrade sysinstall too.

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: <COMPAQ DGHS18Y 01A0> 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: <Adaptec 2940 Ultra SCSI adapter> rev 0x01 int a irq 12 on pci0.9.0
> ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs
> ahc1: <Adaptec 2940 Ultra SCSI adapter> rev 0x01 int a irq 9 on pci0.10.0
> ahc1: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs
> ahc2: <Adaptec 2940A Ultra SCSI adapter> 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: <QUANTUM VIKING II 4.5WSE 3506> 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: <COMPAQ DGHS18Y 01A0> 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: <QUANTUM XP34550W LYK8> 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: <QUANTUM XP34550W LYK8> 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: <QUANTUM XP34301 1071> 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: <QUANTUM XP34301 1071> 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: <QUANTUM XP34550S LXY4> 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: <QUANTUM XP34301 1071> 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: <Quantum XP34300 L912> 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

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19981109140601.A2798>