From owner-freebsd-questions@FreeBSD.ORG Tue Jan 26 14:25:23 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 741A41065698 for ; Tue, 26 Jan 2010 14:25:23 +0000 (UTC) (envelope-from kraduk@googlemail.com) Received: from mail-bw0-f213.google.com (mail-bw0-f213.google.com [209.85.218.213]) by mx1.freebsd.org (Postfix) with ESMTP id 0133A8FC1F for ; Tue, 26 Jan 2010 14:25:22 +0000 (UTC) Received: by bwz5 with SMTP id 5so3659417bwz.3 for ; Tue, 26 Jan 2010 06:25:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=H8bNqIChOVFbTvdrCjIsSH1YhbjSlc1ncPfg9SdiYLI=; b=LyPC16o42NmJKIeQEwiQbx0oQsgdcykHb3DURw63lwCe/8bLiGDUGM2bkg5i6Ik5wl XiXIb7YksLmRoEMIIExpbbM/fk7w6pi+dMAmWo6yz0DiVQFHFb3zpM83l6s2vtaOP9dE vfALXnawrE54wGWomdHnbVntbp8eObYmj6ZAc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=UnOCBR3OeDw+5Drgc0DwTHdyZnB49TIjbr8bnSnBXrUz1jr2UGDGX7BMV2fcCF5dQB J57VdKT6jGUiEN7BTnrvp129Bbtz5d+tZrWLFCLnCwERBwut17ToPZTfFEZqven7qXa0 9BrH/kjsoW62fKkE4sBexNBftUoBuFuFaVPEY= MIME-Version: 1.0 Received: by 10.239.193.140 with SMTP id j12mr876658hbi.70.1264515921293; Tue, 26 Jan 2010 06:25:21 -0800 (PST) In-Reply-To: References: <4B5EE153.9050402@ibctech.ca> Date: Tue, 26 Jan 2010 14:25:21 +0000 Message-ID: From: krad To: Steve Bertrand Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: George Liaskos , Ross Penner , freebsd-questions@freebsd.org Subject: Re: Help booting FreeBSD with a ZFS root filesystem X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Jan 2010 14:25:23 -0000 2010/1/26 krad > > > 2010/1/26 Steve Bertrand > > krad wrote: >> > 2010/1/26 Ross Penner >> > >> >> That seems to have been the problem. >> >> >> >> Thanks for the help. >> >> >> >> On Mon, Jan 25, 2010 at 5:29 PM, George Liaskos > > >> >> wrote: >> >>> I had the same issue because i forgot to copy the zpool.cache under >> >>> /zroot/boot/zfs. >> >> > once you have generated the zpool.cache never never never export the >> boot >> > pool again. Exporting isnt the same as unmounting (a common >> misconception). >> > If you do export it the pool will become unbootable. >> >> Out of curiosity (because I had this problem a few weeks back), how does >> one move a bootable pool into another physical server in order to be >> able to see the pool as a 'data' set without exporting/importing, and >> then moving the pool back to the hardware that it normally boots from? >> >> Perhaps I was lucky when copying the cache back onto itself worked... >> >> Steve >> > > with difficulty i suspect. You will probably have to specify an alternate > root and zpool.cache file. Then copy the cache file onto the zpool before > powering down, and NOT exporting. > > If you don't use an alternate zpool.cache file I suspect you will get > issues as the test systems zpools will be referenced in there, and will > cause a pickle when you bring the broken system up. > > Its probably best to use a non zfs based rescue system just to keep things > simpler. > > > > > Not sure if there will be any issues with hostid being different. I presume the pool is imported with a -f option on boot