Thank you _martin for helping and providing such creative ideas and thank you covacat for pointing to the right tracks ;) and thanks to others as well ;)
That's a good idea! I was thinking maybe I'm not using the good boot file...
I mean I used
sudo gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ada0
which pulled the file from the 11.2-RELEASE from the rescue OS.
I have now done
sudo gpart bootcode -b /mnt/boot/pmbr -p /mnt/boot/gptzfsboot...
I was responding to gpw928 about the bootfs path and beadm thing ;)
ls -latrh /mnt/boot | tail -5
drwxr-xr-x 2 root wheel 809B Mar 16 10:19 kernel
drwxr-xr-x 2 root wheel 808B Mar 16 10:19 kernel.old
drwxr-xr-x 19 root wheel 25B Mar 16 10:35 ..
drwxr-xr-x 15 root wheel...
Not exactly it's a random network drive connected to the machine, it acts as boot device/OS.
I could not mess up with the bootfs parameter as the zpool is readonly due to the 11.2-RELEASE zfs differences.
Will try that, will have to set a VM first.
The zroot/ROOT/default path is a beadm way I think.
Maybe I messed up things when creating the mountpoints, this was working fine previously though..
What I did at the time
zpool set bootfs=zroot/root zroot
zfs set mountpoint=/ zroot/root
zfs set mountpoint=/zroot zroot
zfs set mountpoint=/tmp...
It's mainly a cloud provider but here it is a dedicated host, the rescue console is an OS on another drive that boots the device and loads the server drive as an external drive, so you can have a `rescue` access through ssh.
The most up to date FreeBSD version they provide is 11.2 sadly.
Good...
Weird this doesn't change a thing...
System is not UEFI
sysctl machdep.bootmethod
machdep.bootmethod: BIOS
Still not possible to log in and no update in /var/run/dmesg.boot or /var/log/messages
Am I missing something?
Upgraded from 12 and yes pool was upgraded after a while...
Do you mean doing this?
zpool set bootfs=zroot/root zroot
I'm reading [upgrading-root-pools-on-freebsd-13.79911 right now..
Thanks for the help ;)
Update from FreeBSD 13.0-RELEASE-p7 to FreeBSD 13.0-RELEASE-p8.
File System is ZFS.
Rescue console is stuck at FreeBSD 11.2-RELEASE so I can only mount the ZFS pool read only...
sudo zpool import -o altroot=/mnt -o cachefile=/var/tmp/zpool.cache -d /dev/gpt zroot -f...
Hello,
I just did the FreeBSD 13.0-RELEASE-p8 update today.
After reboot I no longer have access (connection timed out).
I was able to get in through a rescue console, the service doesn't have a KVM over IP.
/var/run/dmesg.boot clearly shows nothing (dated from previous reboot from january)...
Or... is it just that FreeBSD 11.2p8 enforces use of .ssh/authorized_keys even if /etc/ssh/sshd_config overrides it with AuthorizedKeysFile .ssh/authorized_keys2?
Because changing both the filename and the /etc/ssh/sshd_config allowed me to log again to the box.
Really weird…
Hello,
I was updating jails with mergemaster -iFU after 11.2p8 update and run it on main host by inadvertance.
I realized this when mergemaster output looked suspicious :
*** The following files exist in /etc/rc.d but not in /var/tmp/temproot/etc/rc.d/:
blacklistd iovctl ipfw_netflow ypldap...
As stated as the man page and as you understood it, 10.1-RELEASE in that case. Read this https://forums.freebsd.org/threads/ezjail-and-major-host-upgrades.52203/#post-292852 for a more complete process.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.