*BSD News Article 81695


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.cs.su.oz.au!metro!metro!munnari.OZ.AU!news.ecn.uoknor.edu!news.wildstar.net!news.ececs.uc.edu!newsrelay.netins.net!newsfeed.dacom.co.kr!arclight.uoregon.edu!nntp.primenet.com!howland.erols.net!mathserv.mps.ohio-state.edu!newsfeed.acns.nwu.edu!news.cc.uic.edu!bert.eecs.uic.edu!onevarez
From: Oswaldo Nevarez <onevarez@bert.eecs.uic.edu>
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: couldn't get root image from cd0a???
Date: Fri, 25 Oct 1996 11:25:00 -0500
Organization: University of Illinois at Chicago
Lines: 32
Message-ID: <Pine.SUN.3.95.961025104412.9835A-100000@bert.eecs.uic.edu>
Reply-To: Oswaldo Nevarez <onevarez@bert.eecs.uic.edu>
NNTP-Posting-Host: bert.eecs.uic.edu
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

choosing the novice option at the installation menu I go create a FREEBSD
slice and lable it.  Then I go choose cdrom as the media.  It starts
copying the initial files but when it goes to get the root image it tells
me "couldn't get root image from cd0a.  So then I reboot start over and
choose MSDOS as the media.  With all the correct files and directories
already made.  This time I get "couldn't get root image from sd0s1.  So
then I say forget the novice set up, being that I've installed Linux
before.  So I go into custom and create the FREEBSD slice, then lable it.
Choose the media and distribution files.  Then instead of commit I go
choose Extract only.  This time I get "/:create/symlink failed, no inodes
free, unable to make node for /dev/sd0s2b in /dev"

Another strange thing is that sometimes when I go create a FREEBSD slice
it uses all the remaining hard drive about 390MB but when I go lable it
the last slice shows up as 5378MB, which is impossible. So I delete the
FREEBSD slice and create it again this time it doesn't entire disk but
leave an unused slice ,after the FREEBSD slice, of size 0. Now the lables
work fine. But the above problem persists.

Does anybody have a clue as to what is or might be going on?  Is my hard
drive the problem( Conner, SCSI).

By the the I checked out the probing messages and there arre no errors
both the hard drive and cdrom are identified correctly.


Oswaldo Nevarez            /////////////  //\        ////
                          ////     ////  ////\\     ////
onevarez@eecs.uic.edu    ////     ////  ////  \\\  ////
                        ////     ////  ////     \\////  
                       /////////////  ////        \//