From owner-freebsd-current@FreeBSD.ORG  Thu Nov 11 13:03:57 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id C06FC16A4CE; Thu, 11 Nov 2004 13:03:57 +0000 (GMT)
Received: from picard.newmillennium.net.au
	(static-114.250.240.220.dsl.comindico.com.au [220.240.250.114])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id A65E643D5D; Thu, 11 Nov 2004 13:03:54 +0000 (GMT)
	(envelope-from alastair@newmillennium.net.au)
Received: from riker (riker.nmn.cafn [10.0.1.2])iABD3rIa001345;
	Fri, 12 Nov 2004 00:03:53 +1100 (EST)
	(envelope-from alastair@newmillennium.net.au)
From: <freebsd@newmillennium.net.au>
Sender: "Alastair D'Silva" <alastair@newmillennium.net.au>
To: <current@freebsd.org>
Date: Fri, 12 Nov 2004 00:05:29 +1100
Organization: New Millennium Networking
Message-ID: <01cc01c4c7ef$1eb55d10$0201000a@riker>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2616
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
Subject: Recovering Gvinum RAID5 after a crash
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Nov 2004 13:03:57 -0000

Ok, my machine just locked up, and after rebooting, two of the four
drives in the RAID5 showed up as stale. I tried issuing a
'rebuildparity', but its not implemented, and neither it seems is
'setstate'.

I tried issuing a 'start' request, and it appeared to start initializing
the disks!! So, I killed the machine and left the array unmounted. I've
got duplicate data of most of the stuff on there, so its not a big deal,
but there should be a way to get the array back up without initializing
the disks.

Of course, I could be mistaken and the RAID5 rebuild could be showing up
as 'I', in which case it should should probably be changed to 'R' or
something to avoid confusion.

-- 
Alastair D'Silva           mob: 0413 485 733
Networking Consultant      fax: 0413 181 661
New Millennium Networking  web: http://www.newmillennium.net.au