*BSD News Article 31559


Return to BSD News archive

Newsgroups: comp.unix.bsd
Path: sserve!newshost.anu.edu.au!munnari.oz.au!hippo.ru.ac.za!Braae!g89r4222
From: csgr@cs.ru.ac.za (Geoff Rehmet)
Subject: Re: AHA 1542CF + Maxtor 1240S no good for FreeBSD?
Message-ID: <Cr588F.J86@hippo.ru.ac.za>
Sender: news@hippo.ru.ac.za (Usenet News Admin)
Reply-To: csgr@cs.ru.ac.za
Organization: Rhodes University, Grahamstown, South Africa
References: <2t7038$a1a@newsserv.cs.sunysb.edu>
Date: Thu, 9 Jun 1994 18:48:14 GMT
Lines: 44

In <2t7038$a1a@newsserv.cs.sunysb.edu> cchen@cs.sunysb.edu (temp acct to clean dir) writes:

>Hello, world,

>I'm having endless troubles trying to install FreeBSD 
>with the above combo.  The problem I'm getting is that
>when the installation procedure prompts me asking for
>the hard disk type, and I type scsi, it will print
>"uid 0, /: file system full
>  Hm, ... Sare you sure it's a scsi?(something like that)"

>And of course nothing will be written to the root file system
>if I tell the system to keep going.
>Has anyone tried the above combo?  I tried various disk
>geometries, 1024, 64, 32, etc.  But nothing worked.

I'm not sure if you may be having the same problem which I had
yesterday, while installing FreeBSD on a system with a 1542CF and
a 1.9G seagate hard disk.  Because the system also has DOS and 
Netware 4.0 installed on it (it's our system for networking
experimentation) I had to use the translation geometry which the
controller uses for DOS, which is something really rediculous like
134 cyls, 255 heads and 63 sects/cyl !!!!! ;-) 
Anyhow, I could label the disk OK, but newfs failed, moaning that
the parameters given to it wouldn't work.
I eventually managed to manually newfs the disk - the filesystem is
still suboptimal because the geometry is really lousy for a UFS.
When I tried the install again, I got errors that the root filesystem
was full - I found that was due to the install script trying to start
the install onto the filesys floppy after failing to mount the
filsystems which could not be newfs'd.  I eventually managed to get
the thing to work.

I'm still trying to think of a workaround for this, but haven't really
managed to think of anything.  We need somehow to see beforehand that
newfs is not going to like the stupid disk geometry, and do something
about that.  I'd welcome any suggestions!

Geoff.
--
 Geoff Rehmet, Computer Science Department,   | ____   _ o         /\
  Rhodes University,  South Africa            |___  _-\_<,        / /\/\
 FreeBSD core team                            |    (*)/'(*)    /\/ /  \ \
     csgr@cs.ru.ac.za, csgr@freefall.cdrom.com, geoff@neptune.ru.ac.za