On 4/29/14, 11:44 PM, Chris Buechler wrote: > On Tue, Apr 29, 2014 at 11:38 AM, David Newman <[email protected]> > wrote: >> On 4/29/14, 12:28 AM, Chris Buechler wrote: >> >>>> Still, I was unable do the 2.1.2 update from the GUI. The system >>>> remained offline after 1 hour. >>>> >>>> After power-cycling the system, both partitions still came up with 2.1.1. >>>> >>> >>> Check the upgrade log under Diagnostics>Nanobsd, should have info as to why. >> >> Here's that log: >> >> http://pastebin.com/h4iPtZ7k >> >> My untrained eyes saw these: >> >> 1. The April 8 date -- is this from the 2.1.1 upgrade and not 2.1.2? >> > > Yeah so it never attempted to upgrade apparently. The few times I've > seen that, it's been on an ALIX and because it ran out of RAM. They > were running usual loads at around 240 MB RAM usage or so, and the > upgrade attempt ran it out of RAM. If you're that tight on RAM, might > have to disable some services, upgrade, then re-enable so you have > enough RAM. And you'll probably want to find some hardware with more > RAM.
Agreed. This 2d13 has 256 Mbytes of RAM but apparently that's not enough, even with all services disabled. The console upgrade also failed, though at least this time it wrote out a log. The only problem I see is fdisk complaining about no valid partition, same as last time. It's possible this is related to this being 4G Sandisk CF cards, and modern 2G and 4G Sandisk cards producing alignment errors. I'm going to have to go pull CF card and reflash it. dn dn _______________________________________________ List mailing list [email protected] https://lists.pfsense.org/mailman/listinfo/list
