> > I labeled my new disk as follows.  It would fsck and mount and
> > service me until I rebooted.  After reboot I can do nothing without
> > it complaining that it cannot read the last super block tha newfs
> > created.
> 
> This sounds to me as though the end of the partition you're newfsing -
> the a partition, in this case - overlaps something else and keeps
> getting written over.  Maybe it overlaps the beginning of your swap
> area, maybe it overlaps something else...check the partitioning on that
> drive.
> 
> Also, you say the label is getting trashed, but it sounds more as
> though the label is just fine, but the filesystem is being damaged.

I experienced a similar problem when I disklabeled my second SCSI
disk. After disklabeling everything worked fine - until a reboot! The
problem was that the kernel somehow did'nt have the same disklabel as the
actual disk had (I told disklabel to list the raw disklabel, and everything
was fine). I don't know if this is a problem with the kernel, or my
disklabeling process.

The problem got fixed when I disklabel'ed the partition on the disk as
well. I don't know if this is the correct way of doing things, but the
kernel now reads the correct disklabel.

But I am still not able to mount my MS-DOS partition on that disk :( Any
ideas?

Bye,
-- 
Geir Inge Jensen                               Department of Computer Science
                                               University of Tromsų, Norway
SMTP : geiri@staff.cs.uit.no
URL  : http://www.cs.uit.no/~geiri/            Phone: +47 77 64 57 47