Update 2.1.5 to 2.2 fails on APU
-
If the problem is only related to bsnmpd and for those who can live without snmp, isn't it enough to simply disable snmp before upgrading and then upgrade to 2.2 ?
-
Someone that can replicate this, could you get me a config that exhibits the issue? I've tried a wide range of things and haven't found a way to replicate. Could PM it to me.
@GLR:
If the problem is only related to bsnmpd and for those who can live without snmp, isn't it enough to simply disable snmp before upgrading and then upgrade to 2.2 ?
Yes, that would be adequate.
-
Isn't it enough to (try to) run 2.2 on an APU unit with bsnmpd enabled ?
-
Eh???
-
We've tracked down the source of this one. It appears to be only when you're running from mSATA and have no SD card installed.
https://redmine.pfsense.org/issues/4403Not down to a specific root cause yet, just know it appears to be specific to that circumstance where you don't have a SD card in the system, and you enable SNMP.
Anyone here seeing this happen who has a SD card installed in their APU?
-
Yes, I don't have any mSATA module but only a SD card.
-
Hi all
I've a similar same problem. As yu can see below the system is on SD.
I tried to upgrade with the webGui. Neither Manual Update nor Auto Update were working. It just rebooted with the old version.
CPU:AMD G-T40E Processor, 2 CPUs: 1 package(s) x 2 core(s)
Version: 2.1.5-RELEASE (amd64) built on Mon Aug 25 07:44:45 EDT 2014
Plattform: nanobsd (4g)Did anyone manage to update on such configuration from 2.15 to 2.2? Any advice is most welcome!
Many thanks!
Patrick -
If it rebooted to the previous version it's failed to update for some reason, not the same issue as described by this thread. Check the upgrade log in Diagnostics > Nanobsd for errors. Start a new thread if there's nothing in there about bsnmpd.
Steve
-
This looks a whole lot like the upgrade failure that I got on my soekris 6501. I'm running mSATA only, but I don't use snmp, and that's an Atom e6xx chip. i386 full install.
-
Hi
In the meanwhile I found out that can't do changes anymore. It seemed that the hd is only readonly mountable.
I therefore decided to reinstall the whole system on v2.2. With the backup I got it finally working after a fair amount of efforts with the new version of pfsense.
Shit happens. :)
Patrick
-
Indeed it does! ::)
In NanoBSD the filesystem is supposed to be mounted read-only. It gets re-mounted as read write only when a config change is saved. It is designed that way to prevent excess writes to flash media.
https://www.freebsd.org/doc/en_US.ISO8859-1/articles/nanobsd/Steve
