From owner-freebsd-questions@FreeBSD.ORG  Wed Feb  1 08:52:39 2006
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
X-Original-To: freebsd-questions@freebsd.org
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 4722216A420
	for <freebsd-questions@freebsd.org>;
	Wed,  1 Feb 2006 08:52:39 +0000 (GMT)
	(envelope-from freebsd@juiceless.net)
Received: from fep32-app.kolumbus.fi (fep32-0.kolumbus.fi [193.229.0.63])
	by mx1.FreeBSD.org (Postfix) with ESMTP id AE85F43D5E
	for <freebsd-questions@freebsd.org>;
	Wed,  1 Feb 2006 08:52:32 +0000 (GMT)
	(envelope-from freebsd@juiceless.net)
Received: from [192.168.1.33] (really [80.186.228.199])
	by fep32-app.kolumbus.fi with ESMTP
	id <20060201085231.XCQW3516.fep32-app.kolumbus.fi@[192.168.1.33]>
	for <freebsd-questions@freebsd.org>; Wed, 1 Feb 2006 10:52:31 +0200
Message-ID: <43E076CC.2090107@juiceless.net>
Date: Wed, 01 Feb 2006 10:52:28 +0200
From: Ville Lundberg <freebsd@juiceless.net>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: freebsd-questions@freebsd.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: gmirror: degraded, Component ad4 (device gm0) broken, skipping.
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Feb 2006 08:52:39 -0000

Hi,

one of my clients had a problem with their server and had to cold reboot
it. It's running 6.0-release-p4.
As I feared, the harddrives did not like the reboot, and gmirror now
states it is degraded.
I have no chance to get to the server console any time soon, so I
thought someone could help me check that this procedure I planned is OK
- I probably have to explain via telephone or email to the client how to
do it, and they certainly aren't technical people.

Boot message:

Feb  1 08:40:51 portfolio kernel: GEOM_MIRROR: Device gm0 created (id=4091963512).
Feb  1 08:40:51 portfolio kernel: GEOM_MIRROR: Device gm0: provider ad4 detected.
Feb  1 08:40:51 portfolio kernel: GEOM_MIRROR: Device gm0: provider ad6 detected.
Feb  1 08:40:51 portfolio kernel: GEOM_MIRROR: Component ad4 (device gm0) broken, skipping.
Feb  1 08:40:51 portfolio kernel: GEOM_MIRROR: Device gm0: provider ad6 activated.
Feb  1 08:40:51 portfolio kernel: GEOM_MIRROR: Device gm0: provider mirror/gm0 launched.

so one of the SATA harddrives is lost from the mirror. The harddrive is
probably ok, as it's just one week old. If I understood it correctly, I
should do
gmirror forget gm0
gmirror insert gm0 ad4
and this should build the mirror again? If this fails, the hd is really
physically broken?
  --Ville

gmirror list:

Geom name: gm0
State: DEGRADED
Components: 2
Balance: round-robin
Slice: 4096
Flags: NONE
GenID: 1
SyncID: 1
ID: 4091963512
Providers:
1. Name: mirror/gm0
   Mediasize: 37019565568 (34G)
   Sectorsize: 512
   Mode: r6w6e7
Consumers:
1. Name: ad6
   Mediasize: 37019566080 (34G)
   Sectorsize: 512
   Mode: r1w1e1
   State: ACTIVE
   Priority: 0
   Flags: NONE
   GenID: 1
   SyncID: 1
   ID: 1675341426