Clue bat to spare, anybody?

ksh$ raidctl -S raid4
raidctl: unable to open device file: raid4
ksh$ raidctl -S rraid4
Reconstruction is 100% complete.
Parity Re-write is 100% complete.
Copyback is 100% complete.
ksh$ sysctl kern.securelevel
kern.securelevel = -1
ksh$ uname -a
NetBSD xxx 1.6ZI NetBSD 1.6ZI (STIX-PC) #3: Tue Feb 10 19:27:42 EST  
2004   
xxx@xxx:/export/build/obj.i386/export/build/src/sys/arch/i386/compile/ 
STIX-PC i386
ksh$ ls -l /dev/*raid4d
brw-r-----  1 root  operator       18, 35 May  4  2003 /dev/raid4d
crw-r-----  1 root  operator       62, 35 Jan 25 16:03 /dev/rraid4d

While on another system I built recently:

ksh$ raidctl -S raid4
Reconstruction is 100% complete.
Parity Re-write is 100% complete.
Copyback is 100% complete.
ksh$ raidctl -S rraid4
Reconstruction is 100% complete.
Parity Re-write is 100% complete.
Copyback is 100% complete.
ksh$ sysctl kern.securelevel
kern.securelevel = -1
ksh$ uname -a
NetBSD xxx 1.6ZG NetBSD 1.6ZG (SEAHORSE) #4: Sun Dec 28 02:05:47 EST  
2003   
xxx@xxx:/export/build/obj.i386/export/build/src/sys/arch/i386/compile/ 
SEAHORSE i386
ksh$ ls -l /dev/*raid4d
brw-r-----  1 root  operator      18, 35 Nov 23 14:40 /dev/raid4d
crw-r-----  1 root  operator      62, 35 Dec 27 15:05 /dev/rraid4d

Cheers,
--
Paul Ripke
Unix/OpenVMS/TSM/DBA
I love deadlines. I like the whooshing sound they make as they fly by.
-- Douglas Adams