raidctl was looking for:
"/dev/wd0e  " on the disklabel instead of
"/dev/wd0e" because of trailing white space the configure failed.

Grrrr...

On Thu, Apr 11, 2002 9:21 PM, Bruce Anderson
<mailto:brucea@shell.spacestar.net> wrote:
>I was attempting to configure a new raid device when I hit this little
>wall.
>
>bruce@puma$ raidctl -C /etc/raid.d/raid1.conf raid1
>raidctl: ioctl (RAIDFRAME_CONFIGURE) failed: No such file or directory
>
>Is this a sign of cruft in my local source tree, and if so where?
>
>Note the message from the kernel (dmesg) when running raidctl.
>

[snip]

>Kernelized RAIDframe activated
>RAID autoconfigure
>Configuring raid0:
>RAIDFRAME: protectedSectors is 64
>RAIDFRAME: Configure (RAID Level 0): total number of sectors is\
> 24665600 (12043 MB)
>RAIDFRAME(RAID Level 0): Using 6 floating recon bufs with no\
> head sep limit
>boot device: raid0
>root on raid0a dumps on raid0b
>root file system type: ffs
>[ Note: raid0 is on wd1 and wd2 BA- ]
>raidlookup on device: /dev/wd0e   failed!
>Closing vnode for row: 0 col: 0
>vnode was NULL
>Closing vnode for row: 0 col: 1
>vnode was NULL
>RAIDFRAME: failed rf_ConfigureDisks with 2
>Closing vnode for row: 0 col: 0
>vnode was NULL
>Closing vnode for row: 0 col: 1
>vnode was NULL
>
>
>bruce@puma$ cat /etc/raid.d/raid1.conf
># Begin raid frame configuration
>
>START array
># numRow numCol numSpare
>1 2 0
>
>START disks
>/dev/wd0e  
>/dev/wd0f
>
>START layout 
># sectPerSU  SUsPerParityUnit  SUsPerReconUnit  RAID_level
>32 1  1  1
>
>START queue
>scan 200
>

[snip]

>
>
>" Stamp out root logins .  .  .  . su "   --Bruce Anderson  
> This message was created and sent using Cyberdog 2.0, MacOS 8.6,
> awk, find, sed, sendmail, sh, and NetBSD a free Multi-Platform OS.
> NetBSD runs on  44 different system architectures featuring 16
> distinct families of CPUs.   http://www.netbsd.org/
>
>
>
>