I should note that in addition to the symptoms I mentioned earlier that followed the 2.2.0 upgrade, there were several messages like this on the console:
cannot get uid for user 'root' ...and similar. Unfortunately I don't have the full context of those logs. Thank you- Erik On Tue, Jan 27, 2015 at 8:23 PM, Erik Anderson <[email protected]> wrote: > I just attempted a self-upgrade from 2.1.5-RELEASE to 2.2.0-RELEASE on > a Soekris 6501-50. Storage is a 64GB Sandisk SSD with the full install > on it (not NanoBSD). > > After the upgrade, the router rebooted as expected and then came > *partially* back up, as in the interfaces were configured and it would > NAT/route packets, but none of the daemons were started correctly > (DHCP, DNS Forwarder, SSH, etc.). Even the web configurator was > throwing 500 errors. > > After attaching to the serial console, I noticed php-fpm errors, which > would explain the web configurator issues, but not the rest of the > daemons failure to start. > > Next, I decided to do a fresh 2.2 install, so I downloaded the serial > memstick image, burned it to a usb drive and booted off of it. I ran > the installation wizard, which appeared to go just fine (no errors). > Then rebooted, only to find out that the BIOS doesn't recognize the > internal SSD as a bootable drive. As such, it's just stuck in a reboot > cycle. > > As a last resort, I downloaded the 2.1.5 memstick serial image, burned > that to a USB drive and ran *that* installer, which proceeded > normally. I rebooted, just as I did with the 2.2 installer, and this > time it actually booted as expected, and I was able to successfully > restore my config backup. > > So, I'm back up and running, which is good, but my question is: where > to go from here? There appears to be some sort of an issue with the > 2.2 memstick installer, perhaps not installing the bootloader > correctly, or not setting the "active" flag on the partition? I'm just > throwing out possibilities here - I really have no idea why 2.2 failed > to install correctly. > > I'd appreciate any insight on: > 1) What might have caused the 2.2 installation failures > 2) How I might proceed with a successful upgrade from 2.1.5 to 2.2.0 > > Thank you! > -Erik Anderson _______________________________________________ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
