Subject: Re: raidframe recovery
To: Greg Oster <>
From: Patrick Welche <>
List: netbsd-users
Date: 10/04/2004 20:52:01
On Mon, Oct 04, 2004 at 01:38:42PM -0600, Greg Oster wrote:
> Oh...... This is 2.0E from May 5, and support for 'absent' didn't 
> happen until May 22, 2004. 

Our emails must have crossed :-)

> If you go back to your original /etc/raid0.conf with wd1a, and make 
> sure wd1a (as a physical component) doesn't exist, then 'raidctl -C' 
> should configure the set for you.  When you do 'raidctl -s', you
> should see wd1a listed, but marked as failed.  (you need to make sure 
> wd1a doesn't exist, as otherwise it will be considered the 'master' 
> here, and you'll end up reading from it instead of from wd2a!)

Much happier :-)

# raidctl -s raid0
           /dev/wd1a: failed
           /dev/wd2a: optimal
No spares.
/dev/wd1a status is: failed.  Skipping label.
Component label for /dev/wd2a:
   Row: 0, Column: 1, Num Rows: 1, Num Columns: 2
   Version: 2, Serial Number: 35710, Mod Counter: 273
   Clean: No, Status: 0
   sectPerSU: 128, SUsPerPU: 1, SUsPerRU: 1
   Queue size: 100, blocksize: 512, numBlocks: 490234624
   RAID Level: 1
   Autoconfig: No
   Root partition: No
   Last configured as: raid0
Parity status: DIRTY
Reconstruction is 100% complete.
Parity Re-write is 100% complete.
Copyback is 100% complete.

Now to make a backup ;)

How can I pop a new wd1 back in? disklabel it, but then how can I get past
the loop I was in before?