From owner-freebsd-questions Fri Dec 29 09:20:36 1995 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA01652 for questions-outgoing; Fri, 29 Dec 1995 09:20:36 -0800 (PST) Received: from hillae.com (hillae.hillae.com [204.213.232.57]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA01643 for ; Fri, 29 Dec 1995 09:20:27 -0800 (PST) Received: from haehub by hillae.com with uucp (Smail3.1.29.1 #3) id m0tVjNT-00013lC; Fri, 29 Dec 95 13:18 EST Received: by hillae.com; Fri, 29 Dec 95 11:48:08 Message-ID: Date: Fri, 29 Dec 95 11:48:08 From: Yankura David To: questions@freebsd.org Subject: More info on install problem X-Mailer: UGate [Ver. 2.02] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-questions@freebsd.org Precedence: bulk I've been making some more attempts to install FreeBSD v2.1 on my AMD 486/DX4 100MHz system and have come across something which might be part or all of the problem. I tried a <> installation instead of the <> one and followed this path: boot from floppy select custom installation select allocate disk space from menu select sd1(no existing partitions) for use by FreeBSD(Seagate st3283N 237MB drive w/1691 cyl, 5 hds, and 57 sectors/track avg). select option "A" - use entire disk for FreeBSD(leaving a true partition) This process creates a freebsd partition @ offset 57, size 485298, named sd1s1 w/flag "C" I then execute option "W" to save these changes. I select installation of the booteasy boot mgr. get msg that fdisk partition info written successfully. select label allocated disk partitions from menu select option "A" - Auto defaults for all: this creates partitions: sd1s1a / 32MB UFS Y sd1s1b 27MB SWAP sd1s1e /var 30MB UFS Y sd1s1f /usr 147MB UFS Y select option "W" to save these changes - are you sure - YES get the following msg: "WARNING! unable to swap to /dev/sd1s1b: device not configured" "this may cause the installation to fail at some point" "if you don't have a lot of memory." I then get another msg: "Unable to make new root filesystem on /dev/rsd1a!" "command returned status 1." Since my machine only has 8MB ram I wonder if this might be the cause of my installation problems. If I continue on with the installation I get the error that I have reported before during the creation of /bin: on the console session: "panic: bad dir" and on the 2nd screen: "/mnt: bad dir ino 157 at offset 677: mangled entry" As I mentioned before the ino# and offset# are different every time I try an installation. I have never seen any msgs like these when I use the <> installation. Any help or just insight as to what might be going on would be greatly appreciated. David Yankura dgy@hillae.com