Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!network.ucsd.edu!usc!sol.ctr.columbia.edu!eff!enterpoop.mit.edu!eru.mt.luth.se!lunic!sunic!isgate!veda.is!adam From: adam@veda.is (Adam David) Newsgroups: comp.os.386bsd.questions Subject: Re: install problems (desparate) Message-ID: <C5MGp8.K69@veda.is> Date: 17 Apr 93 09:51:08 GMT References: <match.17.735012627@civil.utah.edu> Organization: Veda Systems, Iceland Lines: 20 match@civil.utah.edu (Marvin Match) writes: >new dist.fs boots (says it's version 0.1.44 I think, or is it 0.1.24) >and I can run install. Upon completion, the machine says to remove the >floppy, and hit return to boot off the hard drive. When I do that, I get >endless messages scrolling off of the screen, the likes of "386 bsd not >installed" or "can't find 386bsd. trying vmunix" or some such. (hard to >tell, it all goes by so fast) The .44 or .24 doesn't necessarily mean anything useful. When you are booting from the hard disk, the bootblocks are obviously found but the 386bsd kernel binary is not found. By far the most common cause of this is a knackered filesystem. You could try booting from the fixit floppy and and run fsck on the boot partition of the hard disk (probably /dev/as0a). Of course, if the root filesystem is somewhere else than where the bootblock expects it to be, then this will probably not help either. -- Adam D. (adam@veda.is)