Paul M wrote:
Thinking about this some more, I suspect that what may be happening is that
the disk still thinks it is a spare. Try blowing away the RAID partition,
possibly even replace it with a regular partition and write data to it just
to make sure. Then delete that, recreate the RAID partition and try
again to
reconstruct the component.
(It may also be possible to achieve this with the -r option to raidctl, but
I'm unfamiliar with the operation of this switch).
I will nuke the raid partition. I'll relabel is as a regular partition
and format a file system on it. I'll then relabel it again as a RAID
partition. I assume that would count as a "nuke 'em from space". :)
Once it's nuked what are the series of steps to add it as a component to
the array? I want to make sure I get it right this time.
Essentially, you configured the disk as a spare, now you want to override
that configuration and configure it as a component.
The man page does say that the spare and the component it was reconstructed
from are interchangeable, but I think the system is getting confused as to
just what wd1d is.
OK...
Taking a different approach, you could keep wd1d as the spare, but add a
3rd disk to replace the failed component and simply reconstruct onto that
(using the -B switch to raidctl)
I will look in the box to see if I can get another drive in there. I may
be space constrained...
Also - dont forget about the syslog.
Sorry, but I'm not clear on what you mean here? Could you clarify?
Thanks,
Jeff
--
Jeffrey C. Smith Phone: 512.692.7607
RevolutionONE Cell : 512.965.3898
j...@revolutionone.com
paulm
