Date: Wed, 13 Apr 2022 22:53:40 +0900 From: Tomoaki AOKI <junchoon@dec.sakura.ne.jp> To: Ronald Klop <ronald-lists@klop.ws>, Dennis Clarke <dclarke@blastwave.org> 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> <cad68cb5-301a-0c8d-36fa-731b04d1a4eb@klop.ws> <010001801d7dde5c-332ee2e3-0df9-4112-9081-46d99b689ea5-000000@email.amazonses.com> <585833961.324.1649766560673@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 12 Apr 2022 14:29:20 +0200 (CEST) Ronald Klop <ronald-lists@klop.ws> wrote: > > Van: Thomas Laus <lausts@acm.org> > 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 <junchoon@dec.sakura.ne.jp>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20220413225340.a610f6528c2c5dc6937ed33a>