Subject: Re: fsck problem
To: Colin Wood <cwood@ichips.intel.com>
From: Edward Seth Miller <esmiller@engin.umich.edu>
List: port-mac68k
Date: 08/20/1997 14:11:58
On Wed, 20 Aug 1997, Colin Wood wrote:

> Edward Seth Miller wrote:
> > 
> > I was running the Generic-SBC #32 kernel (since I have a Quantum drive) 
> > with the 1.2.1 binaries to test the SBC kernel out.  I found that it 
> > worked, so I pulled down the current-970601 binaries.  On the plus side, 
> > w and ps now work.  On the minus side, fsck seems to be a little bit 
> > different, in as much as it will not run at startup.  ("Unknown error; 
> > help!")  As a result, it automatically boots into single-user mode.
> 
> What happens when you manually fsck the disk when in single-user??  I've
> had trouble with the automatic fsck at boot time before, but it usually
> either hangs waiting in tsleep() or just panics for me (actually, it
> usually boots just fine, but the above have happened more than once).
> I've never received that particular error message before.  Is you
> /etc/fstab file correct?

The problem is that it needs the dev that needs to be fsck-ed to be 
specified; it doesn't just assume one like it used to.  The fstab appears 
to be in good shape... it looks like:

	/dev/sd0a
	/
	ufs
	rw 1 1
	/dev/sd0b
	none    swap    sw 0 0
	kern            /kern
	kernfs  rw 0 0
	proc            /proc
	procfs  rw 0 0

I'm assuming that the way it runs fsck at startup is essentially just 
invoking fsck -f.  At least, the way it fails is about the same...  (It 
says, "fsck [-dfnpy] [-b block] [-c level] [-m mode] filesystem ..." 
instead of running.)
 
> > 	Also, as it's starting the rpc daemons, specifically ypbind, it 
> > says "ypbind: Domainname not set. Aborting.".  This is a new error, and 
> > while I'm not sure what it's affecting, I wouldn't mind knowing how to 
> > fix it...
> > 	Does anybody have any suggestions on how to get around these?
> 
> You can create a file called /etc/mydomain (it might exist already) and
> put something silly in it like 'mydomain.dom', or perhaps something more
> useful like your real domain name if you have one.

It seemed to be missing, although I've added it and it still doesn't 
work.  What is the format for that file?  (i.e. what should it consist 
of?  It seems to be absent from the man pages...)

> Of course, this raises the question:  why in the world are you running
> ypbind???  Do you have your own intranet?  If you have only one machine,
> and it's not tied into a network that you can share passwd and mail alias
> information with, there is no good reason to run ypbind.  You can turn it
> off by changing the flags in /etc/rc.conf (assuming you upgraded your /etc
> files to -current as well as everything else, otherwise I think you have
> to edit either /etc/rc or /etc/netstart).

Since I'm attached to the University of Michigan ethernet, it seems like 
I may need that stuff in the not too distant future...  That's why I'd 
rather it was working.

> 
> I hope this helps.

Well, we'll see...  Thanks...

	-Seth Miller