From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 19:01:18 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 78A4B16A6FA for ; Thu, 6 Apr 2006 17:47:12 +0000 (UTC) (envelope-from freebsd4@fadesa.es) Received: from fuego.fadesa.es (fuego.fadesa.es [195.55.55.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8EBBD45908 for ; Thu, 6 Apr 2006 17:28:55 +0000 (GMT) (envelope-from freebsd4@fadesa.es) Received: (from root@localhost) by fuego.fadesa.es (8.9.3p2/8.8.8) id TAA00147 for ; Thu, 6 Apr 2006 19:29:52 +0200 Received: from tierra.fadesa.es(195.55.55.7) by fuego.fadesa.es Thu, 6 Apr 06 19:29:27 +0200 Received: from fadesa.es (filemon.fadesa.es [195.55.55.6] (may be forged)) by tierra.fadesa.es (8.9.3p2/8.8.8) with ESMTP id TAA25954 for ; Thu, 6 Apr 2006 19:28:18 +0200 Sender: fan@fadesa.es Message-ID: <44354FB1.6163DF7A@fadesa.es> Date: Thu, 06 Apr 2006 19:28:17 +0200 From: "=?iso-8859-15?Q?Jos=E9?= M. =?iso-8859-15?Q?Fandi=F1o?=" Organization: Inmobiliaria FADESA X-Mailer: Mozilla 4.8 [en] (X11; U; Linux 2.4.30-ow1 i686) X-Accept-Language: gl, en, es MIME-Version: 1.0 CC: freebsd-stable@freebsd.org References: <4433DB2B.7753D2C3@fadesa.es> <20060406153115.GC5578@garage.freebsd.pl> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit X-Logged: Logged by tierra.fadesa.es as TAA25954 at Thu Apr 6 19:28:18 2006 Subject: Re: GEOM_RAID3: Device datos is broken, too few valid components X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd4@fadesa.es List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Apr 2006 19:01:20 -0000 Pawel Jakub Dawidek wrote: > +> Unfortunately, the metadata structure of my data partition (a geom raid3 > +> array with tree components ) seems to be corrupted by this hard lock, > +> the following message is scrolled constantly on the screen: > +> > +> GEOM_RAID3: Device datos created (id=3217021940). > +> GEOM_RAID3: Device datos: provider ad6s2 detected. > +> GEOM_RAID3: Device datos: provider ad5s2 detected. > +> GEOM_RAID3: Device datos: provider ad4s2 detected. > +> GEOM_RAID3: Component ad6s2 (device datos) broken, skipping. > +> GEOM_RAID3: Component ad4s2 (device datos) broken, skipping. > +> GEOM_RAID3: Device datos is broken, too few valid components. > +> GEOM_RAID3: Device datos destroyed. > +> > +> Checking the search engine results it isn't a very usual problem, the advice > +> in the returned hits is rerunning "graid label -h datos ad4s2 ad5s2 ad6s2", > +> but before of erasing all my data I would like to ask to list members. > +> > +> How dangerous is running the mentioned command in this context? > > You should be safe as long as the order of slices you give here is the > same as it was when device was initially labeled. I don't remember the exact order (my history file is only 2000 lines long :) however I'm going to duplicate two disks, because they are the minimum necessary to reconstruct the raid3, and I will do some tests over them, so I can maintain intact the original disks. > Of course (as I understand) one of those broken components was really > broken, right? If yes, you should 'graid3 rebuild' it immediatelly after > 'label' command. If no, you should still rebuild one of them after > labeling it. no, it was a collateral damage. The initial problem was a faulty disk in the system raid1 blocking the computer, after the reboot the data raid3 disks show the cited message. I will try to follow your advice and tell something to the list. -- -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GCS/IT d- s+:+() a32 C+++ UBL+++$ P+ L+++ E--- W++ N+ o++ K- w--- O+ M+ V- PS+ PE+ Y++ PGP+>+++ t+ 5 X+$ R- tv-- b+++ DI D++>+++ G++ e- h+(++) !r !z ------END GEEK CODE BLOCK------