Disklabel Question

[Adrian Michael Nida]

Hey,

I'm trying to configure vinum to create a RAID 5 array out of the 5x500GB drives
that I have.  In order to do this, I have to use disklabel to mark each drive
with a "vinum" file system.  These are new drives and each has been `fdisk
-I`ed.  They show up as ad4, ad6, ad8, ad10, and ad12 on my system.

However, I'm running into a problem.  Every way I try to use disklabel ends up
in some error message.

First off:

leviathan# uname -a
DragonFly leviathan.labthug.com 1.11.0-DEVELOPMENT DragonFly 1.11.0-DEVELOPMENT
#0: Mon Aug 13 21:30:43 EDT 2007    
root at leviathan.labthug.com:/usr/obj/usr/src/sys/GENERIC  i386

leviathan# disklabel -r ad4
disklabel: bad pack magic number (label is damaged, or pack is unlabeled)
leviathan# disklabel -r ad4s0
disklabel: /dev/ad4s0: Unknown error: 0
leviathan# disklabel -r ad4s0c
disklabel: /dev/ad4s0c: Invalid argument
leviathan# disklabel -r ad4s1
disklabel: bad pack magic number (label is damaged, or pack is unlabeled)
leviathan# disklabel -r ad4s1c
disklabel: /dev/ad4s1c: Invalid argument

Prepending "/dev/" to the ad4* produces the same error messages.

disklabel -e produces some interesting error messages:

leviathan# disklabel -e /dev/ad4
disklabel: Operation not supported by device
leviathan# disklabel -e /dev/ad4s0
disklabel: ioctl DIOCGDINFO32: label magic number or checksum is wrong!
(disklabel or kernel is out of date?)
leviathan# disklabel -e /dev/ad4s0c
disklabel: /dev/ad4s0c: Invalid argument
leviathan# disklabel -e /dev/ad4s1
disklabel: ioctl DIOCGDINFO32: label magic number or checksum is wrong!
(disklabel or kernel is out of date?)
leviathan# disklabel -e /dev/ad4s1c
disklabel: /dev/ad4s1c: Invalid argument

As you can tell from the uname, I succesfully completed a:

`make buildworld && make buildkernel && make installkernel && make installworld
&& make upgrade`

cycle very recently.  I'm unsure why it still thinks my disklabel or kernel is
out of date.

What am I forgetting?

Thanks,

Adrian