From owner-freebsd-questions@FreeBSD.ORG Tue Jan 6 00:00:47 2015 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6DD30762 for ; Tue, 6 Jan 2015 00:00:47 +0000 (UTC) Received: from mail.unitedinsong.com.au (mail.unitedinsong.com.au [150.101.178.33]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 22E4D6493E for ; Tue, 6 Jan 2015 00:00:46 +0000 (UTC) Received: from [192.168.0.198] (laptop1.herveybayaustralia.com.au [192.168.0.198]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.unitedinsong.com.au (Postfix) with ESMTPSA id 4E4A9273B2 for ; Tue, 6 Jan 2015 10:00:42 +1000 (EST) Message-ID: <54AB25A7.4040901@herveybayaustralia.com.au> Date: Tue, 06 Jan 2015 10:00:39 +1000 From: Da Rock User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: freebsd-questions@freebsd.org Subject: Re: ZFS replacing drive issues References: <54A9D9E6.2010008@herveybayaustralia.com.au> <54A9E3CC.1010009@hiwaay.net> In-Reply-To: <54A9E3CC.1010009@hiwaay.net> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Jan 2015 00:00:47 -0000 On 05/01/2015 11:07, William A. Mahaffey III wrote: > On 01/04/15 18:25, Da Rock wrote: >> I haven't seen anything specifically on this when googling, but I'm >> having a strange issue in replacing a degraded drive in ZFS. >> >> The drive has been REMOVED from ZFS pool, and so I ran 'zpool replace >> '. This normally just works, and I >> have checked that I have removed the correct drive via serial number. >> >> After resilvering, it still shows that it is in a degraded state, and >> that the old and the new drive have been REMOVED. >> >> No matter what I do, I can't seem to get the zfs system online and in >> a good state. >> >> I'm running a raidz1 on 9.1 and zfs is v28. >> >> Cheers >> _______________________________________________ >> freebsd-questions@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >> To unsubscribe, send any mail to >> "freebsd-questions-unsubscribe@freebsd.org" >> > > Someone posted a similar problem a few weeks ago; rebooting fixed it > for them (as opposed to trying to get zfs to fix itself w/ management > commands), might try that if feasible .... $0.02, no more,l no less .... > Sorry, that didn't work unfortunately. I had to wait a bit until I could do it between it trying to resilver and workload. It came online at first, but then went back to removed when I checked again later. Any other diags I can do? I've already run smartctl on all the drives (5hrs+) and they've come back clean. There's not much to go on in the logs either. Do a small number of drives just naturally error when placed in a raid or something?