From owner-freebsd-questions@freebsd.org Mon Feb 6 23:29:13 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 74E98CB4210 for ; Mon, 6 Feb 2017 23:29:13 +0000 (UTC) (envelope-from rcarter@pinyon.org) Received: from h2.pinyon.org (h2.pinyon.org [65.101.20.170]) (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 4FA7D77C for ; Mon, 6 Feb 2017 23:29:12 +0000 (UTC) (envelope-from rcarter@pinyon.org) Received: by h2.pinyon.org (Postfix, from userid 58) id B4D0522B78; Mon, 6 Feb 2017 16:29:06 -0700 (MST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=pinyon.org; s=DKIM; t=1486423746; bh=fFCmqcqD4mGrWJ9UnEm00uv9dpoojXtAemgmu3Y83IY=; h=Subject:To:References:From:Date:In-Reply-To; b=CjlO9C06pFZKVB5KhDIMtEz+os3cHgVrW57q6nT7QlphIa3k/JJisZXBJe706YIeY MQLRgcmC4I758mLlfTjvkrDgUeZFAO/rRWrnhLbW1uaqn8Hx5zTJnU3FLLUR7gQ/Gw dYtdaTtYE6kbDs7HGsakXtuFOD//ueMUYUp2gECU= X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on h2.pinyon.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED shortcircuit=no autolearn=ham autolearn_force=no version=3.4.1 Received: from [10.0.10.15] (h1.pinyon.org [65.101.20.169]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by h2.pinyon.org (Postfix) with ESMTPSA id EDAA022B6A for ; Mon, 6 Feb 2017 16:29:05 -0700 (MST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=pinyon.org; s=DKIM; t=1486423745; bh=fFCmqcqD4mGrWJ9UnEm00uv9dpoojXtAemgmu3Y83IY=; h=Subject:To:References:From:Date:In-Reply-To; b=C/A0Eh6nADym474Ga9l4FPSDvybIwlWHWgPchqLadTwctWAUoP5D3DgbCPZYkZF6f kG9W5/NzXIY3Z417gla2NlIvirK5cUJ9AjTWc62YvvaUYmjwTrSF96paKkE0yku8ND DpZf1DQeWEZcXp6jE9Cb2AroqeYpcR0XJDsIDJHY= Subject: Re: zfs upgrade "gpart: /dev/da4p1: not enough space" To: freebsd-questions@freebsd.org References: From: "Russell L. Carter" Message-ID: <2f897949-d25e-9637-e6ae-82c03de1447a@pinyon.org> Date: Mon, 6 Feb 2017 16:29:05 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Feb 2017 23:29:13 -0000 On 02/04/17 20:55, Russell L. Carter wrote: > Greetings, > > amd64 11/stable > > So I'm on the last machine of a zpool upgrade everybody, and on the > very last, and most important pool, I zpool upgraded and then > went to finish the boot zpool and what did I see: > > root@terpsichore> gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 > da3 > gpart: /dev/da3p1: not enough space > > So... what do I do now? It's happy staying up for days, but... will > I have to reinstall the system to make da3p1 big enough? Ok, I sent that over the weekend. I think this is important enough that the proper response to encountering this situation should be made visible to google at least. I have tried various searches and found zero results so far. To recap, in part because of the annoying text that shows up with every zpool status, I upgraded all of my zfs pools. On the first four bootable pools, I successfully followed the instructions to update the bootcode as described above, adjusted for the appropriate device. On updating the final boot pool, I get the error: gpart: /dev/da3p1: not enough space. The filesystems in that pool are not near full, btw. The pool itself was created from a 10.0 system and is a mirror, and updating the bootcode for other drive returned the same error, unsurprisingly. So, 1st question that it would be helpful to get a google answer for in the future: is this pool now unbootable? 2nd question, if it is not bootable, is there a way to rescue it? Otherwise, I am guessing, I will have to completely reinstall (including repartitioning, etc.) the system, in order to regain a bootable system. Maybe that should be part of the instructions that obeying the incessant nagging from the zpool status command can lead to this kind of unexpected and time consuming... exercise. Thanks, Russell