Bug #14687
closed
Error in boot messages about missing ``/boot/loader.conf.d`` directory
Added by Steve Wheeler over 1 year ago.
Updated 7 days ago.
Category:
Operating System
Affected Architecture:
amd64
Description
This is defined in /boot/defaults/loader.conf:
loader_conf_dirs="/boot/loader.conf.d"
It produces the error at boot:
Failed to load conf dir '/boot/loader.conf.d': not a directory
This should be removed or the directory added to prevent the error.
Tested 23.05.1
Stock FreeBSD comes with the directory.
Thus the best long term option is to just add one, but I don't know to do it in a pfSense-friendly manner so someone(tm) else will have to take this.
- Subject changed from Failed to load conf dir '/boot/loader.conf.d': not a directory to Error in boot messages about missing ``/boot/loader.conf.d`` directory
I spot checked several systems here and they all had that directory already. Does this only appear on a new fresh install?
My system (6100) was a clean & fresh install for 23.05 (now on 23.09d) and the loader.conf.d directory is in place and empty.
☕️
- Plus Target Version changed from 23.09 to 24.03
Moving this ahead for now since it doesn't appear to be a problem and may not even be actionable. If that is the case we can close it out.
- Plus Target Version changed from 24.03 to 24.07
The directory is there even on a completely fresh install. I'm not sure what, if anything, we need to do here.
- Plus Target Version changed from 24.07 to 24.08
- Plus Target Version changed from 24.08 to 24.11
- Plus Target Version changed from 24.11 to 25.01
- Status changed from New to Closed
- Target version deleted (
2.8.0)
- Plus Target Version deleted (
25.01)
This can be reopened if there are additional reports or if it can be reproduced in recent versions.
Also available in: Atom
PDF