From owner-freebsd-questions@FreeBSD.ORG Thu Jul 31 02:24:09 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 126CC1065684 for ; Thu, 31 Jul 2008 02:24:09 +0000 (UTC) (envelope-from derek@computinginnovations.com) Received: from betty.computinginnovations.com (mail.computinginnovations.com [64.81.227.250]) by mx1.freebsd.org (Postfix) with ESMTP id A02A98FC15 for ; Thu, 31 Jul 2008 02:24:08 +0000 (UTC) (envelope-from derek@computinginnovations.com) Received: from p28.computinginnovations.com (dhcp-10-20-30-100.computinginnovations.com [10.20.30.100]) (authenticated bits=0) by betty.computinginnovations.com (8.14.2/8.14.2) with ESMTP id m6V2O0O5044517; Wed, 30 Jul 2008 21:24:01 -0500 (CDT) (envelope-from derek@computinginnovations.com) Message-Id: <6.0.0.22.2.20080730212205.02530430@mail.computinginnovations.com> X-Sender: derek@mail.computinginnovations.com X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22 Date: Wed, 30 Jul 2008 21:23:54 -0500 To: "ghostcorps@gmail.com" From: Derek Ragona In-Reply-To: <48910D00.4070100@gmail.com> References: <48906509.4000201@gmail.com> <6.0.0.22.2.20080730152038.0258bd38@mail.computinginnovations.com> <489103DD.2010004@gmail.com> <6.0.0.22.2.20080730191952.0249ab50@mail.computinginnovations.com> <48910D00.4070100@gmail.com> Mime-Version: 1.0 X-Antivirus: avast! (VPS 080730-0, 07/30/2008), Outbound message X-Antivirus-Status: Clean X-Virus-Scanned: ClamAV 0.93.3/7894/Wed Jul 30 12:26:14 2008 on betty.computinginnovations.com X-Virus-Status: Clean X-ComputingInnovations-MailScanner-Information: Please contact the ISP for more information X-MailScanner-ID: m6V2O0O5044517 X-ComputingInnovations-MailScanner: Found to be clean X-ComputingInnovations-MailScanner-From: derek@computinginnovations.com X-Spam-Status: No Content-Type: text/plain; charset="us-ascii"; format=flowed X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-questions@freebsd.org Subject: Re: {Spam?} Re: {Spam?} Re: SCSI RAID on FreeBSD 7.0, where is the array? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Jul 2008 02:24:09 -0000 At 07:53 PM 7/30/2008, ghostcorps@gmail.com wrote: >Thanks for the quick reply! > >I created the array in the Adaptec BIOS and confirmed it with an XP >installer disk, which gave me the option to install to the array as I had >named it. > > >I have to apologise for not having the actual dmesg handy but identifies >the disks much like the example below, but with Seagate disks. > >It does not identify any striping or make any differentiation between the >discs other than the target id. >. > >da0 at ahd0 bus 0 target 2 lun 0 >da0: Fixed Direct Access SCSI-3 device da0: >320.000MB/s transfers (160.000MHz, offset 127, 16bit), Tagged Queueing Enabled >da0: 35074MB (71833096 512 byte sectors: 255H 63S/T 4471C) >da1 at ahd0 bus 0 target 4 lun 0 >da1: Fixed Direct Access SCSI-3 device da1: >320.000MB/s transfers (160.000MHz, offset 127, 16bit), Tagged Queueing Enabled >da1: 35074MB (71833096 512 byte sectors: 255H 63S/T 4471C) > > > >Regards > Are you seeing any aacd drives in the dmesg? This would be the device name for an advanced adaptec raid drive. -Derek >Derek Ragona wrote: >>At 07:14 PM 7/30/2008, ghostcorps@gmail.com wrote: >>>Hi Derek, >>> >>>As mentioned in my post, I have configured the Adaptec BIOS >>>(SCSIselect/HostRAID) to create a RAID0 array. >>> >>>The GENERIC Kernel natively-uses the 'ahd' adapter for this card, >>>http://www.freebsd.org/cgi/man.cgi?query=ahd&sektion=4&manpath=FreeBSD+7.0-RELEASE >>> >>> >>>dmesg does not post any errors, it recognised the card as ahd0, and >>>states that da0 & da1 are on that bus. I can not post the dmesg as the >>>NIC adapter needs to be patched once the OS is installed. I could find a >>>USB key and copy it over if you like, but there are no errors to consider. >>> >>>Regards >> >>What does dmesg show for da0 and da1? >> >>Did you actually create the array in the Adaptec RAID BIOS? If you did, >>with a stripped array I'd expect dmesg to only report da0 as the stripped >>compendium of both disks. >> >> -Derek >> >> >> >> >> >>>Derek Ragona wrote: >>>>At 07:56 AM 7/30/2008, >>>>ghostcorps@gmail.com wrote: >>>>>Hi all, >>>>> >>>>> >>>>>I am fighting the following hardware: >>>>> >>>>>MB: ASUS p5b-plus (NON vista edition) >>>>>Cpu: Core 2 duo 4600 >>>>>SCSI Card: Adaptec 39320 (Unused Dell OEM bought from ebay) >>>>>HDDs: 2xSeagate Cheetah 73.4 GB Ultra320 SCSI (posibly Dell OEM) >>>>> >>>>>Nb. The MB does not support PCI-X, but is backwards compatible to a >>>>>standard PCI slot. On recommendations I have limited the throughput on >>>>>the channels to 160mb. >>>>> >>>>>If you think any other pieces relevant let me know. >>>>> >>>>> >>>>>I think this is probably just an issue with my not knowing wtf I'm >>>>>doing, but to be optimistic lets assume the ahd module worked as there >>>>>are no errors in dmesg; which device do I install to? I can not see >>>>>see ahd0 in fdisk. >>>>> >>>>>There are alot of posts over the years reporting trouble with the >>>>>Dell(Adaptec/Seagate) combiniation. The funny thing is that I am >>>>>having none of these troubles; There are no panics, no dumps and no >>>>>lengthy pauses. It all seems fine, until I try to select the disk to >>>>>install to and I only have da0 or da1. >>>>> >>>>> >>>>> >>>>>Thanks for your time >>>> >>>>Have you defined an array? >>>> >>>>If you create the array in the adaptec BIOS you will see one large hard >>>>disk in FreeBSD. If you do not define an array in the adaptec BIOS you >>>>will see the individual SCSI drives as da0, da1, etc. >>>> >>>>The GENERIC kernel has all the typical SCSI and RAID adapters compiled >>>>in, so look at the dmesg output when you boot FreeBSD. >>>> >>>> -Derek >>>> >>>>-- >>>>This message has been scanned for viruses and >>>>dangerous content by MailScanner, and is >>>>believed to be clean. >>> >>> >>>-- >>>This message has been scanned for viruses and >>>dangerous content by MailScanner, and is >>>believed to be clean. > > >-- >This message has been scanned for viruses and >dangerous content by MailScanner, and is >believed to be clean. > -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.