From owner-freebsd-fs@FreeBSD.ORG Sun Apr 6 00:12:38 2014 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2514AD10 for ; Sun, 6 Apr 2014 00:12:38 +0000 (UTC) Received: from mail-we0-x22a.google.com (mail-we0-x22a.google.com [IPv6:2a00:1450:400c:c03::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AFADBDE2 for ; Sun, 6 Apr 2014 00:12:37 +0000 (UTC) Received: by mail-we0-f170.google.com with SMTP id w61so5163905wes.1 for ; Sat, 05 Apr 2014 17:12:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=Fb84jn7r04z954+DppURNWmtbAeDlpSc/QQL5HDtujg=; b=bKdQYZ4lzPJElIpaWZGZCGU8VWy8NCQQ/VsTfBtdAXAt1cbnUKiJhUzRmJGZzYqVSR lJGgn2B4fpqCe3MHcQUXfMTb1S5LVFb7aD6To0RJ4WzY12cdvbjXa6QdY/ZHU+9/4UHN Vi1ooujRU49XJ4QuBjQmtACdMpt0ZhqZE8nvJgbLOXob3Ntf7ReDE1Z1mpXTe66Ph0CB sZhUMxGC10KooSavmSeIm71z7uzre1oQ/awYWR+yVkVrxeZEkmVSELaBuJxR6AJsu0Jb JqBdbfpM2lIUxNbXTOrrgHQ1MYdq69N14n1qEVT+lNxHSk2fTRPVTbJWof3b0hNHhb6T 32ug== X-Received: by 10.194.203.2 with SMTP id km2mr31232655wjc.72.1396743155597; Sat, 05 Apr 2014 17:12:35 -0700 (PDT) Received: from [192.168.20.30] (81-178-2-118.dsl.pipex.com. [81.178.2.118]) by mx.google.com with ESMTPSA id cl9sm19105164wjc.25.2014.04.05.17.12.34 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 05 Apr 2014 17:12:34 -0700 (PDT) Message-ID: <53409BF1.6050001@gmail.com> Date: Sun, 06 Apr 2014 01:12:33 +0100 From: Kaya Saman User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: Vusa Moyo Subject: Re: Device Removed by Administrator in ZPOOL? References: <53408FAB.8080202@gmail.com> <512A7865-CEFD-4BDA-A060-AE911BEDD5B7@tuxsystems.co.za> In-Reply-To: <512A7865-CEFD-4BDA-A060-AE911BEDD5B7@tuxsystems.co.za> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Filesystems X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Apr 2014 00:12:38 -0000 Many thanks for the response! The server doesn't show any lights for "drive error" however, the blue read LED isn't coming on, on the drive in question (as removed from ZPOOL). I will have a look for LSI tools in @Ports and also see if the BIOS LSI hook comes up with anything. Regards, Kaya On 04/06/2014 12:44 AM, Vusa Moyo wrote: > This is more than likely a failed drive. > > Have you physically looked at the server for orange lights which may help ID the failed drive?? > > There could also be tools to query the lsi hba. > > Sent from my iPad > >> On Apr 6, 2014, at 1:20 AM, Kaya Saman wrote: >> >> Hi, >> >> I'm running FreeBSD 10.0 x64 on a Xeon E5 based system with 8GB RAM. >> >> >> Checking the ZPOOL status I saw one of my drives has been offlined... the exact error is this: >> >> # zpool status -v >> pool: ZPOOL_2 >> state: DEGRADED >> status: One or more devices has been removed by the administrator. >> Sufficient replicas exist for the pool to continue functioning in a >> degraded state. >> action: Online the device using 'zpool online' or replace the device with >> 'zpool replace'. >> scan: scrub repaired 0 in 9h3m with 0 errors on Sat Apr 5 03:46:55 2014 >> config: >> >> NAME STATE READ WRITE CKSUM >> ZPOOL_2 DEGRADED 0 0 0 >> raidz2-0 DEGRADED 0 0 0 >> da0 ONLINE 0 0 0 >> 14870388343127772554 REMOVED 0 0 0 was /dev/da1 >> da2 ONLINE 0 0 0 >> da3 ONLINE 0 0 0 >> da4 ONLINE 0 0 0 >> >> >> I think this is due to a dead disk however, I'm not certain which is why I wanted to ask here as I didn't remove the drive at all..... rather then some kind of OS/ZFS error. >> >> >> The drives are 2TB WD Green drives all connected to an LSI HBA; everything is still under warranty so no big issue there and I have external backups too so I'm not really that worried, I'm just trying to work out what's going on. >> >> >> Are my suspicions correct or should I simply try to reboot the system and see if the drive comes back online? >> >> >> Regards, >> >> >> Kaya >> _______________________________________________ >> freebsd-fs@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-fs >> To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org"