Date: Sat, 1 Aug 2020 20:02:16 -0400 (EDT) From: Doug Denault <doug@safeport.com> To: freebsd-questions@FreeBSD.ORG Subject: freebsd-update - Cannot identify running kernel Message-ID: <alpine.BSF.2.00.2008012000320.83675@bucksport.safeport.com>
next in thread | raw e-mail | index | archive | help
I did an update from 11.3 --> 12.1 that did not seem to work. That turned out to be my error but I rolled back to 11.3. I have a 12.0 system that did not have the error so I thought I would update to 12.0 to try to get a handle on my problem. This update did not exactly work. It will boot and I suspect I can do anything not requiring access to /boot. The zfs boot process is not bothered by this problem. zpool list NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT bootpool 1.98G 274M 1.72G - - 15% 13% 1.00x ONLINE - zroot 920G 7.76G 912G - - 0% 0% 1.00x ONLINE - zfs list NAME USED AVAIL REFER MOUNTPOINT bootpool 273M 1.59G 271M /bootpool zroot 7.76G 883G 96K /zroot zroot/ROOT 5.15G 883G 96K none zroot/ROOT/default 5.15G 883G 5.15G / zroot/tmp 168K 883G 168K /tmp zroot/usr 2.59G 883G 96K /usr zroot/usr/home 682M 883G 682M /usr/home zroot/usr/ports 742M 883G 742M /usr/ports zroot/usr/src 1.20G 883G 1.20G /usr/src zroot/var 12.5M 883G 96K /var zroot/var/audit 96K 883G 96K /var/audit zroot/var/crash 96K 883G 96K /var/crash zroot/var/log 572K 883G 572K /var/log zroot/var/mail 11.5M 883G 11.5M /var/mail zroot/var/tmp 96K 883G 96K /var/tmp In comparing this with a zfs system I have not so abused, I can tell that bootpool needs to be added to the zroot/ROOT/default as boot thus the file system visible to the OS would have /boot in it. I know my terminology is likely all messed up, I am a zfs newbie. Anyway bootpool/boot/ has the right stuff: ls bootpool/boot/ ./ delay.4th loader.efi* menu.4th ../ device.hints loader.rc menu.rc beastie.4th dtb/ loader_4th* menusets.4th boot efi.4th loader_4th.efi* modules/ boot0 entropy loader_lua* pmbr boot0sio firmware/ loader_lua.efi* pxeboot boot1 frames.4th loader_simp* screen.4th boot1.efi* gptboot loader_simp.efi* shortcuts.4th boot1.efifat gptzfsboot logo-beastie.4th support.4th boot2 isoboot logo-beastiebw.4th userboot.so brand-fbsd.4th kernel/ logo-fbsdbw.4th userboot_4th.so brand.4th kernel.old/ logo-orb.4th userboot_lua.so cdboot loader* logo-orbbw.4th version.4th check-password.4th loader.4th lua/ zfs/ color.4th loader.conf mbr zfsboot defaults/ loader.conf.orig menu-commands.4th zfsloader* So ... is my analysis correct? If so how do it put bootpool/boot/ where "it belongs"? _____ Douglas Denault http://www.safeport.com support@safeport.com Voice: 301-217-9220 Fax: 301-217-9277
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.2008012000320.83675>