raid1: unable to open device, error = 16

[Edgar Fuß <ef%math.uni-bonn.de@localhost>]

Now this is strange.

I built raid1 on dk0..dk5.

I gpt'd raid1.

I raidctl -u raid1 and raidctl -c /etc/raid1.conf raid1, and the wedges were 
auto-detected as expected (XXXX'd the GUID and GPT names):

raid1: Components: /dev/dk0 /dev/dk1 /dev/dk2 /dev/dk3 /dev/dk4
raid1: Total Sectors: 23437491200 (11444087 MB)
raid1: GPT GUID: XXXX
dk5 at raid1: XXXX
dk5: 12884901888 blocks at 2048, type: ffs
dk6 at raid1: XXXX
dk6: 6442450944 blocks at 12884903936, type: ffs
dk7 at raid1: XXXX
dk7: 1073741824 blocks at 19327354880, type: ffs
dk8 at raid1: XXXX
dk8: 2097152 blocks at 20401096704, type: ffs
dk9 at raid1: XXXX
dk9: 268435456 blocks at 20403193856, type: ffs
dk10 at raid1: XXXX
dk10: 268435456 blocks at 20671629312, type: ffs
dk11 at raid1: XXXX
dk11: 1073741824 blocks at 20940064768, type: ffs

I newfs'd dk5..8.

I then tried gpt show -l raid1, which now said:
gpt: unable to open device 'd': No such process
(before all of the newfs's, gpt show wowrked)

I unconfigured and re-configured raid1, and now the wedges were NOT 
auto-detected, instead, I get:

raid1: Components: /dev/dk0 /dev/dk1 /dev/dk2 /dev/dk3 /dev/dk4
raid1: Total Sectors: 23437491200 (11444087 MB)
raid1: unable to open device, error = 16

I now get the following inconsistent results from disklabel/mbr/gpt):

disklabel raid1: OK
disklabel -r raid1: could not read existing label (as expected)
fdisk raid1: OK (apart from fdisk: Cannot determine the number of heads)
gpt show raid1: gpt: unable to open device 'd': No such process
gpt show rraid1: gpt: unable to open device '1d': No such process
gpt show /dev/raid1: gpt: unable to open device 'raid1d': No such process
gpt show /dev/rraid1: OK (all the partitions are still there)

I can manually add (dkctl addwedge) dk5 and successfully mount it.

It's 6.0_BETA2/amd64 in case it matters.

I'll try to re-boot.