> >> How to reconfigure RAIDFrame to use another hdd? Earler I have such
> >> configuration with NON-existent hdd (wd2):
> >>
> >> ...
> >> START disks
> >> /dev/wd1e
> >> /dev/wd2e
> >> ...
> >>
> >> Now, I need to replace non-existent wd2e with wd0e. Disklabel for wd0
> >> identical to wd1e. After reading raidctl(8) I did following:
> >>
> >> raidctl -a /dev/wd0e raid0
> >> raidctl -vF component1 raid0
> >> raidctl -P raid0
> >>
> >> Again after reboot I've got failed ``component1':
> >>
> >> # raidctl -vs raid0
> >> raid0 Components:
> >>            /dev/wd1e: optimal
> >>           component1: failed
> >> No spares.
> 
> KBK> It seems you weren't successful in adding wd0e as a spare.  But if you
> KBK> were,
> 
> KBK> raidctl -r /dev/wd0e raid0
> 
> KBK> to remove it.
> 
> KBK> Modify your raid0.conf:
> KBK> START disks
> KBK> /dev/wd1e
> KBK> /dev/wd0e
> KBK> ...
> 
> KBK> raidctl -Rv /dev/wd0e raid0
> KBK> raidctl -Pv raid0
> 
> KBK> to reconstruct directly onto wd0e.
> 
> KBK> I'm not sure what to make of 'component1'.  It's not an explicit
> KBK> device, did you use that string your raid0.conf?  The first slot in
> KBK> these commands should refer to an explicit device.
> 
> # raidctl -vF component1 raid0
> # raidctl -vP raid0
> # raidctl -s raid0
> raid0 Components:
>            /dev/wd1e: optimal
>           component1: spared
> Spares:
>            /dev/wd0e: used_spare
> Parity status: clean
> Reconstruction is 100% complete.
> Parity Re-write is 100% complete.
> Copyback is 100% complete.
> # raidctl -r /dev/wd0e raid0
> # cat /etc/raid0.conf
> START array
> 1 2 0
> 
> START disks
> /dev/wd1e
> /dev/wd0e
> 
> START layout
> 128 1 1 1
> 
> START queue
> fifo 100
> # raidctl -Rv /dev/wd0e raid0                                                 
>  
> raidctl: ioctl (RAIDFRAME_GET_INFO) failed
> # raidctl -Pv raid0                                                           
>  
> raid0: Parity status: clean
> # raidctl -sv raid0
> raid0 Components:
>            /dev/wd1e: optimal
>           component1: spared
> Spares:
>            /dev/wd0e: used_spare
> Component label for /dev/wd1e:
>    Row: 0, Column: 0, Num Rows: 1, Num Columns: 2
>    Version: 2, Serial Number: 777, Mod Counter: 348
>    Clean: No, Status: 0
>    sectPerSU: 128, SUsPerPU: 1, SUsPerRU: 1
>    Queue size: 100, blocksize: 512, numBlocks: 156038272
>    RAID Level: 1
>    Autoconfig: Yes
>    Root partition: Yes
>    Last configured as: raid0
> component1 status is: spared.  Skipping label.
> raidctl: ioctl (RAIDFRAME_GET_COMPONENT_LABEL) failed
> # 
> 
> -- 
> Sincerely,
> Dennis
> 

I've never had good luck attempting to recover from a failure like this.

I've pretty much always rebooted from a recovery partition and not
autoconfigured the raid slices.

Then I would set up my disklabel on the fresh drive to match the raid'd
drive, with the excpetion being the slices would be FFS. Format the drives.

Then put the raid disklabel on.

Configure the raid device from a conf file.
disable autoconfiguration of the device
manually rebuild the device
enable autoconfiguration

http://www.yggdrasil.ca/openbsd/recovery.txt  describes my procedure for
recovering from a failure. Hope it helps.

Jim

On Thu, Nov 17, 2005 at 12:37:26PM +0300, Dennis S.Davidoff wrote:
> Wednesday, November 16, 2005, 11:35:16 PM, you wrote:
> 
> KBK> "Dennis S.Davidoff" <[EMAIL PROTECTED]> writes:
> 

-- 
"Most moms teach their daughters how to run a house, but you?  You teach
yours the fine art of mass destruction."
      - Nabs - Goodbye is not forever

perl -le '$_="6110>374086;2064208213:90<307;55";tr[0->][ LEOR!AUBGNSTY];print'

Reply via email to