From owner-freebsd-fs@freebsd.org Mon Oct 15 20:03:18 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 934F810C7A68 for ; Mon, 15 Oct 2018 20:03:18 +0000 (UTC) (envelope-from jeffc@supranet.net) Received: from mailbox.supranet.net (mailbox.supranet.net [IPv6:2607:f4e0:100:111::9]) (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 3DA9882EEF for ; Mon, 15 Oct 2018 20:03:17 +0000 (UTC) (envelope-from jeffc@supranet.net) Received: from [209.204.169.179] (helo=[192.168.1.205]) by mailbox.supranet.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.82 (FreeBSD)) (envelope-from ) id 1gC958-000KU1-1h for freebsd-fs@freebsd.org; Mon, 15 Oct 2018 15:03:14 -0500 Date: Mon, 15 Oct 2018 13:03:12 -0700 From: Jeff Chan Reply-To: Jeff Chan Message-ID: <632689552.20181015130312@supranet.net> To: freebsd-fs@freebsd.org Subject: Re: "ZFS: can't find pool by guid" after reboot during 11.1 to 11.2 upgrade In-Reply-To: <609311573.20181002183857@supranet.net> References: <609311573.20181002183857@supranet.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Oct 2018 20:03:18 -0000 On Tuesday, October 2, 2018, 6:38:57 PM, Jeff Chan wrote: > Hi Folks, > Apologies in advance if this isn't the right place to ask. Wasn't > sure if it was perhaps related to the 11.2 ZFS-related boot loader > changes though. > During a FreeBSD upgrade from 11.1 to 11.2, after the reboot step > between freebsd-update installs, got an error from the boot loader: > ZFS: can't find pool by guid > ZFS: can't find pool by guid > ZFS: can't find pool by guid > can't load 'kernel' To follow up, does anyone have any suggestions for how to recover from this? Cheers, Jeff C. > Booting from memstick USB into liveCD to get some diagnostics: > root@:~ # gpart show =>> 34 5860533101 da0 GPT (2.7T) > 34 6 - free - (3.0K) > 40 1024 1 freebsd-boot (512K) > 1064 16777216 2 freebsd-swap (8.0G) > 16778280 5843754848 3 freebsd-zfs (2.7T) > 5860533128 7 - free - (3.5K) =>> 34 5860533101 diskid/DISK-Z1Z36VFN00009426QDUJ GPT (2.7T) > 34 6 - free - (3.0K) > 40 1024 1 freebsd-boot (512K) > 1064 16777216 2 freebsd-swap (8.0G) > 16778280 5843754848 3 freebsd-zfs (2.7T) > 5860533128 7 - free - (3.5K) =>> 34 5860533101 da1 GPT (2.7T) > 34 6 - free - (3.0K) > 40 1024 1 freebsd-boot (512K) > 1064 16777216 2 freebsd-swap (8.0G) > 16778280 5843754848 3 freebsd-zfs (2.7T) > 5860533128 7 - free - (3.5K) =>> 34 5860533101 da2 GPT (2.7T) > 34 6 - free - (3.0K) > 40 1024 1 freebsd-boot (512K) > 1064 16777216 2 freebsd-swap (8.0G) > 16778280 5843754848 3 freebsd-zfs (2.7T) > 5860533128 7 - free - (3.5K) =>> 34 5860533101 da3 GPT (2.7T) > 34 6 - free - (3.0K) > 40 1024 1 freebsd-boot (512K) > 1064 16777216 2 freebsd-swap (8.0G) > 16778280 5843754848 3 freebsd-zfs (2.7T) > 5860533128 7 - free - (3.5K) =>> 34 5860533101 diskid/DISK-Z1Z38VVZ000094274QNB GPT (2.7T) > 34 6 - free - (3.0K) > 40 1024 1 freebsd-boot (512K) > 1064 16777216 2 freebsd-swap (8.0G) > 16778280 5843754848 3 freebsd-zfs (2.7T) > 5860533128 7 - free - (3.5K) =>> 34 5860533101 diskid/DISK-Z1Y084BY GPT (2.7T) > 34 6 - free - (3.0K) > 40 1024 1 freebsd-boot (512K) > 1064 16777216 2 freebsd-swap (8.0G) > 16778280 5843754848 3 freebsd-zfs (2.7T) > 5860533128 7 - free - (3.5K) =>> 34 5860533101 diskid/DISK-Z1Y2YWBN0000C524DDKE GPT (2.7T) > 34 6 - free - (3.0K) > 40 1024 1 freebsd-boot (512K) > 1064 16777216 2 freebsd-swap (8.0G) > 16778280 5843754848 3 freebsd-zfs (2.7T) > 5860533128 7 - free - (3.5K) =>> 1 62652415 da4 MBR (30G) > 1 1600 1 !239 (800K) > 1601 1505616 2 freebsd [active] (735M) > 1507217 61145199 - free - (29G) =>> 0 1505616 da4s2 BSD (735M) > 0 16 - free - (8.0K) > 16 1505600 1 freebsd-ufs (735M) =>> 1 62652415 diskid/DISK-0336216080014934 MBR (30G) > 1 1600 1 !239 (800K) > 1601 1505616 2 freebsd [active] (735M) > 1507217 61145199 - free - (29G) =>> 0 1505616 diskid/DISK-0336216080014934s2 BSD (735M) > 0 16 - free - (8.0K) > 16 1505600 1 freebsd-ufs (735M) > (da4 is the USB drive, obviously) > root@:~ # zpool import > ZFS filesystem version: 5 > ZFS storage pool version: features support (5000) > pool: zroot > id: 12421595622411140545 > state: ONLINE > status: Some supported features are not enabled on the pool. > action: The pool can be imported using its name or numeric identifier, though > some features will not be available without an explicit 'zpool upgrade'. > config: > zroot ONLINE > raidz1-0 ONLINE > diskid/DISK-Z1Z36VFN00009426QDUJ ONLINE > diskid/DISK-Z1Z38VVZ000094274QNB ONLINE > diskid/DISK-Z1Y084BY ONLINE > diskid/DISK-Z1Y2YWBN0000C524DDKE ONLINE > pool: zroot > id: 6087619269570541526 > state: ONLINE > status: Some supported features are not enabled on the pool. > action: The pool can be imported using its name or numeric identifier, though > some features will not be available without an explicit 'zpool upgrade'. > config: > zroot ONLINE > raidz1-0 ONLINE > da0p3 ONLINE > da1p3 ONLINE > da2p3 ONLINE > da3p3 ONLINE > Not able to import zroot by name: > root@:~ # zpool import -fR /mnt zroot > cannot import 'zroot': more than one matching pool > import by numeric ID instead > What's the best way to fix this? > Also the zpool hasn't been upgraded in a long time, and I wonder if > that interacted with the 11.2 boot loader code change: > https://www.freebsd.org/releases/11.2R/relnotes.html#boot-loader >> 9.1. Boot Loader Changes >> >> The boot code and loader(8) have been updated to check for >> unsupported ZFS feature flags. If unsupported features are active, >> the pool is not considered as a bootable pool, and a diagnostic >> message is printed to the console. [r321519] > and the related patch: > https://svnweb.freebsd.org/base?view=revision&revision=321519 > If we should do a zpool upgrade, can that be done from the liveCD > safely? This is a hot spare of a production system, and it would be > nice if it could be restored to operation with a few commands. > There's (always) the chance that a hard drive is wearing out too, > though recent zpool scrubs seem fine, and smartctl errors look ok. > Much easier to fix from a running system if needed. > Thanks in advance for any advice! > Cheers, > Jeff C. > -- > Jeff Chan > mailto:jeffc@supranet.net > _______________________________________________ > freebsd-fs@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" -- Jeff Chan mailto:jeffc@supranet.net http://www.jeffchan.com/