Project

General

Profile

Bug #10708

ZFS bootpool boot symlink issue

Added by Paul Magid about 1 month ago. Updated 21 days ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Upgrade
Target version:
Start date:
06/27/2020
Due date:
% Done:

0%

Estimated time:
Affected Version:
2.5.0
Affected Architecture:
amd64

Description

Using 2.5.0-DEVELOPMENT when I do an install that creates a zfs mirror (MBR), the boot directory is actually a symlink to the boot directory in the bootpool pool. As soon as I do an upgrade to a newer build the boot directory symlink is overwritten and a directory called boot is created. The boot directory in bootpool goes out of sync with the boot directory that is now physically present on the zroot pool. This causes issues with kernel module mismatches etc.

History

#1 Updated by Paul Magid about 1 month ago

To clarify: upon upgrade a physical directory called boot is created in the zroot pool over the symlink...

#2 Updated by Louis van Breda 21 days ago

Reading this symlink issue I do remember that in the past days I did notice messages, indication that some files could not be found. I did noticed that during a crash recovery startup. Just for info might be related. I do not know.

Loading configuration … done
Sh: /usr/local/pkg/pfblockerng/pfblockerng.sh: not found (note I am not even using “pfblockerng” that apart)

Starting CRON … done
ERROR: It was not possible to identify which pfSense kernel is installed

Well before this occurred I did install pfSense using an USB-install disk, in combination with an USB-config disk (to automatic recover the old config). Sometimes I have the impression that it was looking for the USB-stick, not present any more.

Also available in: Atom PDF