gvinum causing kernel panic when referencing nonexistent partition

[Jason Andresen]

I have a machine that I tried upgrading from 4-STABLE to 5-STABLE.  In 
the process I lost one of the disks and had to replace it.  The problem 
is, that gvinum "knows" about the disk, but I can't seem to either 
create the media volume (kernel panic) nor erase that entry from the 
vinum list (kernel panic).

I also can't seem to get resetconfig to work--it doesn't seem to be 
defined in gvinum :(.

All I need to do is clear media.p0.s3 out of this and I think I'll be 
able to recreate the volume I need (including grabbing the new disk):

gvinum -> list
9 drives:
D media1                State: up       /dev/ad6s1      A: 76316/76316 
MB (100%)
D media3                State: up       /dev/ad8s1      A: 76316/76316 
MB (100%)
D media9                State: up       /dev/ad10s1     A: 76316/76316 
MB (100%)
D media2                State: up       /dev/ad12s1     A: 76316/76316 
MB (100%)
D mediaa                State: up       /dev/ad14s1     A: 76316/76316 
MB (100%)
D media5                State: up       /dev/ad16s1     A: 76316/76316 
MB (100%)
D media6                State: up       /dev/ad18s1     A: 76316/76316 
MB (100%)
D media8                State: up       /dev/ad20s1     A: 76316/76316 
MB (100%)
D media7                State: up       /dev/ad22s1     A: 76316/76316 
MB (100%)

1 volume:
V media                 State: up       Plexes:       0 Size:          0  B

1 plex:
P media.p0           R5 State: down     Subdisks:     0 Size:          0  B

1 subdisk:
S media.p0.s3           State: up       D: media4       Size:         74 GB

Is there maybe a special place on each drive I could dd /dev/zero to 
clear out all of the vinum information?  I tried clobbering the vinum 
slices on every drive and newfsing them as individual filesystems, but 
that didn't seem to do the trick.