Can't use more than 30GB on 80GB drive, almost...

["Nathan Sharfi" <nisharfi@tstonramp.com>]

I recently installed an 80GB Maxtor DiamondMax 6L080J4 as a slave drive in
my Abit BM6. However, when I followed the instructions in the FAQ to set it
up, I only got a reported capacity of 30GB from df -h. First off, I did sudo
fdisk -i wd1:

Only LBA values are valid in ending cylinder for partition #3.

        -----------------------------------------------------
        ------ ATTENTION - UPDATING MASTER BOOT RECORD ------
        -----------------------------------------------------

Do you wish to write new MBR? [n] y
Cylinder values are modified to fit in CHS.

Next, I did the disklabel song and dance with -E:

comatoast@dymaxion: ~> sudo disklabel -E wd1
Password:
# using MBR partition 3: type A6 off 63 (0x3f) size 156340737 (0x9519201)

Treating sectors 63-156340800 as the OpenBSD portion of the disk.
You can use the 'b' command to change this.

Initial label editor (enter '?' for help at any prompt)
> p
device: /dev/rwd1c
type: ESDI
disk: ESDI/IDE disk
label: MAXTOR 6L080J4
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 16
sectors/cylinder: 1008
cylinders: 16383
total sectors: 156355584
free sectors: 90296640
rpm: 3600

16 partitions:
#        size   offset    fstype   [fsize bsize   cpg]
  a: 66044097       63    4.2BSD     1024  8192    16   # (Cyl.    0*-
65519)
  c: 66055248        0    unused        0     0         # (Cyl.    0 -
65530)
> d a
> a a
offset: [63]
size: [156340737]
FS type: [4.2BSD]
> w
> q
No label changes.
comatoast@dymaxion: ~>

(I had already done this step, and wanted to replay it, so "No label
changes" doesn't surprise me.)
Next, newfs:

comatoast@dymaxion: ~> sudo newfs wd1a
Warning: 64 sector(s) in last cylinder unallocated
/dev/rwd1a:     156340736 sectors in 155100 cylinders of 16 tracks, 63
sectors
        76338.2MB in 9694 cyl groups (16 c/g, 7.88MB/g, 1920 i/g)
super-block backups (for fsck -b #) at:
 32, 16224, 32416, 48608, 64800, 80992, 97184
...more stuff...
 156264800, 156280992, 156297184, 156313376, 156329568,
comatoast@dymaxion: ~>

now, to mount it on /u (I already made the dir)

comatoast@dymaxion: ~> sudo mount /dev/wd1a /u

and to check drive capacity:

comatoast@dymaxion: ~> df -h
Filesystem    Size   Used  Avail Capacity  Mounted on
/dev/wd0a     997M    20M   926M     2%    /
/dev/wd0d     494M   8.8M   460M     2%    /var
/dev/wd0e     1.9G   967M   919M    51%    /usr
/dev/wd0f     5.8G   5.0G   541M    90%    /home
/dev/wd0g      17G    16G    80M   100%    /opt
/dev/wd1a      72G   1.0K    69G     0%    /u

(insert cursing here.)

I must have done the SAME procedure multiple times; what could have
magically whacked OpenBSD over the head to recognize all the drive space? I
got measurements of 30G for /u several times; what could I have overwritten?