Hi Steve and List,

This more or less go me back up.

The first time I tried "raidctl -R /dev/wd0a raid0" I locked the system.

After a reboot, I noticed the following in my boot messages:
wd0a: DMA error writing fsbn 3744960 of 3744960-3745087
      (wd0 bn 3745023; cn 3715 tn 4 sn 51), retrying
wd0: soft error (corrected)

After which the "raidctl -R /dev/wd0a raid0" did successfuly rebuild.

I apologize to the list that I neglected to try alternate
capitalizations of RAID vs raid. I'm surprised the search
defaults to case sensitive. Or maybe I just missed it...

Thanks,
gene

I yancm@sdf.lonestar.org posted;
>>2 days ago I got a message that one of the disks failed.
>>
>># raidctl -s raid0
>>Components:
>>           /dev/wd0a: failed
>>           /dev/wd2a: optimal

To which "Steven M. Bellovin" <smb@cs.columbia.edu> Wrote:
> I had that, too, under 2.0.  It was a false alarm; there was no
> hardware problem.  I did have to repair my disk as far as raid was
> concerned, though.
>
> As with you, wd0a was listed as "failed".  I believe I repaired it by
> saying
>
> 	raidctl -R wd0a raid0
>
> My original posting was on August 8, 2005, if you want to check the
> archives.