According to William R. Dickson:
>
>Speaking of which, I had a fight with fsck last night myself.  So far,
>it's still winning.  Essentially, mount keeps telling me that /dev/sd0a
>isn't clean, and that I should run fsck(8).  So I boot into single-user
>mode, do an fsck -f, it chugs away, and happily marks both my filesystems
>clean.  I then try to mount the drives, and mount again tells me that
>/dev/sd0a isn't clean.
>

Hmmm it sounds suspiciously like /dev/sd0a is your / partition - is
this the case?

If it is then you have a couple of choices.  One is to boot up from
the install floppies and see if fsck is on them somewhere (I cannot
remember if it is or not...) and use this to fsck the partition.  The
alternative is to boot to single user, do the fsck and then hit the
reset switch - do not shutdown or sync the disks in any way, otherwise
you will write the in-core superblock back to disk after fsck has
carefully modified the on-disk copy and you will be back where you
were when you started.  You need only do this for disks that you
cannot fsck in the unmounted state.

-- 
Brett Lymn, Computer Systems Administrator, AWA Defence Industries
===============================================================================
  "Upgrading your memory gives you MORE RAM!" - ad in MacWAREHOUSE catalogue.