Return to BSD News archive
Xref: sserve comp.os.386bsd.misc:1321 comp.os.386bsd.questions:6169 Path: sserve!newshost.anu.edu.au!munnari.oz.au!ariel.ucs.unimelb.EDU.AU!ucsvc.ucs.unimelb.edu.au!lugb!latcs1!wongm Newsgroups: comp.os.386bsd.misc,comp.os.386bsd.questions Subject: FreeBSD installation problem [still unsuccessful!] Message-ID: <CFGELv.1Hv@latcs1.lat.oz.au> From: wongm@latcs1.lat.oz.au (M.C. Wong) Date: Mon, 25 Oct 1993 12:56:18 GMT Organization: Comp Sci, La Trobe Uni, Australia Lines: 57 Hi, During my last installation of FreeBSD, I got to the step where I ahve finished with 3rd floppy, ie cpio-floppy, and let FreeBSD boot itself up off the hard disk (wd0), upon the first boot, it complains about 4 fsck errors as is mentioned in install notes, and boots itself up for the 2nd time, and supposed to be with a clean filesystem this time, but I got the following error messages. Automatic reboot in progress ... Bus error Unkown error in reboot Automatic reboot in progress ... Bus error Unkown error in reboot . . . [repeated!] ANd I realized where the problem was, ie fsck -p in .profile! So, I experimented booting up from kcopy-aha-floppy, and did fsck on /dev/wd0a and /dev/wd0e, and the conclusion is sometimes fsck fails, sometimes it doesn't. But most of the time when I boot up from hard disk, the fsck fails quite often, so I copy the fsck from kcopy-aha-floppy, and try it out and the conclusion was as before, sometimes it works, sometimes it complaints a Bus error (core dumped). I figured out that when the / is still read-only, a core dumped is not possible, and I am left with ambiguous error of Bus error, looks very much like hardware problem! So, I finally get to the point to copy a new fsck onto my FreeBSD /sbin, and let boot up use the new (fresh) fsck does its job, and I read in all of the binary and source distribution, and get them extracted in to proper places. But when I start up the system, I still have the following 2 problems : 1) fsck complains about Bus error, looks like transient problem to me , why ? Can I make this problem go away permanently ? 2) Upon starting up network (from /etc/rc), I get a panic message : Starting network vm_fault (fe11e0000, fe345000, 3, 0)->1 type c, code 2 trap type 12 code = 2 eip = fe02287d cs = 8 eflags = 10202 cr2 fe345000 cpl 1a panic : trap Syncing disks ... I tried rebooting a few times, but I keep getting problem 2), can someone help please ? Well, I have been persistent enough to stay up with FreeBSD so far, and I hope you guys can just get me onto the right path, by baring with my unsuccessful installtion, and I will be right! Thanks in advance, and email replies please! - wongm@latcs1.lat.oz.au (M.C Wong) -- - wongm@latcs1.lat.oz.au