Date: Tue, 12 Apr 2022 14:10:25 +0200 From: Alexander Leidinger <Alexander@leidinger.net> To: Thomas Laus <lausts@acm.org> Cc: freebsd-current@freebsd.org Subject: Re: main-n254654-d4e8207317c results in "no pools available to import" Message-ID: <20220412141025.Horde.qFDoIMkAMle-xQvg6sskxpe@webmail.leidinger.net> In-Reply-To: <010001801d7dde5c-332ee2e3-0df9-4112-9081-46d99b689ea5-000000@email.amazonses.com> 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>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] Quoting Thomas Laus <lausts@acm.org> (from Tue, 12 Apr 2022 11:17:09 +0000): > 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. Some data point from a system with current as of 2022-04-06 15:23 (not sure if related or a red hering): pool imports fine, but iocage spits out a lot of "setting up zpool for iocage usage" during an "iocage list". And it doesn't auto-start the iocage jails. As I only updated the OS and not the ports (besides: no change to iocage in ports), it may be the case that some kind of detection logic in zfs code is now misbehaving in some cases... Bye, Alexander. -- http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIzBAABCAAdFiEER9UlYXp1PSd08nWXEg2wmwP42IYFAmJVbDEACgkQEg2wmwP4 2IbQfQ/8DdNgr+rLnK15HARMpeth+fNu8PZwifCcHZbtwLq/krCyfoX743ok8YaB dZ32rMGT9c2jWw9oLuwjCXCemFbsxIAFsHjxRBcYB1l6CKfLDfYf+O4fsrywiwfM G2Gu4gFMJi01Zi2wVCbsml3B4jBmtN2TVUQgT9DRZBsZMy6hTAlQqj+HnOsdJ6L1 d/WrIIwvnv8PGH4vZj3tpTnMqj+8kPRIBvantQkO76lH5dixY0FvKdfDojLSZxee qNELUmrSfwhjYvVkI6GeYubWduHixyqMZytAn2DHgGkcX/RYkPDZrlf4ySKppGOJ VEqqe3YMMyyEg2fSo4j36W32KkpsEa0aZtjfgBRqaLuoNOSZj3BtdR6aOhNrV0Wg 7dMINcYmg4GnEnqkMveh/+9/DCQ+DZIpKkFgFqOKUsRmzNGSqX9wQB1waufT1YP7 jKTnpIENfd4LIi40DFT/hWL1dJtMAivaLGFfQne/d7jec4bkLGEau7f5hHEY8MzP thcgFSP20YA1JFuQVdKmHrBx3+2NczdGG9kT5Ie9yhW3Zrty+2qlIB4EDaGnqgP3 Mq2KbeWBKCVXOnZRxdSSkl7ifX5Uss7CPvW31I9KzLIsey7beE2fYFfFqChSFBwu nHUhF8hYfcQG+b4DA8YmgwJesXaoEzcOJK4Hv+N7kjcvRoNUjUk= =qQqR -----END PGP SIGNATURE-----help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20220412141025.Horde.qFDoIMkAMle-xQvg6sskxpe>