https://redmine.pfsense.org/https://redmine.pfsense.org/favicon.ico?16780521162010-05-04T01:02:17ZpfSense bugtrackerpfSense - Bug #560: loader.conf is empty after a firmware update.https://redmine.pfsense.org/issues/560?journal_id=17712010-05-04T01:02:17ZChris Buechlercbuechler@gmail.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Feedback</i></li></ul><p>should be resolved by: <br /><a class="external" href="https://rcs.pfsense.org/projects/pfsense-tools/repos/mainline/commits/7bd58f242717f23919756bbaa0a82cbcd2cf6daa">https://rcs.pfsense.org/projects/pfsense-tools/repos/mainline/commits/7bd58f242717f23919756bbaa0a82cbcd2cf6daa</a></p>
<p>needs test</p> pfSense - Bug #560: loader.conf is empty after a firmware update.https://redmine.pfsense.org/issues/560?journal_id=17722010-05-04T01:11:46ZJim Pingle
<ul></ul><p>Would we not need /boot/loader /boot/loader.rc and /boot/loader.4th - especially over a base OS version upgrade?</p>
<p>If we need special knobs in loader.conf we could script those into a post-upgrade command (but we rarely need something there anyhow).</p> pfSense - Bug #560: loader.conf is empty after a firmware update.https://redmine.pfsense.org/issues/560?journal_id=17772010-05-04T12:11:02ZJim Pingle
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Resolved</i></li></ul><p>Looks like the latest fix from Scott is good:</p>
<p><a class="external" href="https://rcs.pfsense.org/projects/pfsense-tools/repos/mainline/commits/3a0c3546a842df63d7d6316360cd6087704cffe9">https://rcs.pfsense.org/projects/pfsense-tools/repos/mainline/commits/3a0c3546a842df63d7d6316360cd6087704cffe9</a></p> pfSense - Bug #560: loader.conf is empty after a firmware update.https://redmine.pfsense.org/issues/560?journal_id=28392010-08-08T21:39:50ZChris Buechlercbuechler@gmail.com
<ul><li><strong>Status</strong> changed from <i>Resolved</i> to <i>New</i></li></ul><p>this reportedly isn't fixed. <a class="external" href="http://forum.pfsense.org/index.php/topic,27257.0.html">http://forum.pfsense.org/index.php/topic,27257.0.html</a></p> pfSense - Bug #560: loader.conf is empty after a firmware update.https://redmine.pfsense.org/issues/560?journal_id=37642010-11-20T22:54:05ZErik Fonnesbeck
<ul></ul><p>Is this still an issue on full installs? Note that there is a separate ticket for this on nanobsd.</p> pfSense - Bug #560: loader.conf is empty after a firmware update.https://redmine.pfsense.org/issues/560?journal_id=37672010-11-20T23:15:21ZJim Pingle
<ul></ul><p>I believe it still is, as a VM I keep updated has an empty loader.conf when it should the default entries.</p>
<p>It's a different issue, though, in that I think somehow the builder is putting an empty loader.conf in the update, but the full/proper one is on the .iso and gets carried over from there.</p> pfSense - Bug #560: loader.conf is empty after a firmware update.https://redmine.pfsense.org/issues/560?journal_id=39072010-11-29T17:53:56ZScott Ullrichsullrich@gmail.com
<ul></ul><p>I just downloaded <a class="external" href="http://snapshots.pfsense.org/FreeBSD_RELENG_8_1/i386/pfSense_HEAD/updates/pfSense-Full-Update-2.0-BETA4-20101127-0055.tgz">http://snapshots.pfsense.org/FreeBSD_RELENG_8_1/i386/pfSense_HEAD/updates/pfSense-Full-Update-2.0-BETA4-20101127-0055.tgz</a> and do not see a /boot/loader.conf .. The issue seems resolved?</p> pfSense - Bug #560: loader.conf is empty after a firmware update.https://redmine.pfsense.org/issues/560?journal_id=39112010-11-29T18:09:46ZScott Ullrichsullrich@gmail.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Feedback</i></li></ul> pfSense - Bug #560: loader.conf is empty after a firmware update.https://redmine.pfsense.org/issues/560?journal_id=39152010-11-29T18:28:02ZJim Pingle
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>New</i></li></ul><p>I just tested it again, it's still getting wiped out somehow during the update process.</p> pfSense - Bug #560: loader.conf is empty after a firmware update.https://redmine.pfsense.org/issues/560?journal_id=47612011-01-20T15:58:34ZR M
<ul></ul><p>I'm seeing a slightly different behaviour which may be unique to having serial console enabled after a an update.</p>
<p>After an update, the previous contents from loader.conf is replaced with just a single one line entry console="comconsole" which is checked from the interface to enable com output on a headless box.</p>
<p>Either way, the previous values added to loader.conf are not being carried over after an update.</p>
<p>Tested with <a class="external" href="http://snapshots.pfsense.org/FreeBSD_RELENG_8_1/amd64/pfSense_HEAD/updates/pfSense-Full-Update-2.0-BETA5-amd64-20110119-1309.tgz">http://snapshots.pfsense.org/FreeBSD_RELENG_8_1/amd64/pfSense_HEAD/updates/pfSense-Full-Update-2.0-BETA5-amd64-20110119-1309.tgz</a></p> pfSense - Bug #560: loader.conf is empty after a firmware update.https://redmine.pfsense.org/issues/560?journal_id=48062011-01-25T19:24:16ZR M
<ul></ul><p>Apologies. Please disregard my previous comment.</p>
<p>Wrongly perceived the issue to be that values entered manually in loader.conf never get sucked back in after an upgrade when in fact that is the intended behaviour not to carry manual values over during updates. It has been conveyed to me by Jim P (<a class="external" href="http://redmine.pfsense.org/issues/1221#note-5">http://redmine.pfsense.org/issues/1221#note-5</a>) that it's not really a problem since manual changes are never supposed to go in loader.conf, but loader.conf.local instead since it was easier to handle it that way.</p>
<p>After having essentially posted a comment unrelated to the issue at hand, I'm providing this response to clear up any possible confusion that my last comment may have caused.</p> pfSense - Bug #560: loader.conf is empty after a firmware update.https://redmine.pfsense.org/issues/560?journal_id=48222011-01-28T16:51:13ZJim Pingle
<ul></ul><p>I discovered another vector for loader.conf being emptied - it's included in the kernel archives (kernel_Dev.gz, kernel_SMP.gz, kernel_uniprocessor.gz, kernel_wrap.gz, kernel_wrap_Dev.gz). So when a kernel is unpacked, the empty loader.conf from the kernel archive clobbers whatever is on the filesystem.</p> pfSense - Bug #560: loader.conf is empty after a firmware update.https://redmine.pfsense.org/issues/560?journal_id=48562011-02-05T12:12:05ZScott Ullrichsullrich@gmail.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Feedback</i></li></ul><p>This should be resolved. I fixed the bug in the kernel upgrade code that was causing this.</p> pfSense - Bug #560: loader.conf is empty after a firmware update.https://redmine.pfsense.org/issues/560?journal_id=50542011-03-03T01:24:49ZBraden McGrathbraden@big-geek.net
<ul></ul><p>Just upgraded from 1.2.3 Embedded to 2.0-RC1 Embedded. Loader.conf was NOT blank, but the changes I had put in there were gone.</p>
<p>Knowing now that loader.conf*.local* is the preferred spot for customizations, this makes sense. Is there code in the flash/upgrade process to preserve the .local version? On embedded, you guys are disabling DMA on ATA/ATAPI. While this is admittedly safer, it's bad juju on an established Embedded machine that is already using DMA. Why? Because after upgrade, all of the packages get reinstalled... which causes a boatload of disk access, which is painful if it's still using PIO.</p>
<p>If the root of the bug is that loader.conf is <strong>empty</strong> after an upgrade, this bug is resolved in RC1, my loader.conf was "decustomized" but the sane defaults were in there.</p> pfSense - Bug #560: loader.conf is empty after a firmware update.https://redmine.pfsense.org/issues/560?journal_id=50552011-03-03T01:26:13ZBraden McGrathbraden@big-geek.net
<ul></ul><p>Just upgraded from 1.2.3 Embedded to 2.0-RC1 Embedded. Loader.conf was NOT blank, but the changes I had put in there were gone.</p>
<p>Knowing now that <strong>loader.conf.local</strong> is the preferred spot for customizations, this makes sense. Is there code in the flash/upgrade process to preserve the .local version? On embedded, you guys are disabling DMA on ATA/ATAPI. While this is admittedly safer, it's bad juju on an established Embedded machine that is already using DMA. Why? Because after upgrade, all of the packages get reinstalled... which causes a boatload of disk access, which is painful if it's still using PIO.</p>
<p>If the root of the bug is that loader.conf is <strong>empty</strong> after an upgrade, this bug is resolved in RC1, my loader.conf was "decustomized" but the sane defaults were in there.</p> pfSense - Bug #560: loader.conf is empty after a firmware update.https://redmine.pfsense.org/issues/560?journal_id=50562011-03-03T01:56:05ZChris Buechlercbuechler@gmail.com
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Resolved</i></li></ul><p>overwriting the changes is normal and unavoidable, just make sure your customizations are in .local and you can make that change prior to upgrading so it'll take effect after upgrading. .local is always retained and not modified.</p>