Re: RAIDframe mirror failure: Found(low mod_counter): wd5e at 0

[Milos Negovanovic <milos.negovanovic%googlemail.com@localhost>]

On Thu, Mar 05, 2009 at 07:33:23PM +1100, Simon Burge wrote:
> After a wedge and reboot, one of my RAIDframe mirrors wasn't happy.
> 
> In my boot messages I see:
> 
>       Found: wd4e at 1
>       RAID autoconfigure
>       Configuring raid1:
>       Starting autoconfiguration of RAID set...
>       Looking for 0 in autoconfig
>       Found(low mod_counter): wd5e at 0
>       Looking for 1 in autoconfig
>       Found: wd4e at 1
>       raid1: allocating 20 buffers of 65536 bytes.
>       raid1: RAID Level 1
>       raid1: Components: /dev/wd5e[**FAILED**] /dev/wd4e
>       raid1: Total Sectors: 33554176 (16383 MB)
>       raid1: configured ok
> 
> and raidctl has this to say:
> 
>       thoreau 19> raidctl -s raid1
>       Components:
>                  /dev/wd5e: failed
>                  /dev/wd4e: optimal
>       No spares.
>       /dev/wd5e status is: failed.  Skipping label.
>       Component label for /dev/wd4e:
>          Row: 0, Column: 1, Num Rows: 1, Num Columns: 2
>          Version: 2, Serial Number: 2001, Mod Counter: -1189456427
>          Clean: No, Status: 0
>          sectPerSU: 128, SUsPerPU: 1, SUsPerRU: 1
>          Queue size: 100, blocksize: 512, numBlocks: 33554176
>          RAID Level: 1
>          Autoconfig: Yes
>          Root partition: No
>          Last configured as: raid1
>       Parity status: DIRTY
>       Reconstruction is 100% complete.
>       Parity Re-write is 100% complete.
>       Copyback is 100% complete.
> 
> There are no read/write errors for wd5 and I was planning on doing a
> "raidctl -R /dev/wd5e raid1" to just rebuild in place, but thought I'd
> check here to see if there was anything else to check first.

'raidctl -R /dev/wd5e raid1' should work just fine. Recently I had to
recover from similar situation and thats exactly what Ive done.

Regards
-- 
Milos Negovanovic
milos.negovanovic%googlemail.com@localhost