From nobody Wed Apr 13 13:53:40 2022 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id A1EAB1AF01D5 for ; Wed, 13 Apr 2022 13:53:59 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from www121.sakura.ne.jp (www121.sakura.ne.jp [153.125.133.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4KdkbB2XBCz4V28 for ; Wed, 13 Apr 2022 13:53:57 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from kalamity.joker.local (123-1-31-137.area1b.commufa.jp [123.1.31.137]) (authenticated bits=0) by www121.sakura.ne.jp (8.16.1/8.16.1/[SAKURA-WEB]/20201212) with ESMTPA id 23DDrfJT091153; Wed, 13 Apr 2022 22:53:42 +0900 (JST) (envelope-from junchoon@dec.sakura.ne.jp) Date: Wed, 13 Apr 2022 22:53:40 +0900 From: Tomoaki AOKI To: Ronald Klop , Dennis Clarke Cc: freebsd-current@freebsd.org Subject: Re: main-n254654-d4e8207317c results in "no pools available to import" Message-Id: <20220413225340.a610f6528c2c5dc6937ed33a@dec.sakura.ne.jp> In-Reply-To: <585833961.324.1649766560673@localhost> References: <778a795c-5413-9c79-5312-e34dd6bb29c1@blastwave.org> <010001801d7dde5c-332ee2e3-0df9-4112-9081-46d99b689ea5-000000@email.amazonses.com> <585833961.324.1649766560673@localhost> Organization: Junchoon corps X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd13.0) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4KdkbB2XBCz4V28 X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of junchoon@dec.sakura.ne.jp has no SPF policy when checking 153.125.133.21) smtp.mailfrom=junchoon@dec.sakura.ne.jp X-Spamd-Result: default: False [-1.36 / 15.00]; RCVD_TLS_LAST(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; MV_CASE(0.50)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[sakura.ne.jp]; AUTH_NA(1.00)[]; TO_DN_SOME(0.00)[]; HAS_ORG_HEADER(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_SHORT(-0.76)[-0.765]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; MLMMJ_DEST(0.00)[freebsd-current]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:7684, ipnet:153.125.128.0/18, country:JP]; RCVD_COUNT_TWO(0.00)[2]; MID_RHS_MATCH_FROM(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[123.1.31.137:received] X-ThisMailContainsUnwantedMimeParts: N On Tue, 12 Apr 2022 14:29:20 +0200 (CEST) Ronald Klop wrote: > > Van: Thomas Laus > Datum: dinsdag, 12 april 2022 13:17 > Aan: freebsd-current@freebsd.org > Onderwerp: Re: main-n254654-d4e8207317c results in "no pools available to import" > > > > On 4/11/22 14:18, Ronald Klop wrote: > > > On 4/11/22 17:17, Dennis Clarke wrote: > > >> > > >> Did the usual git pull origin main and buildworld/buildkernel but >> after installkernel the machine will not boot. > > >> > > >> The rev seems to be main-n254654-d4e8207317c. > > >> > > >> I can boot single user mode and get a command prompt but nothing past > > >> that. Is there something borked in ZFS in CURRENT ? > > >> > > > Up until now you are the only one with this error on the mailinglist > today. So I doubt something is borked. > > > You could consider to share more details about your setup to help people > to think along with you. > > > > > I can confirm this issue. My last update was 'main-n253996-1b3af110bc' from March 31, 2022 that worked fine. My update yesterday received the same error and refused to boot past looking for kernel modules. I did receive the "no pools available to import" message a couple of lines earlier. My hardware is a Dell Inspiron laptop with a SSD and ZFS filesystem. I have a little time today and plan on git reverting back to March 31 to further isolate the problem. > > > > Tom > > > > -- > > Public Keys: > > PGP KeyID = 0x5F22FDC1 > > GnuPG KeyID = 0x620836CF > > > > > > > > > > > Hi, > > Are you guys both using NVME or EFI? Just wondering if the common problem is in ZFS or some other component. > > Ronald. > My booting-fine installation is still at git c79331a42c308139828c1117f49224bb83617a53 and is using both NVMe and UEFI, but via nda, not nvd. Non-Geli-encrypted bootfs. Note that my BOOTx64.efi is not a copy of loader.efi, but boot1.efi applied latest patch uploaded on Bug 207940 [1]. [1] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207940 Basically, I upgrade pool only when I switch to latest stable branch that is just created, meaning that the zfs codes and boot codes are basically 100% match on main and latest stable. This way, both pools of main environment and of stable (now stable/13) environment have 100% equal features. -- Tomoaki AOKI