From owner-freebsd-questions@FreeBSD.ORG Thu Nov 8 18:10:10 2007 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 09F7616A41B for ; Thu, 8 Nov 2007 18:10:10 +0000 (UTC) (envelope-from jaikat@email.unc.edu) Received: from smtp.unc.edu (smtpsrv1.isis.unc.edu [152.2.1.140]) by mx1.freebsd.org (Postfix) with ESMTP id C558213C4B8 for ; Thu, 8 Nov 2007 18:10:07 +0000 (UTC) (envelope-from jaikat@email.unc.edu) Received: from [152.23.75.195] (dhcp29913.wireless.unc.edu [152.23.75.195]) (authenticated bits=0) by smtp.unc.edu (8.13.4/8.13.4) with ESMTP id lA8I9JBR005620; Thu, 8 Nov 2007 13:09:19 -0500 (EST) Message-ID: <473350CD.3060600@email.unc.edu> Date: Thu, 08 Nov 2007 13:09:17 -0500 From: Jay Aikat Organization: University of North Carolina at Chapel Hill User-Agent: Thunderbird 1.5.0.13 (Windows/20070809) MIME-Version: 1.0 To: Jay Aikat References: <473329C6.1050505@email.unc.edu> <20071108154838.GA659@owl.midgard.homeip.net> <47333571.1080701@email.unc.edu> <20071108162224.GA1283@owl.midgard.homeip.net> <47334400.5010208@email.unc.edu> In-Reply-To: <47334400.5010208@email.unc.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: 6.1 install and multiple drives 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, 08 Nov 2007 18:10:10 -0000 Just an update to this (my own) question below. Turns out the mfi_ioctl.h file is not listed as an updated one in the list below, but I needed to change that file as well. So, I copied that from the 6.2 distribution as well, and then the kernel compiled fine. Even better, I was then able to, with the new kernel installed, fdisk and label my other 7 drives - no problems! Thanks to Erik and this very helpful list! --Jay. Jay Aikat wrote: > Erik, > Thanks. I used the CVS repository directly. It turns out that that > still has the old versions of these files for 6.1. So, I grabbed the > files for 6.2 instead and compiled them into my kernel. Doesn't work. > Error included below for reference. > > Would you know if there is someone I could contact to get the 6.1 > updates for these files, if it is not in the repository? Thanks, > > Error in make: > ./../dev/mfi/mfi.c > ../../../dev/mfi/mfi.c: In function `mfi_ioctl': > ../../../dev/mfi/mfi.c:1824: error: storage size of 'l_ioc' isn't known > ../../../dev/mfi/mfi.c:1824: warning: unused variable `l_ioc' > ../../../dev/mfi/mfi.c:1845: error: storage size of 'l_aen' isn't known > ../../../dev/mfi/mfi.c:1845: warning: unused variable `l_aen' > ../../../dev/mfi/mfi.c: In function `mfi_linux_ioctl_int': > ../../../dev/mfi/mfi.c:1876: error: storage size of 'l_ioc' isn't known > ../../../dev/mfi/mfi.c:1877: error: storage size of 'l_aen' isn't known > ../../../dev/mfi/mfi.c:1894: error: `MAX_LINUX_IOCTL_SGE' undeclared > (first use in this function) > ../../../dev/mfi/mfi.c:1894: error: (Each undeclared identifier is > reported only once > ../../../dev/mfi/mfi.c:1894: error: for each function it appears in.) > ../../../dev/mfi/mfi.c:1994: error: dereferencing pointer to incomplete > type > ../../../dev/mfi/mfi.c:1876: warning: unused variable `l_ioc' > ../../../dev/mfi/mfi.c:1877: warning: unused variable `l_aen' > *** Error code 1 > > --jay. > > > Erik Trulsson wrote: >> On Thu, Nov 08, 2007 at 11:12:33AM -0500, Jay Aikat wrote: >>> Erik, >>> Thanks a ton for this info! One more (this rather lame) question >>> - sorry. Where can I download the latest files for this mfi driver >>> from? The ftp archive for old releases does not seem to have this. >>> ftp://ftp-archive.freebsd.org/pub/FreeBSD-Archive/old-releases/i386/6.1-RELEASE >>> >>> >>> Thanks! >>> --Jay. >>> >> >> (The FTP archive should have all the files, but probably not in a format >> that can be easily accessed without first installing the release.) >> >> You can always get any version of the source files directly from the CVS >> repository. See http://www.freebsd.org/developers/cvs.html for >> information >> on that. >> >> You might also get away with simply copying the files (either source >> or the >> pre-compiled kernel module) from 6.2-RELEASE >> There is no guarantee that this will work (since the updated driver might >> depend on some other changes) but it might be worth a try. >> >> >>> Erik Trulsson wrote: >>>> On Thu, Nov 08, 2007 at 10:22:46AM -0500, Jay Aikat wrote: >>>>> I am trying to install FreeBSD 6.1 on a Dell Poweredge 2900 which >>>>> has an Intel dual-core processor, and 8 drives on a SATA backplane, >>>>> connected to a PERC 5i controller. They are setup as just a bunch >>>>> of disks, and not raided. >>>>> >>>>> Here's the issue: >>>>> -- 6.2 installs fine (but I need 6.1 for some hardware we installed >>>>> on this machine that only works with 6.1, not 6.2) >>>>> >>>>> -- 6.1 install fails with a vm-fault error after starting to write >>>>> to disk0 (if all 8 drives have been fdisked and labeled). >>>>> >>>>> -- 6.1 installs fine if I fdisk and label only the drive0 (mfid0) >>>>> >>>>> But after installing 6.1 using only one drive, if I then run >>>>> sysinstall to add more drives, fdisk works fine, but when I run >>>>> label, and then "write" it crashes, and then I can't even boot into >>>>> the disk0 b/c its partitions have become corrupted. >>>>> >>>>> What seems to be happening is that "label" somehow seems to be >>>>> duplicating the /var partition in disk0 into the disk1 partition. >>>>> Then if I add disk2, label seems to be duplicating the disk1 >>>>> partition onto disk2. (this duplication problem I discover when I >>>>> try to label outside of sysinstall). >>>>> >>>>> Has anyone seen this bizarre behavior - seems like a bug in >>>>> bsdlabel in 6.1 - not sure. Any help or suggestions are highly >>>>> appreciated. Thanks, >>>>> --jay. >>>>> >>>> I think I remember seeing a similar bugreport in the past. If I >>>> remember >>>> correctly it was a bug in the driver for the disk controller. >>>> The commit entry quoted below was likely the one which fixed the >>>> problem >>>> (it was merged to 6-STABLE a couple of weeks later.) >>>> As you can see from the date it was made after 6.1 was out, but before >>>> 6.2 was out, so it is not surprising 6.2 works while 6.1 does not. >>>> ps 2006-06-20 22:41:44 UTC >>>> FreeBSD src repository >>>> Modified files: >>>> sys/dev/mfi mfi.c mfi_disk.c mfi_pci.c mfireg.h >>>> mfivar.h >>>> Log: >>>> Instead of using scsi probes to do device discovery, use the >>>> firmware >>>> commands to grab the device listing. This resolves issues using >>>> multiple volumes, where each volume was actually internally >>>> pointing >>>> to target 0. >>>> Revision Changes Path >>>> 1.11 +77 -202 src/sys/dev/mfi/mfi.c >>>> 1.4 +3 -9 src/sys/dev/mfi/mfi_disk.c >>>> 1.3 +1 -0 src/sys/dev/mfi/mfi_pci.c >>>> 1.3 +96 -0 src/sys/dev/mfi/mfireg.h >>>> 1.3 +1 -3 src/sys/dev/mfi/mfivar.h >>> _______________________________________________ >>> freebsd-questions@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >>> To unsubscribe, send any mail to >>> "freebsd-questions-unsubscribe@freebsd.org" >>