From owner-freebsd-questions Mon Oct 23 10:53:16 2000 Delivered-To: freebsd-questions@freebsd.org Received: from chmls05.mediaone.net (chmls05.mediaone.net [24.147.1.143]) by hub.freebsd.org (Postfix) with ESMTP id E5D6037B661 for ; Mon, 23 Oct 2000 10:53:12 -0700 (PDT) Received: from mediaone.net (h00104b44180b.ne.mediaone.net [24.91.120.32]) by chmls05.mediaone.net (8.8.7/8.8.7) with SMTP id NAA18554 for ; Mon, 23 Oct 2000 13:53:06 -0400 (EDT) Date: Mon, 23 Oct 2000 13:53:06 -0400 (EDT) From: robdefriesse@mail.com Message-Id: <200010231753.NAA18554@chmls05.mediaone.net> To: freebsd-questions@FreeBSD.ORG Subject: Can't install FBSD on system with Promise ATA-100. Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I recently acquired a Promise ATA-100 controller and an ATA-100 compatible hard drive. I put these into an old computer that my brother gave me. 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 acient, though. I connected the 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 am unable to install FreeBSD 4.1.1. 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. The diagnostic is terse, but here it is: > panic: ffs_valloc: dup alloc > > syncing disk... 86 86 86 86 17 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 > done > Uptime 8m15s > Automatic reboot... This occurs while unpacking the ports tarball. At this point 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 hard 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? What do I do now? Should I submit a bug report? If so, is there any way I can provide more information? I would be grateful if someone would tell me how to proceed. Thank you, Rob. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message