https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236981
Bug ID: 236981 Summary: loader_lua does not boot from encrypted ZFS pool after upgrading from r345243 to r345759 Product: Base System Version: CURRENT Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: iz-rp...@hs-karlsruhe.de The base r345759 boot failes because it can not find the encrypted ZFS pool any more. The console looks like: BTX loader 1.00 BTX version 1.02 Consoles: internal video/keyboard BIOS drive C: is disk0 BIOS drive D: is disk1 BIOS drive E: is disk2 BIOS 630kb/30... available memory FreeBSD/x86 bootstrap loader, Revision 1.1 ZFS: can't find pool by guid ZFS: can't find pool by guid ZFS: can't find pool by guid Startup error in /boot/lua/loader.lua: LUA ERROR: cannot open /boot/lua/loader.lua: invalid argument. can't load 'kernel' Type '?' for a list of commands... I managed to get the machine back by - booting from FreeBSD-13.0-CURRENT-amd64-20190321-r345355-memstick.img - attaching the partitions containing the ZFS boot pool with "geli attach" - using "zpool import -f" to import the pool and - replacing the base r345759 loader (linked with loader_lua) with the base r345243 loader_lua. So the machine is currently bootstraping with base r345243 loader_lua and running the base r345759 kernel and world. Searching the commit logs between base r345243 and base r345759 leads me to suspect base r345330 "loader: fix loading of kernels with . in path", but I did not had the time to just reverse base r345330 and give the resulting loader_lua a try. Ralf -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"