From owner-freebsd-scsi@FreeBSD.ORG Mon May 31 01:37:56 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EE6C516A4CE for ; Mon, 31 May 2004 01:37:56 -0700 (PDT) Received: from mail.marktplaza.nl (mail.marktplaza.nl [193.19.225.71]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4AFFB43D41 for ; Mon, 31 May 2004 01:37:56 -0700 (PDT) (envelope-from rudy@marktplaza.nl) Received: from localhost (localhost [127.0.0.1]) by mail.marktplaza.nl (Postfix) with ESMTP id 551A367C4 for ; Mon, 31 May 2004 10:37:52 +0200 (CEST) Received: from mail.marktplaza.nl ([127.0.0.1]) by localhost (server1.marktplaza.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 28050-10 for ; Mon, 31 May 2004 10:37:52 +0200 (CEST) Received: from rudy (marktplaza.xs4all.nl [80.126.152.60]) by mail.marktplaza.nl (Postfix) with ESMTP id C94AD67B9 for ; Mon, 31 May 2004 10:37:51 +0200 (CEST) From: "Rudy Kappert" To: Date: Mon, 31 May 2004 10:38:05 +0200 Message-ID: <000a01c446ea$979c7000$0200000a@rudy> MIME-Version: 1.0 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 X-Virus-Scanned: by amavisd-new at marktplaza.nl Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: Freebsd 5.2.1 - adaptec 2200S X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 May 2004 08:37:57 -0000 Hello, This is my first post in the freebsd-scsi mailing list, so sorry i've I do something wrong.. I've freebsd 5.2.1 installed on my supermicro systeem. I use an adaptec 2200s scsi controller. But the speed of my controller with Raid-5 of Raid-10 is very slow... Here you can see some results of bonnie: (1st = raid-5, 2nd = ide mirroring, 3rd = raid-10) http://www.webhostingtalk.nl/showthread.php?s= &postid=355145#post355145 When i look in my dmesg i get this: aac0: mem 0xf8000000-0xfbffffff irq 96 at device 1.0 o n pci5 aac0: [MPSAFE] aac0: i960RX 100MHz, 48MB cache memory, optional battery present aac0: Kernel 4.0-0, Build 6011, S/N ba67ca aac0: Supported Options=1f7e aacp0: on aac0 aacp1: on aac0 pass0 at aacp0 bus 0 target 0 lun 0 pass0: Fixed unknown SCSI-3 device pass0: 160.000MB/s transfers (80.000MHz, offset 63, 16bit) pass1 at aacp0 bus 0 target 1 lun 0 pass1: Fixed unknown SCSI-3 device pass1: 160.000MB/s transfers (80.000MHz, offset 63, 16bit) pass2 at aacp0 bus 0 target 2 lun 0 pass2: Fixed unknown SCSI-3 device pass2: 160.000MB/s transfers (80.000MHz, offset 63, 16bit) pass3 at aacp0 bus 0 target 3 lun 0 pass3: Fixed unknown SCSI-3 device pass3: 160.000MB/s transfers (80.000MHz, offset 63, 16bit) Is there a problem with my harddisks? Shouldn't it be at 320MB/s, because my adaptec should be able to use Ultra320? If you need some more informatie, please give the command to use. I'm a little bit new in the scsi world on freebsd. Regards, Rudy From owner-freebsd-scsi@FreeBSD.ORG Mon May 31 11:58:10 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D36A816A4CE for ; Mon, 31 May 2004 11:58:10 -0700 (PDT) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id B629A43D45 for ; Mon, 31 May 2004 11:58:10 -0700 (PDT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (IDENT:brdavis@localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.12.10/8.12.10) with ESMTP id i4VIvbSK006454; Mon, 31 May 2004 11:57:37 -0700 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.12.10/8.12.3/Submit) id i4VIvbR9006453; Mon, 31 May 2004 11:57:37 -0700 Date: Mon, 31 May 2004 11:57:37 -0700 From: Brooks Davis To: Alex Hoff Message-ID: <20040531185737.GB1419@Odin.AC.HMC.Edu> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="neYutvxvOLaeuPCA" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.4i cc: "'freebsd-scsi@freebsd.org'" Subject: Re: FreeBSD and extremely large volumes X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 May 2004 18:58:11 -0000 --neYutvxvOLaeuPCA Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, May 28, 2004 at 10:03:03AM -0400, Alex Hoff wrote: > Hi,=20 >=20 > We have a FreeBSD 4.7 system with an Adaptec 2200S RAID controller and 14= x > 140 gig IBM drives. We have run in to an issue that when all drives are > combined into a single volume, the OS can't handle the large number of > sectors. Since the RAID controller sets the sector size to 512, and we can > not change that, the total number of sectors in our system is between 2^31 > and 2^32. Well utilities such as fdisk use a signed integer and here in l= ies > the problem, the total number of sectors is now negative. Oops. To make > things worse, as soon as 300 gig drives become available, we will have 14= x > 300 which will result in the number of sectors > 2^32, thus overflowing t= he > int.=20 >=20 > I am sure that someone else has a setup with such a large amount of stora= ge. > What have these people done to overcome this limitation? Since we can't > change the sector size, what other tricks can we use? Keeping the drive a= s a > single volume is required for the intended application.=20 With 5.x, it's fairly easy to support volumes up to 2TB. With current releases you can install on them by creating one small MBR slice to hold the OS and leaving the rest of the disk unallocated. Fdisk deals fine with creating a second slice by hand, but sysinstall has issues. I believe there are some patchs to fix sysinstall as well. 2TB is as good as it gets with MBR partition tables. They simply can't address any more space. You either need to move to GPT or place the FS directly on the disk (allowed with GEOM). -- Brooks --neYutvxvOLaeuPCA Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFAu4AgXY6L6fI4GtQRAsxkAKCpLQwXc+Cy478txs6zD/S2U5JQfwCfUbPl N+WkNwCTU7u9kElqVWazLzw= =kMPa -----END PGP SIGNATURE----- --neYutvxvOLaeuPCA-- From owner-freebsd-scsi@FreeBSD.ORG Tue Jun 1 15:59:17 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B65CF16A4CE for ; Tue, 1 Jun 2004 15:59:17 -0700 (PDT) Received: from dragon.rutgers.edu (dragon.rutgers.edu [128.6.25.118]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6186443D46 for ; Tue, 1 Jun 2004 15:59:17 -0700 (PDT) (envelope-from bohra@cs.rutgers.edu) X-Virus-Scanned: by dragon-cgpav-clamav-v1.3b Received: from [165.230.44.70] (account bohra HELO cs.rutgers.edu) by dragon.rutgers.edu (CommuniGate Pro SMTP 4.1.8) with ESMTP id 15549613 for freebsd-scsi@freebsd.org; Tue, 01 Jun 2004 18:59:16 -0400 Message-ID: <40BD0982.9000708@cs.rutgers.edu> Date: Tue, 01 Jun 2004 18:56:02 -0400 From: Aniruddha Bohra User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040409 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-scsi@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: SCSI device question X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Jun 2004 22:59:17 -0000 Hello, All SCSI devices cam/scsi/scsi_xx.c do the following : /* * Install a global async callback. This callback will * receive async callbacks like "new device found". */ csa.event_enable = AC_FOUND_DEVICE; csa.callback = passasync; However, I did not find the code where the event is triggered. Is it automatically done by the rescan code? Is there a standard way to indicate to the peripheral drivers that there is a new device on the bus? Thanks Aniruddha From owner-freebsd-scsi@FreeBSD.ORG Tue Jun 1 16:04:52 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A506C16A4CE for ; Tue, 1 Jun 2004 16:04:52 -0700 (PDT) Received: from vjofn.tucs-beachin-obx-house.com (vjofn.tucs-beachin-obx-house.com [204.107.90.128]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5934043D45 for ; Tue, 1 Jun 2004 16:04:52 -0700 (PDT) (envelope-from tuc@tucs-beachin-obx-house.com) Received: from himinbjorg.tucs-beachin-obx-house.com (ool-44c09852.dyn.optonline.net [68.192.152.82]) (authenticated bits=128)i51N4pYT018214 for ; Tue, 1 Jun 2004 19:04:51 -0400 (EDT) Received: from himinbjorg.tucs-beachin-obx-house.com (localhost.tucs-beachin-obx-house.com [127.0.0.1])id i51N4pod013289 for ; Tue, 1 Jun 2004 19:04:51 -0400 (EDT) (envelope-from tuc@tucs-beachin-obx-house.com) Received: (from tucobx@localhost)i51N4pV4013286 for freebsd-scsi@freebsd.org; Tue, 1 Jun 2004 19:04:51 -0400 (EDT) (envelope-from tucobx) From: Tuc at Beach House Message-Id: <200406012304.i51N4pV4013286@himinbjorg.tucs-beachin-obx-house.com> To: freebsd-scsi@freebsd.org Date: Tue, 1 Jun 2004 19:04:51 -0400 (EDT) X-Mailer: ELM [version 2.5 PL6] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: 1TB issue X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Jun 2004 23:04:52 -0000 Hi, Having a SCSI Geometry issue on a 5.2.1-RELEASE-p4 system. It has a Symbios SDMS PCI SCSI, 53C1010-66 adapter that shows up as : sym0: <1010-66> port 0xa000-0xa0ff mem 0xf6000000-0xf6001fff,0xf6800000-0xf68003 ff irq 25 at device 5.0 on pci1 sym0: Symbios NVRAM, ID 7, Fast-80, LVD, parity checking sym0: open drain IRQ line driver, using on-chip SRAM sym0: using LOAD/STORE-based firmware. sym0: handling phase mismatch from SCRIPTS. And to it I'm connecting an EasyRaid II RAID box. There is LITTLE I can configure on it, basically termination, SCSI ID, and Raid 0/1/0+1/3/5 and thats pretty much it. When the system boots, the splash screen claims the geometry is 1024/255/63 at 40M sync, and 16 wide. In the controller I've used "Alternate CHS Mapping" and "SCSI Plug and Play Mapping" without any differences. When FreeBSD boots, it sees : (noperiph:sym0:0:-1:-1): SCSI BUS reset delivered. da0 at sym1 bus 0 target 3 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 31, 16bit), Tagged Queueing Enabled da0: 1060184MB (2171256832 512 byte sectors: 255H 63S/T 135154C) When I try to /stand/sysinstall it, fdisk pitches a serious fit about it. What can I do to get this configured properly? It seems that if I bring it down to RAID-1+0, it configures up fine (Not sure what the geometry shows as, sorry). Thanks, Tuc From owner-freebsd-scsi@FreeBSD.ORG Tue Jun 1 16:40:12 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CA89C16A4CE for ; Tue, 1 Jun 2004 16:40:12 -0700 (PDT) Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id 56AC143D45 for ; Tue, 1 Jun 2004 16:40:12 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: from panzer.kdm.org (localhost [127.0.0.1]) by panzer.kdm.org (8.12.9/8.12.5) with ESMTP id i51NeAui072857; Tue, 1 Jun 2004 17:40:10 -0600 (MDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.12.9/8.12.5/Submit) id i51NeAas072856; Tue, 1 Jun 2004 17:40:10 -0600 (MDT) (envelope-from ken) Date: Tue, 1 Jun 2004 17:40:10 -0600 From: "Kenneth D. Merry" To: Tuc at Beach House Message-ID: <20040601234010.GA72828@panzer.kdm.org> References: <200406012304.i51N4pV4013286@himinbjorg.tucs-beachin-obx-house.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200406012304.i51N4pV4013286@himinbjorg.tucs-beachin-obx-house.com> User-Agent: Mutt/1.4.1i cc: freebsd-scsi@freebsd.org Subject: Re: 1TB issue X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Jun 2004 23:40:12 -0000 On Tue, Jun 01, 2004 at 19:04:51 -0400, Tuc at Beach House wrote: > Hi, > > Having a SCSI Geometry issue on a 5.2.1-RELEASE-p4 system. It has > a Symbios SDMS PCI SCSI, 53C1010-66 adapter that shows up as : > > sym0: <1010-66> port 0xa000-0xa0ff mem 0xf6000000-0xf6001fff,0xf6800000-0xf68003 > ff irq 25 at device 5.0 on pci1 > sym0: Symbios NVRAM, ID 7, Fast-80, LVD, parity checking > sym0: open drain IRQ line driver, using on-chip SRAM > sym0: using LOAD/STORE-based firmware. > sym0: handling phase mismatch from SCRIPTS. > > And to it I'm connecting an EasyRaid II RAID box. There is LITTLE > I can configure on it, basically termination, SCSI ID, and Raid 0/1/0+1/3/5 > and thats pretty much it. > > When the system boots, the splash screen claims the geometry is > 1024/255/63 at 40M sync, and 16 wide. In the controller I've used > "Alternate CHS Mapping" and "SCSI Plug and Play Mapping" without any > differences. > > When FreeBSD boots, it sees : > > (noperiph:sym0:0:-1:-1): SCSI BUS reset delivered. > da0 at sym1 bus 0 target 3 lun 0 > da0: Fixed Direct Access SCSI-2 device > da0: 40.000MB/s transfers (20.000MHz, offset 31, 16bit), Tagged Queueing Enabled > da0: 1060184MB (2171256832 512 byte sectors: 255H 63S/T 135154C) > > > When I try to /stand/sysinstall it, fdisk pitches a serious fit about > it. > > What can I do to get this configured properly? It seems that if I > bring it down to RAID-1+0, it configures up fine (Not sure what the > geometry shows as, sorry). See another recent message on this list from Brooks Davis. It sounds like sysinstall has issues with large arrays in -current, but fdisk works okay. Try doing your installation on a smaller fdisk partition within sysinstall, and then once you're installed, use the command line fdisk to create another slice and use up the rest of the array. Ken -- Kenneth Merry ken@kdm.org From owner-freebsd-scsi@FreeBSD.ORG Tue Jun 1 16:53:29 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D86BD16A4CE for ; Tue, 1 Jun 2004 16:53:29 -0700 (PDT) Received: from vjofn.tucs-beachin-obx-house.com (vjofn.tucs-beachin-obx-house.com [204.107.90.128]) by mx1.FreeBSD.org (Postfix) with ESMTP id 901C543D58 for ; Tue, 1 Jun 2004 16:53:29 -0700 (PDT) (envelope-from tuc@tucs-beachin-obx-house.com) Received: from himinbjorg.tucs-beachin-obx-house.com (ool-44c09852.dyn.optonline.net [68.192.152.82]) (authenticated bits=128)i51NrPYT020277; Tue, 1 Jun 2004 19:53:25 -0400 (EDT) Received: from himinbjorg.tucs-beachin-obx-house.com (localhost.tucs-beachin-obx-house.com [127.0.0.1])id i51NrOod069824; Tue, 1 Jun 2004 19:53:24 -0400 (EDT) (envelope-from tuc@tucs-beachin-obx-house.com) Received: (from tucobx@localhost)i51NrOZj069823; Tue, 1 Jun 2004 19:53:24 -0400 (EDT) (envelope-from tucobx) From: Tuc at Beach House Message-Id: <200406012353.i51NrOZj069823@himinbjorg.tucs-beachin-obx-house.com> To: ken@kdm.org (Kenneth D. Merry) Date: Tue, 1 Jun 2004 19:53:24 -0400 (EDT) In-Reply-To: <20040601234010.GA72828@panzer.kdm.org> from "Kenneth D. Merry" at Jun 01, 2004 05:40:10 PM X-Mailer: ELM [version 2.5 PL6] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-scsi@freebsd.org cc: Tuc at Beach House Subject: Re: 1TB issue X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Jun 2004 23:53:30 -0000 > > What can I do to get this configured properly? It seems that if I > > bring it down to RAID-1+0, it configures up fine (Not sure what the > > geometry shows as, sorry). > > See another recent message on this list from Brooks Davis. It sounds like > sysinstall has issues with large arrays in -current, but fdisk works okay. > > Try doing your installation on a smaller fdisk partition within sysinstall, > and then once you're installed, use the command line fdisk to create > another slice and use up the rest of the array. > This is a 2nd drive, so its ok. I already have 5.2.1-RELEASE-p4 installed on /dev/da1. If I just do : vjofn2# fdisk da0 ******* Working on device /dev/da0 ******* parameters extracted from in-core disklabel are: cylinders=135154 heads=255 sectors/track=63 (16065 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=135154 heads=255 sectors/track=63 (16065 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 63, size 2171248947 (1060180 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 1023/ head 254/ sector 63 The data for partition 2 is: The data for partition 3 is: The data for partition 4 is: So what config to command line fdisk should I use? p 1 0 0 0 p 1 165 1 2171249010 Thanks, Tuc From owner-freebsd-scsi@FreeBSD.ORG Tue Jun 1 17:43:19 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B140816A4CF for ; Tue, 1 Jun 2004 17:43:19 -0700 (PDT) Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id 210B543D3F for ; Tue, 1 Jun 2004 17:43:19 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: from panzer.kdm.org (localhost [127.0.0.1]) by panzer.kdm.org (8.12.9/8.12.5) with ESMTP id i520hIui073211; Tue, 1 Jun 2004 18:43:18 -0600 (MDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.12.9/8.12.5/Submit) id i520hI6L073210; Tue, 1 Jun 2004 18:43:18 -0600 (MDT) (envelope-from ken) Date: Tue, 1 Jun 2004 18:43:18 -0600 From: "Kenneth D. Merry" To: Tuc at Beach House Message-ID: <20040602004318.GA73188@panzer.kdm.org> References: <20040601234010.GA72828@panzer.kdm.org> <200406012353.i51NrOZj069823@himinbjorg.tucs-beachin-obx-house.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200406012353.i51NrOZj069823@himinbjorg.tucs-beachin-obx-house.com> User-Agent: Mutt/1.4.1i cc: freebsd-scsi@freebsd.org cc: Tuc at Beach House Subject: Re: 1TB issue X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jun 2004 00:43:19 -0000 On Tue, Jun 01, 2004 at 19:53:24 -0400, Tuc at Beach House wrote: > > > What can I do to get this configured properly? It seems that if I > > > bring it down to RAID-1+0, it configures up fine (Not sure what the > > > geometry shows as, sorry). > > > > See another recent message on this list from Brooks Davis. It sounds like > > sysinstall has issues with large arrays in -current, but fdisk works okay. > > > > Try doing your installation on a smaller fdisk partition within sysinstall, > > and then once you're installed, use the command line fdisk to create > > another slice and use up the rest of the array. > > > This is a 2nd drive, so its ok. I already have 5.2.1-RELEASE-p4 > installed on /dev/da1. > > If I just do : > > vjofn2# fdisk da0 > ******* Working on device /dev/da0 ******* > parameters extracted from in-core disklabel are: > cylinders=135154 heads=255 sectors/track=63 (16065 blks/cyl) > > Figures below won't work with BIOS for partitions not in cyl 1 > parameters to be used for BIOS calculations are: > cylinders=135154 heads=255 sectors/track=63 (16065 blks/cyl) > > Media sector size is 512 > Warning: BIOS sector numbering starts with sector 1 > Information from DOS bootblock is: > The data for partition 1 is: > sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) > start 63, size 2171248947 (1060180 Meg), flag 80 (active) > beg: cyl 0/ head 1/ sector 1; > end: cyl 1023/ head 254/ sector 63 > The data for partition 2 is: > > The data for partition 3 is: > > The data for partition 4 is: > > > > So what config to command line fdisk should I use? > > p 1 0 0 0 > p 1 165 1 2171249010 > It looks like you may already have a partition there...it looks like it's about 1TB. Do things work when you attempt to disklabel it? Ken -- Kenneth Merry ken@kdm.org From owner-freebsd-scsi@FreeBSD.ORG Tue Jun 1 17:52:45 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 75C7816A4CE for ; Tue, 1 Jun 2004 17:52:45 -0700 (PDT) Received: from vjofn.tucs-beachin-obx-house.com (vjofn.tucs-beachin-obx-house.com [204.107.90.128]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2E51443D3F for ; Tue, 1 Jun 2004 17:52:45 -0700 (PDT) (envelope-from tuc@tucs-beachin-obx-house.com) Received: from himinbjorg.tucs-beachin-obx-house.com (ool-44c09852.dyn.optonline.net [68.192.152.82]) (authenticated bits=128)i520qiYT023150; Tue, 1 Jun 2004 20:52:44 -0400 (EDT) Received: from himinbjorg.tucs-beachin-obx-house.com (localhost.tucs-beachin-obx-house.com [127.0.0.1])id i520qhod038254; Tue, 1 Jun 2004 20:52:43 -0400 (EDT) (envelope-from tuc@tucs-beachin-obx-house.com) Received: (from tucobx@localhost)i520qhXc038253; Tue, 1 Jun 2004 20:52:43 -0400 (EDT) (envelope-from tucobx) From: Tuc at Beach House Message-Id: <200406020052.i520qhXc038253@himinbjorg.tucs-beachin-obx-house.com> To: ken@kdm.org (Kenneth D. Merry) Date: Tue, 1 Jun 2004 20:52:43 -0400 (EDT) In-Reply-To: <20040602004318.GA73188@panzer.kdm.org> from "Kenneth D. Merry" at Jun 01, 2004 06:43:18 PM X-Mailer: ELM [version 2.5 PL6] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-scsi@freebsd.org cc: Tuc at Beach House Subject: Re: 1TB issue X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jun 2004 00:52:45 -0000 > > On Tue, Jun 01, 2004 at 19:53:24 -0400, Tuc at Beach House wrote: > > > > What can I do to get this configured properly? It seems that if I > > > > bring it down to RAID-1+0, it configures up fine (Not sure what the > > > > geometry shows as, sorry). > > > > > > See another recent message on this list from Brooks Davis. It sounds like > > > sysinstall has issues with large arrays in -current, but fdisk works okay. > > > > > > Try doing your installation on a smaller fdisk partition within sysinstall, > > > and then once you're installed, use the command line fdisk to create > > > another slice and use up the rest of the array. > > > > > This is a 2nd drive, so its ok. I already have 5.2.1-RELEASE-p4 > > installed on /dev/da1. > > > > If I just do : > > > > vjofn2# fdisk da0 > > ******* Working on device /dev/da0 ******* > > parameters extracted from in-core disklabel are: > > cylinders=135154 heads=255 sectors/track=63 (16065 blks/cyl) > > > > Figures below won't work with BIOS for partitions not in cyl 1 > > parameters to be used for BIOS calculations are: > > cylinders=135154 heads=255 sectors/track=63 (16065 blks/cyl) > > > > Media sector size is 512 > > Warning: BIOS sector numbering starts with sector 1 > > Information from DOS bootblock is: > > The data for partition 1 is: > > sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) > > start 63, size 2171248947 (1060180 Meg), flag 80 (active) > > beg: cyl 0/ head 1/ sector 1; > > end: cyl 1023/ head 254/ sector 63 > > The data for partition 2 is: > > > > The data for partition 3 is: > > > > The data for partition 4 is: > > > > > > > > So what config to command line fdisk should I use? > > > > p 1 0 0 0 > > p 1 165 1 2171249010 > > > > It looks like you may already have a partition there...it looks like it's > about 1TB. > > Do things work when you attempt to disklabel it? > Fatal Error: Partitions are larger than actual chunk?? - PRESS ANY KEY TO QUIT Won't let me go any farther. Tuc From owner-freebsd-scsi@FreeBSD.ORG Tue Jun 1 17:53:17 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8E14816A4CE for ; Tue, 1 Jun 2004 17:53:17 -0700 (PDT) Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1AC4643D45 for ; Tue, 1 Jun 2004 17:53:17 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: from panzer.kdm.org (localhost [127.0.0.1]) by panzer.kdm.org (8.12.9/8.12.5) with ESMTP id i520r6ui073303; Tue, 1 Jun 2004 18:53:06 -0600 (MDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.12.9/8.12.5/Submit) id i520r61h073302; Tue, 1 Jun 2004 18:53:06 -0600 (MDT) (envelope-from ken) Date: Tue, 1 Jun 2004 18:53:06 -0600 From: "Kenneth D. Merry" To: Aniruddha Bohra Message-ID: <20040602005306.GA73243@panzer.kdm.org> References: <40BD0982.9000708@cs.rutgers.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <40BD0982.9000708@cs.rutgers.edu> User-Agent: Mutt/1.4.1i cc: freebsd-scsi@freebsd.org Subject: Re: SCSI device question X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jun 2004 00:53:17 -0000 On Tue, Jun 01, 2004 at 18:56:02 -0400, Aniruddha Bohra wrote: > Hello, > All SCSI devices cam/scsi/scsi_xx.c > do the following : > /* > * Install a global async callback. This callback will > * receive async callbacks like "new device found". > */ > csa.event_enable = AC_FOUND_DEVICE; > csa.callback = passasync; > > However, I did not find the code where the event is > triggered. Is it automatically done by the rescan code? > Is there a standard way to indicate to the peripheral drivers > that there is a new device on the bus? See sys/cam/cam_xpt.c, the function probedone() in the PROBE_TUR_FOR_NEGOTIATION case. (xpt_async(AC_FOUND_DEVICE, path, ccb)) It's triggered by a rescan or initial probe at boot. What are you trying to do? Ken -- Kenneth Merry ken@kdm.org From owner-freebsd-scsi@FreeBSD.ORG Tue Jun 1 17:56:27 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6DFD716A4CE for ; Tue, 1 Jun 2004 17:56:27 -0700 (PDT) Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7494243D49 for ; Tue, 1 Jun 2004 17:56:26 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: from panzer.kdm.org (localhost [127.0.0.1]) by panzer.kdm.org (8.12.9/8.12.5) with ESMTP id i520uPui073361; Tue, 1 Jun 2004 18:56:25 -0600 (MDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.12.9/8.12.5/Submit) id i520uPdd073360; Tue, 1 Jun 2004 18:56:25 -0600 (MDT) (envelope-from ken) Date: Tue, 1 Jun 2004 18:56:25 -0600 From: "Kenneth D. Merry" To: Tuc at Beach House Message-ID: <20040602005625.GA73344@panzer.kdm.org> References: <20040602004318.GA73188@panzer.kdm.org> <200406020052.i520qhXc038253@himinbjorg.tucs-beachin-obx-house.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200406020052.i520qhXc038253@himinbjorg.tucs-beachin-obx-house.com> User-Agent: Mutt/1.4.1i cc: freebsd-scsi@freebsd.org cc: Tuc at Beach House Subject: Re: 1TB issue X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jun 2004 00:56:27 -0000 On Tue, Jun 01, 2004 at 20:52:43 -0400, Tuc at Beach House wrote: > > > > On Tue, Jun 01, 2004 at 19:53:24 -0400, Tuc at Beach House wrote: > > > > > What can I do to get this configured properly? It seems that if I > > > > > bring it down to RAID-1+0, it configures up fine (Not sure what the > > > > > geometry shows as, sorry). > > > > > > > > See another recent message on this list from Brooks Davis. It sounds like > > > > sysinstall has issues with large arrays in -current, but fdisk works okay. > > > > > > > > Try doing your installation on a smaller fdisk partition within sysinstall, > > > > and then once you're installed, use the command line fdisk to create > > > > another slice and use up the rest of the array. > > > > > > > This is a 2nd drive, so its ok. I already have 5.2.1-RELEASE-p4 > > > installed on /dev/da1. > > > > > > If I just do : > > > > > > vjofn2# fdisk da0 > > > ******* Working on device /dev/da0 ******* > > > parameters extracted from in-core disklabel are: > > > cylinders=135154 heads=255 sectors/track=63 (16065 blks/cyl) > > > > > > Figures below won't work with BIOS for partitions not in cyl 1 > > > parameters to be used for BIOS calculations are: > > > cylinders=135154 heads=255 sectors/track=63 (16065 blks/cyl) > > > > > > Media sector size is 512 > > > Warning: BIOS sector numbering starts with sector 1 > > > Information from DOS bootblock is: > > > The data for partition 1 is: > > > sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) > > > start 63, size 2171248947 (1060180 Meg), flag 80 (active) > > > beg: cyl 0/ head 1/ sector 1; > > > end: cyl 1023/ head 254/ sector 63 > > > The data for partition 2 is: > > > > > > The data for partition 3 is: > > > > > > The data for partition 4 is: > > > > > > > > > > > > So what config to command line fdisk should I use? > > > > > > p 1 0 0 0 > > > p 1 165 1 2171249010 > > > > > > > It looks like you may already have a partition there...it looks like it's > > about 1TB. > > > > Do things work when you attempt to disklabel it? > > > Fatal Error: Partitions are larger than actual chunk?? - PRESS ANY KEY TO QUIT > > > Won't let me go any farther. You might try "dangerously dedicated" mode, assuming it works. First, blow away your fdisk table: dd if=/dev/zero of=/dev/da0 bs=1m count=1 Then try generating a label automatically: bsdlabel -wr da0 auto Then edit the label, and fix up the partition type, etc.: bsdlabel -e da0 If that works you should be able to newfs da0a, or whatever letter partition you setup in the previous step. Ken -- Kenneth Merry ken@kdm.org From owner-freebsd-scsi@FreeBSD.ORG Tue Jun 1 18:03:40 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8478A16A4CE for ; Tue, 1 Jun 2004 18:03:40 -0700 (PDT) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6691143D1F for ; Tue, 1 Jun 2004 18:03:40 -0700 (PDT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (IDENT:brdavis@localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.12.10/8.12.10) with ESMTP id i5213eSK029822; Tue, 1 Jun 2004 18:03:40 -0700 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.12.10/8.12.3/Submit) id i5213elU029821; Tue, 1 Jun 2004 18:03:40 -0700 Date: Tue, 1 Jun 2004 18:03:39 -0700 From: Brooks Davis To: "Kenneth D. Merry" Message-ID: <20040602010339.GA29173@Odin.AC.HMC.Edu> References: <20040602004318.GA73188@panzer.kdm.org> <200406020052.i520qhXc038253@himinbjorg.tucs-beachin-obx-house.com> <20040602005625.GA73344@panzer.kdm.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="zhXaljGHf11kAtnf" Content-Disposition: inline In-Reply-To: <20040602005625.GA73344@panzer.kdm.org> User-Agent: Mutt/1.5.4i cc: freebsd-scsi@freebsd.org cc: Tuc at Beach House Subject: Re: 1TB issue X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jun 2004 01:03:40 -0000 --zhXaljGHf11kAtnf Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jun 01, 2004 at 06:56:25PM -0600, Kenneth D. Merry wrote: > On Tue, Jun 01, 2004 at 20:52:43 -0400, Tuc at Beach House wrote: > > >=20 > > > On Tue, Jun 01, 2004 at 19:53:24 -0400, Tuc at Beach House wrote: > > > > > > What can I do to get this configured properly? It seems= that if I > > > > > > bring it down to RAID-1+0, it configures up fine (Not sure what= the > > > > > > geometry shows as, sorry). > > > > >=20 > > > > > See another recent message on this list from Brooks Davis. It so= unds like > > > > > sysinstall has issues with large arrays in -current, but fdisk wo= rks okay. > > > > >=20 > > > > > Try doing your installation on a smaller fdisk partition within s= ysinstall, > > > > > and then once you're installed, use the command line fdisk to cre= ate > > > > > another slice and use up the rest of the array. > > > > >=20 > > > > This is a 2nd drive, so its ok. I already have 5.2.1-RELEASE-p4=20 > > > > installed on /dev/da1. > > > >=20 > > > > If I just do : > > > >=20 > > > > vjofn2# fdisk da0 > > > > ******* Working on device /dev/da0 ******* > > > > parameters extracted from in-core disklabel are: > > > > cylinders=3D135154 heads=3D255 sectors/track=3D63 (16065 blks/cyl) > > > >=20 > > > > Figures below won't work with BIOS for partitions not in cyl 1 > > > > parameters to be used for BIOS calculations are: > > > > cylinders=3D135154 heads=3D255 sectors/track=3D63 (16065 blks/cyl) > > > >=20 > > > > Media sector size is 512 > > > > Warning: BIOS sector numbering starts with sector 1 > > > > Information from DOS bootblock is: > > > > The data for partition 1 is: > > > > sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) > > > > start 63, size 2171248947 (1060180 Meg), flag 80 (active) > > > > beg: cyl 0/ head 1/ sector 1; > > > > end: cyl 1023/ head 254/ sector 63 > > > > The data for partition 2 is: > > > > > > > > The data for partition 3 is: > > > > > > > > The data for partition 4 is: > > > > > > > >=20 > > > >=20 > > > > So what config to command line fdisk should I use? > > > >=20 > > > > p 1 0 0 0 > > > > p 1 165 1 2171249010 > > > >=20 > > >=20 > > > It looks like you may already have a partition there...it looks like = it's > > > about 1TB. > > >=20 > > > Do things work when you attempt to disklabel it? > > >=20 > > Fatal Error: Partitions are larger than actual chunk?? - PRESS ANY KEY = TO QUIT > >=20 > >=20 > > Won't let me go any farther. >=20 > You might try "dangerously dedicated" mode, assuming it works. First, bl= ow > away your fdisk table: >=20 > dd if=3D/dev/zero of=3D/dev/da0 bs=3D1m count=3D1 >=20 > Then try generating a label automatically: >=20 > bsdlabel -wr da0 auto >=20 > Then edit the label, and fix up the partition type, etc.: >=20 > bsdlabel -e da0 >=20 > If that works you should be able to newfs da0a, or whatever letter > partition you setup in the previous step. I'm not sure what the limit of a BSD label is, but it my be 1TB unless you can up the block size (512K blocks plus signed ints yeilds 1TB limits). You may want to use fdisk to make a slice for any large partitions rather then trying to use disklabel. On the 2TB system I have, I have one slice that is around 40GB that contains a disklabel and the partions making up a normal OS install. A second slice that has a 1.8TB UFS file system and no disklabel. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --zhXaljGHf11kAtnf Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFAvSdrXY6L6fI4GtQRAmkOAKC5JQr9IxW+OaZjfDOU3EMB0zzytQCfaE1m Y0S4MrcJzZAdje9k6W6pQFM= =8iZe -----END PGP SIGNATURE----- --zhXaljGHf11kAtnf-- From owner-freebsd-scsi@FreeBSD.ORG Tue Jun 1 18:12:54 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 49A0C16A4CE for ; Tue, 1 Jun 2004 18:12:54 -0700 (PDT) Received: from vjofn.tucs-beachin-obx-house.com (vjofn.tucs-beachin-obx-house.com [204.107.90.128]) by mx1.FreeBSD.org (Postfix) with ESMTP id C1AD943D48 for ; Tue, 1 Jun 2004 18:12:53 -0700 (PDT) (envelope-from tuc@tucs-beachin-obx-house.com) Received: from himinbjorg.tucs-beachin-obx-house.com (ool-44c09852.dyn.optonline.net [68.192.152.82]) (authenticated bits=128)i521CiYT024212; Tue, 1 Jun 2004 21:12:44 -0400 (EDT) Received: from himinbjorg.tucs-beachin-obx-house.com (localhost.tucs-beachin-obx-house.com [127.0.0.1])id i521Ciod094525; Tue, 1 Jun 2004 21:12:44 -0400 (EDT) (envelope-from tuc@tucs-beachin-obx-house.com) Received: (from tucobx@localhost)i521CitN094524; Tue, 1 Jun 2004 21:12:44 -0400 (EDT) (envelope-from tucobx) From: Tuc at Beach House Message-Id: <200406020112.i521CitN094524@himinbjorg.tucs-beachin-obx-house.com> To: ken@kdm.org (Kenneth D. Merry) Date: Tue, 1 Jun 2004 21:12:44 -0400 (EDT) In-Reply-To: <20040602005625.GA73344@panzer.kdm.org> from "Kenneth D. Merry" at Jun 01, 2004 06:56:25 PM X-Mailer: ELM [version 2.5 PL6] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-scsi@freebsd.org cc: Tuc at Beach House Subject: Re: 1TB issue X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jun 2004 01:12:54 -0000 > > On Tue, Jun 01, 2004 at 20:52:43 -0400, Tuc at Beach House wrote: > > > > > > On Tue, Jun 01, 2004 at 19:53:24 -0400, Tuc at Beach House wrote: > > > > > > What can I do to get this configured properly? It seems that if I > > > > > > bring it down to RAID-1+0, it configures up fine (Not sure what the > > > > > > geometry shows as, sorry). > > > > > > > > > > See another recent message on this list from Brooks Davis. It sounds like > > > > > sysinstall has issues with large arrays in -current, but fdisk works okay. > > > > > > > > > > Try doing your installation on a smaller fdisk partition within sysinstall, > > > > > and then once you're installed, use the command line fdisk to create > > > > > another slice and use up the rest of the array. > > > > > > > > > This is a 2nd drive, so its ok. I already have 5.2.1-RELEASE-p4 > > > > installed on /dev/da1. > > > > > > > > If I just do : > > > > > > > > vjofn2# fdisk da0 > > > > ******* Working on device /dev/da0 ******* > > > > parameters extracted from in-core disklabel are: > > > > cylinders=135154 heads=255 sectors/track=63 (16065 blks/cyl) > > > > > > > > Figures below won't work with BIOS for partitions not in cyl 1 > > > > parameters to be used for BIOS calculations are: > > > > cylinders=135154 heads=255 sectors/track=63 (16065 blks/cyl) > > > > > > > > Media sector size is 512 > > > > Warning: BIOS sector numbering starts with sector 1 > > > > Information from DOS bootblock is: > > > > The data for partition 1 is: > > > > sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) > > > > start 63, size 2171248947 (1060180 Meg), flag 80 (active) > > > > beg: cyl 0/ head 1/ sector 1; > > > > end: cyl 1023/ head 254/ sector 63 > > > > The data for partition 2 is: > > > > > > > > The data for partition 3 is: > > > > > > > > The data for partition 4 is: > > > > > > > > > > > > > > > > So what config to command line fdisk should I use? > > > > > > > > p 1 0 0 0 > > > > p 1 165 1 2171249010 > > > > > > > > > > It looks like you may already have a partition there...it looks like it's > > > about 1TB. > > > > > > Do things work when you attempt to disklabel it? > > > > > Fatal Error: Partitions are larger than actual chunk?? - PRESS ANY KEY TO QUIT > > > > > > Won't let me go any farther. > > You might try "dangerously dedicated" mode, assuming it works. First, blow > away your fdisk table: > > dd if=/dev/zero of=/dev/da0 bs=1m count=1 > vjofn2# dd if=/dev/zero of=/dev/da0 bs=1m count=1 1+0 records in 1+0 records out 1048576 bytes transferred in 0.037119 secs (28249104 bytes/sec) > > Then try generating a label automatically: > > bsdlabel -wr da0 auto > vjofn2# bsdlabel -wr da0 auto vjofn2# > > Then edit the label, and fix up the partition type, etc.: > > bsdlabel -e da0 > I decided to change it from "a" to "h". > > If that works you should be able to newfs da0a, or whatever letter > partition you setup in the previous step. > (Copious output....................................) (SERIOUSLY COPIOUS!) When I mount it : /dev/da0h 1051469836 4 967352246 0% /news Now lets run a news system for a little bit and see if it starts to get cranky like it used to. :) Thanks, Tuc From owner-freebsd-scsi@FreeBSD.ORG Tue Jun 1 23:36:36 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E92D616A4CE for ; Tue, 1 Jun 2004 23:36:36 -0700 (PDT) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id DE10643D31 for ; Tue, 1 Jun 2004 23:36:36 -0700 (PDT) (envelope-from ps@freebsd.org) Received: from [192.168.1.100] (adsl-67-122-220-241.dsl.snfc21.pacbell.net [67.122.220.241]) by elvis.mu.org (Postfix) with ESMTP id A7A275C82C; Tue, 1 Jun 2004 23:36:36 -0700 (PDT) Message-ID: <40BD75EC.20208@freebsd.org> Date: Tue, 01 Jun 2004 23:38:36 -0700 From: Paul Saab User-Agent: Mozilla Thunderbird 0.6+ (Windows/20040530) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tuc at Beach House References: <200406020112.i521CitN094524@himinbjorg.tucs-beachin-obx-house.com> In-Reply-To: <200406020112.i521CitN094524@himinbjorg.tucs-beachin-obx-house.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-scsi@freebsd.org cc: "Kenneth D. Merry" cc: Tuc at Beach House Subject: Re: 1TB issue X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jun 2004 06:36:37 -0000 Tuc at Beach House wrote: >>If that works you should be able to newfs da0a, or whatever letter >>partition you setup in the previous step. >> >> >> > (Copious output....................................) > > (SERIOUSLY COPIOUS!) > > When I mount it : > >/dev/da0h 1051469836 4 967352246 0% /news > > Now lets run a news system for a little bit and see if it starts >to get cranky like it used to. :) > > Just as an FYI, with -current, if this isn't the boot disk you dont even need a disklabel, you can just newfs da0 and mount it. From owner-freebsd-scsi@FreeBSD.ORG Wed Jun 2 02:49:42 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DFFCA16A4CE for ; Wed, 2 Jun 2004 02:49:42 -0700 (PDT) Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by mx1.FreeBSD.org (Postfix) with SMTP id 200C843D55 for ; Wed, 2 Jun 2004 02:49:42 -0700 (PDT) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 2 Jun 2004 10:49:41 +0100 (BST) Date: Wed, 2 Jun 2004 10:49:39 +0100 From: David Malone To: "Kenneth D. Merry" Message-ID: <20040602094939.GA48588@walton.maths.tcd.ie> References: <200406012304.i51N4pV4013286@himinbjorg.tucs-beachin-obx-house.com> <20040601234010.GA72828@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040601234010.GA72828@panzer.kdm.org> User-Agent: Mutt/1.5.3i Sender: dwmalone@maths.tcd.ie cc: freebsd-scsi@freebsd.org Subject: Re: 1TB issue X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jun 2004 09:49:43 -0000 On Tue, Jun 01, 2004 at 05:40:10PM -0600, Kenneth D. Merry wrote: > See another recent message on this list from Brooks Davis. It sounds like > sysinstall has issues with large arrays in -current, but fdisk works okay. I've heard from some people that there was a 2TB limit on SCSI devices, but it wasn't clear to me if this was a limit of the SCSI implementation they were using, or if it arose from the SCSI spec. What's actually the case here? David. From owner-freebsd-scsi@FreeBSD.ORG Wed Jun 2 03:51:18 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BA8E416A4CE for ; Wed, 2 Jun 2004 03:51:18 -0700 (PDT) Received: from mailout2.pacific.net.au (mailout2.pacific.net.au [61.8.0.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 421EF43D39 for ; Wed, 2 Jun 2004 03:51:15 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from mailproxy2.pacific.net.au (mailproxy2.pacific.net.au [61.8.0.87])i52ApA5v010775; Wed, 2 Jun 2004 20:51:10 +1000 Received: from gamplex.bde.org (katana.zip.com.au [61.8.7.246]) i52Ap7LS029355; Wed, 2 Jun 2004 20:51:08 +1000 Date: Wed, 2 Jun 2004 20:51:06 +1000 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Brooks Davis In-Reply-To: <20040602010339.GA29173@Odin.AC.HMC.Edu> Message-ID: <20040602203400.N24291@gamplex.bde.org> References: <20040602004318.GA73188@panzer.kdm.org> <200406020052.i520qhXc038253@himinbjorg.tucs-beachin-obx-house.com> <20040602010339.GA29173@Odin.AC.HMC.Edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-scsi@freebsd.org cc: "Kenneth D. Merry" cc: Tuc at Beach House Subject: Re: 1TB issue X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jun 2004 10:51:18 -0000 > I'm not sure what the limit of a BSD label is, but it my be 1TB unless > you can up the block size (512K blocks plus signed ints yeilds 1TB > limits). You may want to use fdisk to make a slice for any large > partitions rather then trying to use disklabel. On the 2TB system I > have, I have one slice that is around 40GB that contains a disklabel and > the partions making up a normal OS install. A second slice that has a > 1.8TB UFS file system and no disklabel. The limit for a bsd label is 2^32-1 sectors (unless geom has broken it). With the normal sector size of 512 bytes, this gives a limit of 2TB less 512 bytes. With a larger sector size, the limit is larger. A sector size of 2048 is quite reasonable, since this is the default fragment size for ffs. This gives a limit of 8TB less 2048 bytes. The main 1TB limits are that RELENG_4 doesn't support disk addresses larger than 1TB, and ffs1 is broken for disk addresses larger than 1TB (disk addresses 31 bytes in units of fragments internally in ffs, so the limit with the default fragment size of 2048 is 4TB less 2048 bytes, but things break at 1TB due to bogus parentheses in the conversion from ffs addresses to disk addresses). Bruce From owner-freebsd-scsi@FreeBSD.ORG Wed Jun 2 05:17:25 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ACD5C16A4D8 for ; Wed, 2 Jun 2004 05:17:25 -0700 (PDT) Received: from dragon.rutgers.edu (dragon.rutgers.edu [128.6.25.118]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5724A43D1D for ; Wed, 2 Jun 2004 05:17:25 -0700 (PDT) (envelope-from bohra@cs.rutgers.edu) X-Virus-Scanned: by dragon-cgpav-clamav-v1.3b Received: from [165.230.44.70] (account bohra HELO cs.rutgers.edu) by dragon.rutgers.edu (CommuniGate Pro SMTP 4.1.8) with ESMTP id 15568525; Wed, 02 Jun 2004 08:17:11 -0400 Message-ID: <40BDC483.9040502@cs.rutgers.edu> Date: Wed, 02 Jun 2004 08:13:55 -0400 From: Aniruddha Bohra User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040409 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Kenneth D. Merry" References: <40BD0982.9000708@cs.rutgers.edu> <20040602005306.GA73243@panzer.kdm.org> In-Reply-To: <20040602005306.GA73243@panzer.kdm.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-scsi@freebsd.org Subject: Re: SCSI device question X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jun 2004 12:17:25 -0000 Kenneth D. Merry wrote: > On Tue, Jun 01, 2004 at 18:56:02 -0400, Aniruddha Bohra wrote: > >>Hello, >> All SCSI devices cam/scsi/scsi_xx.c >>do the following : >> /* >> * Install a global async callback. This callback will >> * receive async callbacks like "new device found". >> */ >> csa.event_enable = AC_FOUND_DEVICE; >> csa.callback = passasync; >> >> However, I did not find the code where the event is >>triggered. Is it automatically done by the rescan code? >>Is there a standard way to indicate to the peripheral drivers >>that there is a new device on the bus? > > > See sys/cam/cam_xpt.c, the function probedone() in the > PROBE_TUR_FOR_NEGOTIATION case. (xpt_async(AC_FOUND_DEVICE, path, ccb)) > > It's triggered by a rescan or initial probe at boot. Thanks a lot. > > What are you trying to do? I am just trying to understand the code. Thanks Aniruddha From owner-freebsd-scsi@FreeBSD.ORG Wed Jun 2 06:12:02 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3230216A4CE for ; Wed, 2 Jun 2004 06:12:02 -0700 (PDT) Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id 63F2343D46 for ; Wed, 2 Jun 2004 06:12:00 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: from panzer.kdm.org (localhost [127.0.0.1]) by panzer.kdm.org (8.12.9/8.12.5) with ESMTP id i52DBtui077167; Wed, 2 Jun 2004 07:11:55 -0600 (MDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.12.9/8.12.5/Submit) id i52DBrNS077164; Wed, 2 Jun 2004 07:11:53 -0600 (MDT) (envelope-from ken) Date: Wed, 2 Jun 2004 07:11:53 -0600 From: "Kenneth D. Merry" To: David Malone Message-ID: <20040602131153.GA77049@panzer.kdm.org> References: <200406012304.i51N4pV4013286@himinbjorg.tucs-beachin-obx-house.com> <20040601234010.GA72828@panzer.kdm.org> <20040602094939.GA48588@walton.maths.tcd.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040602094939.GA48588@walton.maths.tcd.ie> User-Agent: Mutt/1.4.1i cc: freebsd-scsi@freebsd.org Subject: Re: 1TB issue X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jun 2004 13:12:02 -0000 On Wed, Jun 02, 2004 at 10:49:39 +0100, David Malone wrote: > On Tue, Jun 01, 2004 at 05:40:10PM -0600, Kenneth D. Merry wrote: > > See another recent message on this list from Brooks Davis. It sounds like > > sysinstall has issues with large arrays in -current, but fdisk works okay. > > I've heard from some people that there was a 2TB limit on SCSI > devices, but it wasn't clear to me if this was a limit of the SCSI > implementation they were using, or if it arose from the SCSI spec. > What's actually the case here? It's a limitation in the device they're using and/or the SCSI layer they're using. With 10 or 12 byte read/write CDBs, you're limited to 32 bits to specify the LBA. For a device with 512 byte sectors, that limits you to 2TB. With the SBC-2 spec, they (T10) introduced 16 byte read, write and read capacity commands. That allows you to get the size of a device larger than 2TB, and address blocks past the 2TB limit. (The size of the LBA field was increased to 8 bytes for the 16 byte commands, so you can address 2^64 blocks.) CAM in FreeBSD-current has had support for devices larger than 2TB for a little over a year. -stable doesn't have that support, because it has other limitations (pointed out by Bruce) that basically mean CAM support for large devices wouldn't really matter. Ken -- Kenneth Merry ken@kdm.org From owner-freebsd-scsi@FreeBSD.ORG Wed Jun 2 06:35:13 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 640DB16A4CE for ; Wed, 2 Jun 2004 06:35:13 -0700 (PDT) Received: from mail825.megamailservers.com (mail825.carrierinternetsolutions.com [69.49.106.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id D04C643D39 for ; Wed, 2 Jun 2004 06:35:12 -0700 (PDT) (envelope-from strick@covad.net) X-POP-User: strick.covad.net Received: from mist.nodomain (h-67-101-150-45.snfccasy.dynamic.covad.net [67.101.150.45])i52DZ3qC025763; Wed, 2 Jun 2004 09:35:11 -0400 Received: from mist.nodomain (localhost [127.0.0.1]) by mist.nodomain (8.12.11/8.12.11) with ESMTP id i52DZ29o034043; Wed, 2 Jun 2004 06:35:02 -0700 (PDT) (envelope-from dan@mist.nodomain) Received: (from dan@localhost) by mist.nodomain (8.12.11/8.12.11/Submit) id i52DZ2eD034042; Wed, 2 Jun 2004 06:35:02 -0700 (PDT) (envelope-from dan) Date: Wed, 2 Jun 2004 06:35:02 -0700 (PDT) From: Dan Strick Message-Id: <200406021335.i52DZ2eD034042@mist.nodomain> To: dwmalone@maths.tcd.ie cc: freebsd-scsi@freebsd.org Subject: Re: 1TB issue X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jun 2004 13:35:13 -0000 On Wed, 2 Jun 2004 10:49:39 +0100, David Malone wrote: >> > I've heard from some people that there was a 2TB limit on SCSI > devices, but it wasn't clear to me if this was a limit of the SCSI > implementation they were using, or if it arose from the SCSI spec. > What's actually the case here? >> The group 1 SCSI read/write command descriptor blocks have only a 32 bit field for the device address (block number). 2^32 * 2^9 = 2^41 The group 4 SCSI read/write commands defined in the not-yet-published SCSI Block Commands-2 (SBC-2) standard have a 64 bit field for the device address. Dan Strick From owner-freebsd-scsi@FreeBSD.ORG Thu Jun 3 09:52:49 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 10F5416A4CE for ; Thu, 3 Jun 2004 09:52:49 -0700 (PDT) Received: from mail.sandvine.com (sandvine.com [199.243.201.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 865B743D2D for ; Thu, 3 Jun 2004 09:52:48 -0700 (PDT) (envelope-from ahoff@sandvine.com) Received: by mail.sandvine.com with Internet Mail Service (5.5.2657.72) id ; Thu, 3 Jun 2004 12:52:47 -0400 Message-ID: From: Alex Hoff To: "'freebsd-scsi@freebsd.org'" Date: Thu, 3 Jun 2004 12:52:46 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="iso-8859-1" Subject: AACCLI feedback X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jun 2004 16:52:49 -0000 Recently I have been getting quite a few core dumps when trying to use the aaccli tool. When executing the following : open aac0 controller firmware update ac220001.ufi the program cores. When trying the linux version using freebsd compatability code (on 5.2) the same command works just fine. This command also causes aaccli to crash, but I have not yet tried it in the linux version. open aac0: container reconfigure /raid5=TRUE /partition_size=$disk_size 0 $add_disks: exit where disk_size and add_disks are the appropriate values. If any updates are available, that would be greatly appreciated. Thanks From owner-freebsd-scsi@FreeBSD.ORG Thu Jun 3 10:09:55 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A716016A4CE for ; Thu, 3 Jun 2004 10:09:55 -0700 (PDT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5401D43D2D for ; Thu, 3 Jun 2004 10:09:55 -0700 (PDT) (envelope-from scottl@freebsd.org) Received: from [192.168.0.12] (g4.samsco.home [192.168.0.12]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id i53HH3uN025016; Thu, 3 Jun 2004 11:17:03 -0600 (MDT) (envelope-from scottl@freebsd.org) Message-ID: <40BF5B26.5000709@freebsd.org> Date: Thu, 03 Jun 2004 11:08:54 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040514 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Alex Hoff References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: "'freebsd-scsi@freebsd.org'" Subject: Re: AACCLI feedback X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jun 2004 17:09:55 -0000 Alex Hoff wrote: > Recently I have been getting quite a few core dumps when trying to use the > aaccli tool. > > When executing the following : > open aac0 > controller firmware update ac220001.ufi > > the program cores. > When trying the linux version using freebsd compatability code (on 5.2) the > same command works just fine. > The FreeBSD aaccli was compiled before the 2200 was released and does not have the modifications that are needed in order to flash these (and later cards). You'll need to use the Linux version. > This command also causes aaccli to crash, but I have not yet tried it in the > linux version. > open aac0: container reconfigure /raid5=TRUE /partition_size=$disk_size 0 > $add_disks: exit > where disk_size and add_disks are the appropriate values. Does the operation start? I've seen this too and I think it has something to do with the monitoring task that is generated, but I don't know for sure. I no longer work for Adaptec so I can no longer modify the code and release it. > > If any updates are available, that would be greatly appreciated. Call up Adaptec tech support and tell them that you want an update. If enough people do this, it might make a difference. In the mean time, the linux version should work fine. Scott From owner-freebsd-scsi@FreeBSD.ORG Thu Jun 3 14:14:55 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D2EF316A4CF for ; Thu, 3 Jun 2004 14:14:55 -0700 (PDT) Received: from ioskeha.hittite.isp.9tel.net (ioskeha.hittite.isp.9tel.net [62.62.156.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3F6B743D4C for ; Thu, 3 Jun 2004 14:14:54 -0700 (PDT) (envelope-from cyrille.lefevre@laposte.net) Received: from mail.gits.dyndns.org (unknown [84.97.145.139]) by ioskeha.hittite.isp.9tel.net (Postfix) with ESMTP id D96F217BC6A for ; Thu, 3 Jun 2004 23:15:51 +0200 (CEST) Posted-Date: Thu, 3 Jun 2004 23:14:09 +0200 (CEST) X-Envelope-To: Received: from gits.gits.fr.invalid (IDENT:0cqg9oo3wjd670us@localhost [127.0.0.1])i53LE9sc097183 for ; Thu, 3 Jun 2004 23:14:10 +0200 (CEST) (envelope-from cyrille.lefevre@laposte.net) Received: by gits.gits.fr.invalid (tmda-sendmail, from uid 0); Thu, 03 Jun 2004 23:14:08 +0200 (CEST) Date: Thu, 3 Jun 2004 23:14:02 +0200 To: FreeBSD SCSI subsystem mailing list Message-ID: <20040603211401.GA76459@gits.dyndns.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="qMm9M+Fa2AknHoGS" Content-Disposition: inline Organization: ACME X-Face: V|+c; 4!|B?E%BE^{E6); aI.[< Mail-Followup-To: cyrille.lefevre@laposte.net, freebsd-scsi@FreeBSD.org X-Delivery-Agent: TMDA/1.0.2 (Bold Forbes) X-Spam-Status: No, hits=-99.739 required=5 tests=UPPERCASE_25_50,USER_IN_WHITELIST X-Scanned-By: MIMEDefang 2.39 Subject: ahc recovery initiated X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jun 2004 21:14:55 -0000 --qMm9M+Fa2AknHoGS Content-Type: text/plain; charset=us-ascii Content-Disposition: inline the attached messages arrived while I was extracting a tar archive. any thoughts ? Cyrille Lefevre -- mailto:cyrille.lefevre@laposte.net --qMm9M+Fa2AknHoGS Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="messages.txt" Jun 1 15:37:39 gits syslogd: kernel boot file is /boot/kernel/kernel Jun 1 15:37:39 gits kernel: Copyright (c) 1992-2004 The FreeBSD Project. Jun 1 15:37:39 gits kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Jun 1 15:37:39 gits kernel: The Regents of the University of California. All rights reserved. Jun 1 15:37:39 gits kernel: FreeBSD 5.2-CURRENT #29: Mon May 31 01:35:59 CEST 2004 Jun 1 15:37:39 gits kernel: root@gits:/disk3/freebsd/current/obj/disk3/freebsd/current/src/sys/CUSTOM Jun 1 15:37:39 gits kernel: can't re-use a leaf (nsfbufs)! Jun 1 15:37:39 gits kernel: Preloaded elf kernel "/boot/kernel/kernel" at 0xc0821000. Jun 1 15:37:39 gits kernel: Preloaded userconfig_script "/boot/kernel.conf" at 0xc0821154. Jun 1 15:37:39 gits kernel: Preloaded elf module "/boot/modules/splash_bmp.ko" at 0xc08211a4. Jun 1 15:37:39 gits kernel: Preloaded elf module "/boot/modules/vesa.ko" at 0xc0821254. Jun 1 15:37:39 gits kernel: Preloaded splash_image_data "/boot/splash/daemon_640.bmp" at 0xc0821300. Jun 1 15:37:39 gits kernel: Preloaded elf module "/boot/modules/apm.ko" at 0xc0821358. Jun 1 15:37:39 gits kernel: Timecounter "i8254" frequency 1193182 Hz quality 0 Jun 1 15:37:39 gits kernel: CPU: Pentium/P55C (198.95-MHz 586-class CPU) Jun 1 15:37:39 gits kernel: Origin = "GenuineIntel" Id = 0x543 Stepping = 3 Jun 1 15:37:39 gits kernel: Features=0x8001bf Jun 1 15:37:39 gits kernel: real memory = 134217728 (128 MB) Jun 1 15:37:39 gits kernel: avail memory = 121712640 (116 MB) Jun 1 15:37:39 gits kernel: Intel Pentium detected, installing workaround for F00F bug Jun 1 15:37:39 gits kernel: random: Jun 1 15:37:39 gits kernel: VESA: v2.0, 4096k memory, flags:0x1, mode table:0xc07cd302 (1000022) Jun 1 15:37:40 gits kernel: VESA: Matrox Graphics Inc. Jun 1 15:37:40 gits kernel: npx0: [FAST] Jun 1 15:37:40 gits kernel: npx0: on motherboard Jun 1 15:37:40 gits kernel: npx0: INT 16 interface Jun 1 15:37:40 gits kernel: pcibios: BIOS version 2.10 Jun 1 15:37:40 gits kernel: apm0: on motherboard Jun 1 15:37:40 gits kernel: apm0: found APM BIOS v1.2, connected at v1.2 Jun 1 15:37:40 gits kernel: pcib0: at pcibus 0 on motherboard Jun 1 15:37:40 gits kernel: pci0: on pcib0 Jun 1 15:37:40 gits kernel: isab0: at device 7.0 on pci0 Jun 1 15:37:40 gits kernel: isa0: on isab0 Jun 1 15:37:40 gits kernel: atapci0: port 0xffa0-0xffaf,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 7.1 on pci0 Jun 1 15:37:40 gits kernel: atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at 0xffa0 Jun 1 15:37:40 gits kernel: atapci0: Reserved 0x8 bytes for rid 0x10 type 4 at 0x1f0 Jun 1 15:37:40 gits kernel: atapci0: Reserved 0x1 bytes for rid 0x14 type 4 at 0x3f6 Jun 1 15:37:40 gits kernel: ata0: at 0x1f0 irq 14 on atapci0 Jun 1 15:37:40 gits kernel: atapci0: Reserved 0x8 bytes for rid 0x18 type 4 at 0x170 Jun 1 15:37:40 gits kernel: atapci0: Reserved 0x1 bytes for rid 0x1c type 4 at 0x376 Jun 1 15:37:40 gits kernel: ata1: at 0x170 irq 15 on atapci0 Jun 1 15:37:40 gits kernel: pci0: at device 13.0 (no driver attached) Jun 1 15:37:40 gits kernel: pci0: at device 14.0 (no driver attached) Jun 1 15:37:40 gits kernel: ahc0: port 0xf800-0xf8ff mem 0xffbea000-0xffbeafff irq 11 at device 15.0 on pci0 Jun 1 15:37:40 gits kernel: ahc0: Reserved 0x1000 bytes for rid 0x14 type 3 at 0xffbea000 Jun 1 15:37:40 gits kernel: ahc0: [GIANT-LOCKED] Jun 1 15:37:40 gits kernel: aic7890/91: Ultra2 Wide Channel A, SCSI Id=7, 32/253 SCBs Jun 1 15:37:40 gits kernel: ahc1: port 0xfc00-0xfcff mem 0xffbeb000-0xffbebfff irq 9 at device 16.0 on pci0 Jun 1 15:37:40 gits kernel: ahc1: Reserved 0x1000 bytes for rid 0x14 type 3 at 0xffbeb000 Jun 1 15:37:40 gits kernel: ahc1: [GIANT-LOCKED] Jun 1 15:37:40 gits kernel: aic7880: Ultra Wide Channel A, SCSI Id=7, 16/253 SCBs Jun 1 15:37:40 gits kernel: cpu0 on motherboard Jun 1 15:37:40 gits kernel: orm0: