On 10/14/07, Greg Oster <[EMAIL PROTECTED]> wrote:
> knitti writes:
> > raidlookup on device: /dev/wd3d failed !
> ^
> I suspect you have an extra space after "wd3d" in the config file...
> And, unfortunately, that annoying little non-feature is enough to
> stop RA
knitti writes:
> Hi,
>
> I tried to set up a RAID 1 softraid with raidframe, but no matter what
> I try, the RAID refuses to configure. So please, if anyone has an idea
> what I may have missed...
>
> # raidctl -C raid0.conf raid0
> raidctl: ioctl (RAIDFRAME_CONFIGURE) failed
>
> this adds the f
Hi Boris,
On 10/14/07, Boris Goldberg <[EMAIL PROTECTED]> wrote:
> You've said that you'd tried different configurations, but the one you
> are showing here just can't work, because you don't have wd3.
I wrote: " I tried both with wd0d, wd1d (both exist) and with wd1d,wd3d
(latter doesn't ph
Hello knitti,
Saturday, October 13, 2007, 3:43:27 PM, you wrote:
k> raidlookup on device: /dev/wd3d failed !
k> ...
k> START disks
k> /dev/wd3d
Shouldn't it be /dev/wd0d ?
k> /dev/wd1d
k> ...
k> # disklabel wd0
k> ...
k> d:606244905 18892440RAID
k> ...
k> # disklabel wd
Hi,
I tried to set up a RAID 1 softraid with raidframe, but no matter what
I try, the RAID refuses to configure. So please, if anyone has an idea
what I may have missed...
# raidctl -C raid0.conf raid0
raidctl: ioctl (RAIDFRAME_CONFIGURE) failed
this adds the following lines to the dmesg buffer:
5 matches
Mail list logo