From owner-freebsd-questions@freebsd.org Fri Nov 4 00:13:18 2016 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 270EFC2E89E for ; Fri, 4 Nov 2016 00:13:18 +0000 (UTC) (envelope-from brandon.wandersee@gmail.com) Received: from mail-oi0-f45.google.com (mail-oi0-f45.google.com [209.85.218.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id ED857169D for ; Fri, 4 Nov 2016 00:13:17 +0000 (UTC) (envelope-from brandon.wandersee@gmail.com) Received: by mail-oi0-f45.google.com with SMTP id 62so121922866oif.1 for ; Thu, 03 Nov 2016 17:13:17 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:references:user-agent:from:to:cc:subject :in-reply-to:date:message-id:mime-version; bh=89KSGEVfpckJYKT+V014E1dLSHG8uRH3iy/0tRc0BCQ=; b=Rm9nIgAVmp+cBCBN1clz0VEbrlQJeqcCz24V0q02PVTGjxqVNQDNbQ83azaP6Rzf9x wc/plZS6PxTRRADBb5m/YXxKRy1a9QBplnt7zTMXhNEFkK1xFABrixZXZPKta6hKP/Ll 9lW3FL9ooqR+abc+HTX7k+2L2S8KA1YZIx4F6rtRcp/v9UKUAkeE4CiMWFeaYtmFNpBz W213kTCa09n04vsg2AjOP9w9Bz3RzfqblupquQeqYl+UBxQ0Kl2Sh4p0H/xPlvxaJDvL SsRQGwDgxe5E7hKbKRzhoqXNte3S/kq3MxYTSuUqoFvckpaYf9GEC90e6KicLn7CVOwJ VYfw== X-Gm-Message-State: ABUngvfhTZ8rboAiR20ncg7viWnVgFEBb2zP/08W4p1PCklpezrVFhvQNoPAvnmYzzEd3Q== X-Received: by 10.107.50.15 with SMTP id y15mr10663660ioy.30.1478216875750; Thu, 03 Nov 2016 16:47:55 -0700 (PDT) Received: from WorkBox.Home (174-30-222-106.mpls.qwest.net. [174.30.222.106]) by smtp.gmail.com with ESMTPSA id r67sm3716224ioi.9.2016.11.03.16.47.54 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 03 Nov 2016 16:47:54 -0700 (PDT) Received: from localhost (WorkBox.Home [local]) by WorkBox.Home (OpenSMTPD) with ESMTPA id 03a0f000; Thu, 3 Nov 2016 18:47:54 -0500 (CDT) References: User-agent: mu4e 0.9.16; emacs 25.1.1 From: Brandon J. Wandersee To: Matthias Fechner Cc: FreeBSD Mailing List Subject: Re: Prevent zpool from being mounted on next boot In-reply-to: Date: Thu, 03 Nov 2016 18:47:54 -0500 Message-ID: <86eg2sunv9.fsf@gmail.com> MIME-Version: 1.0 Content-Type: text/plain 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: Fri, 04 Nov 2016 00:13:18 -0000 Matthias Fechner writes: > Is there a way to prevent the mount from pool tank at next boot? > > I would not like to destroy the pool (tank) till I can boot the new one without problems. Here would be the "dirty" way of doing it: 1. Boot into "tank," or boot the install medium and choose "Live CD" 2. Import "zroot" (remember to use "altroot"), or mount whatever partition contains /boot for "zroot" 3. Delete /boot/zfs/zpool.cache on "zroot" That file should be replaced when you boot from "zroot," but will only contain the relevant info for the new pool. You'd need to make sure "zfs_enable='YES'" is set in /etc/rc.conf for at least the first boot, since only the root filesystem would be mounted on the first boot otherwise. Someone else might have a cleaner way of doing what you want, though. -- :: Brandon J. Wandersee :: brandon.wandersee@gmail.com :: -------------------------------------------------- :: 'The best design is as little design as possible.' :: --- Dieter Rams ----------------------------------