*BSD News Article 7979


Return to BSD News archive

Newsgroups: comp.unix.bsd
Path: sserve!manuel.anu.edu.au!munnari.oz.au!spool.mu.edu!sdd.hp.com!ux1.cso.uiuc.edu!news.cso.uiuc.edu!uxa.cso.uiuc.edu!jwp20406
From: jwp20406@uxa.cso.uiuc.edu (Jeffrey Palmer)
Subject: [386bsd] Second drive problems... losing disklabel
Message-ID: <By42Bo.G02@news.cso.uiuc.edu>
Sender: usenet@news.cso.uiuc.edu (Net Noise owner)
Organization: University of Illinois at Urbana
Date: Sun, 22 Nov 1992 09:28:33 GMT
Lines: 53

Hello all,

	I just received a new hard drive, and am anxious
to get it up and running under 386bsd.  Unfortunately, I seem
to be beating my head against a wall trying to get this thing
to work.  I created a disktab entry for my desired partitions,
and attempted to disklabel the disk.  Everything is fine and dandy,
I can newfs the partitions nd even mount them, but when I reboot,
it seems as though the disklabel gets lost somewhere.  When I 
do a disklabel just from memory, it only gives me a single bogus
partition.  When I try to mount something on this drive directly
after booting in this condition, I get the following error:

kramer # mount /dev/wd1a /mnt
/dev/wd1a on /mnt: Bogus super block

If I do a disklabel -r wd1 at this point, I get the following:

....
8 partitions:
#        size   offset    fstype   [fsize bsize   cpg]
  a:    15960        0    4.2BSD     1024  8192     0   # (Cyl.    0 - 37)
  b:    33600    15960      swap                        # (Cyl.   38 - 117)
  c:   415380        0    unused        0     0         # (Cyl.    0 - 988)
  d:   415380        0    unused        0     0         # (Cyl.    0 - 988)
  g:    74340   341040    4.2BSD     1024  8192     0   # (Cyl.  812 - 988)
  h:   291480    49560    4.2BSD     1024  8192     0   # (Cyl.  118 - 811)


	which is just what I wanted... In fact, if I try to mount
now, after the disklabel has been read into the kernel, everything works
great... It just seems as though the disklabel is never being read in.
I have looked through the FAQ, and didn't see anything helpful.  I don't
have a problem recognizing the drive, just getting it to load
its information into the kernel.  

	I am running on a Gateway 2000 486/50, with an ati graphics ultra,
X up and running, recompiled kernel with everything (I thought).

	So, I guess I would really appreciate some help, if someone knows
the answer to this (hopefully very easy) problem, please let me know.
Sorry if this is a FAQ.

	Thanks!




-- 
Jeffrey Palmer                palmer@cs.uiuc.edu
------------------------------------------------
for life's not a paragraph
And death i think is no parenthesis