From owner-freebsd-questions@FreeBSD.ORG Fri Jan 9 19:27:07 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 A8ABBA3E for ; Fri, 9 Jan 2015 19:27:07 +0000 (UTC) Received: from smtp124.ord1c.emailsrvr.com (smtp124.ord1c.emailsrvr.com [108.166.43.124]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7FBAC127 for ; Fri, 9 Jan 2015 19:27:06 +0000 (UTC) Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp16.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id C0F761800FB; Fri, 9 Jan 2015 14:18:52 -0500 (EST) X-Virus-Scanned: OK Received: by smtp16.relay.ord1c.emailsrvr.com (Authenticated sender: rhavenn-AT-rhavenn.net) with ESMTPSA id 15FA0180157; Fri, 9 Jan 2015 14:18:51 -0500 (EST) X-Sender-Id: rhavenn@rhavenn.net Received: from vash.rhavenn.local (209-112-171-194.static.acsalaska.net [209.112.171.194]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:25 (trex/5.4.2); Fri, 09 Jan 2015 19:18:52 GMT Received: from localhost (4000@localhost [local]); by localhost (OpenSMTPD) with ESMTPA id 7e14e143; Fri, 9 Jan 2015 10:18:50 -0900 (AKST) Date: Fri, 9 Jan 2015 10:18:50 -0900 From: Henrik Hudson To: Da Rock Subject: Re: ZFS replacing drive issues Message-ID: <20150109191850.GA58984@vash.rhavenn.local> References: <54A9D9E6.2010008@herveybayaustralia.com.au> <54A9E3CC.1010009@hiwaay.net> <54AB25A7.4040901@herveybayaustralia.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <54AB25A7.4040901@herveybayaustralia.com.au> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: freebsd-questions@freebsd.org 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: Fri, 09 Jan 2015 19:27:07 -0000 On Tue, 06 Jan 2015, Da Rock wrote: > 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? > _______________________________________________ > 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" a) try a 'zpool clear' to perhaps force it to clear errors, but to be safe I'd still do "c" below. b) Did you physically remove the old drive and replace it and then run a zpool replace? Did the devices have the same device ID or did you use GPT ids? c) If it's a mirror try just removing the device, zpool remove pool device and then re-attaching it via zpool attach. henrik -- Henrik Hudson lists@rhavenn.net ----------------------------------------- "God, root, what is difference?" Pitr; UF