From owner-freebsd-questions@FreeBSD.ORG Mon Sep 28 09:43:38 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4EC4010656A5 for ; Mon, 28 Sep 2009 09:43:38 +0000 (UTC) (envelope-from robin@reportlab.com) Received: from mail-bw0-f227.google.com (mail-bw0-f227.google.com [209.85.218.227]) by mx1.freebsd.org (Postfix) with ESMTP id D1BF78FC23 for ; Mon, 28 Sep 2009 09:43:37 +0000 (UTC) Received: by bwz27 with SMTP id 27so3039120bwz.43 for ; Mon, 28 Sep 2009 02:43:36 -0700 (PDT) Received: by 10.204.19.144 with SMTP id a16mr2900842bkb.9.1254129259677; Mon, 28 Sep 2009 02:14:19 -0700 (PDT) Received: from ?192.168.0.3? (host-82-44-127-245.static.telewest.net [82.44.127.245]) by mx.google.com with ESMTPS id e17sm4456152fke.2.2009.09.28.02.14.18 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 28 Sep 2009 02:14:19 -0700 (PDT) Message-ID: <4AC07E69.30800@chamonix.reportlab.co.uk> Date: Mon, 28 Sep 2009 10:14:17 +0100 From: Robin Becker User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: fix remote degraded gmirror X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Sep 2009 09:43:38 -0000 I have a freebsd 6.1 system with a gmirror raid 1 which is degraded. Originally I had /dev/ad4 & /dev/ad6, but I'm getting a degraded status and log messages reporting dergraded status and uncorrectable block for ad4. Obviously I need to remove the device and get it replaced and then insert back into the mirror. However, this is a remote machine and I need to get the right disk fixed. Is there a way I can get the colocation engineer to replace the right disk? I guess I need to do 1) figure out what kind of disk this is and 2) figure out some information to allow them to identify. I looked at the smartctl output and see this /dev/ad4 Device Model: WDC WD1600JS-22MHB0 Serial Number: WD-WCANM4438410 /dev/ad6 Device Model: WDC WD1600JS-22MHB0 Serial Number: WD-WCANM4434657 is this sufficient to enable a data centre engineer to fix my problem? -- Robin Becker