Date: Wed, 25 Oct 2000 23:03:44 -0700 (PDT) From: Matthew Jacob <mjacob@feral.com> To: Rob deFriesse <robdefriesse@mail.com> Cc: freebsd-bugs@FreeBSD.ORG Subject: Re: 4.1.1 install fails with diag: ffs_valloc: dup alloc Message-ID: <Pine.BSF.4.21.0010252258390.7350-100000@beppo.feral.com> In-Reply-To: <200010251741.NAA22905@chmls06.mediaone.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> Thank you for your response. > > > 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'm using the FDISK partion editor and the FreeBSD disklabel editor to > define these slices and partitions. These are the utilities that are > invoked during the install process. Neither editor allows me to > specify where slices or partions are placed nor does the partition > editor display the starting sector of each partion. Therefore, I have > to count on them to get this right. Hmm? The FDISK program allows one to set the slices. The partition sets are within a slice. But you're right- I forgot- with the install stuff it just gives you sizes as you lay things out. > In the case of the partition editor, I used the A (automatic) option > to assign partitions. Do you recommend that I override the automatic > assignment? Well- yes. Don't do the 'defaults' - they don't look sensible. When creating a set of partitions for such a big disk, give yourself a couple hundred meg for the root, an equally generous swap area. You can leave yourself 15GB of /usr if you want. I'm wondering what the problem really is, though. It might be that the geometry being reported by the BIOS is just plain wrong- but I don't know enough about how the current label stuff interacts with this to know what to look for- somebody more on top of that should step in and answer that. > > Keep in mind that I used the exact same slice and partition > configuration without the Promise card and had no problem whatsoever > with the installation. > > > > > > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0010252258390.7350-100000>