From owner-freebsd-bugs Tue Oct 24 14:44:52 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 96B6C37B479 for ; Tue, 24 Oct 2000 14:44:49 -0700 (PDT) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id OAA10426; Tue, 24 Oct 2000 14:44:46 -0700 Date: Tue, 24 Oct 2000 14:41:58 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Rob deFriesse Cc: freebsd-bugs@FreeBSD.ORG Subject: Re: 4.1.1 install fails with diag: ffs_valloc: dup alloc In-Reply-To: <200010242143.RAA14248@chmls06.mediaone.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is often the result of having overlapping partitions. Recheck what you've done- also, it's an awfully big /usr with a teeny weeny / and /var. > > I am receiving the following diagnostic: > > > panic: ffs_valloc: dup alloc > > when attempting to install FreeBSD 4.1.1 on a machine with a Promise > Ultra 100 ATA-100 IDE PCI controller. > > I don't know much about the mobo except that it's a 233MHz PCI with an > AMI BIOS and 32Mb mem. It's fairly ancient. > > I connected an ATA-100 HD to the new controller (channel 1) and the > CDROM to the old IDE controller (channel 2) on the mobo. Both are > masters on their respective channels. > > I'm installing from a CD. I allocate about 15Gb to the FreeBSD slice > and use the A (automatic) option to assign partitions. The partitions > are: > > ad4s2a: 50Mb / > ad4s2b: 68Mb swap > ad4s2e: 20Mb /var > ad4s2f: 14255Mb /usr > > I get through the initial set of questions and sysinstall runs newfs. > However, it does not get through unpacking the tarballs. That is, the > diagnostic appears while unpacking the ports tarball. At this point > the install fails and it goes into the boot dialog. > > I have had the install fail in another way. I can't provide the exact > wording because it's impossible to reproduce. The gist of it is that > while it's unpacking a tarball, a form pops up indicating that a write > has failed. The message includes the value -1 (which kinda makes > sense, this being unix and all.) > > If I move the HD to the old IDE controller, I have no problem with > it. FreeBSD installs without a hitch. > > Could this be a problem with the combination of the Promise controller > and a large partition? > > Any help to get this working would be appreciated. > > Thank you, > Rob. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-bugs" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message