Upgrade to 2.2, failed to reboot.. Out of file descriptors… then bricked

sense1138 · Jan 25, 2015, 3:14 AM

Ran auto updater.. waited for it to upgrade, waited for wan link to die.. never saw it die, found that strange..

went back to status page, saw copyright updated to 2015 at bottom.. and it was complaining about SQLite missing for Captive Portal status page..

check logs:

lighttpd[60316]: (server.c.1558) server stopped by UID = 0 PID = 86416
php: /reboot.php: The command '/usr/local/bin/beep.sh stop' returned exit code '2', the output was 'Out of file descriptors'
check_reload_status: Syncing firewall
php: /reboot.php: Stopping all packages.
php: /reboot.php: The command '/usr/local/etc/rc.d/ntop.sh stop' returned exit code '2', the output was 'Out of file descriptors'

Firewalls been running fine for weeks without issue, no other logs before that with anything strange in them.. just the daily DynDNS update.

hard rebooted, since I couldn't SSH into it (it was closing connection).. and box never came back.

Have to drag a monitor out there now.. didn't see anyone reporting any Sqllite issues related to captive portal, and the out of file descriptors thing I could find was from 6+ months ago in the bug database, seems unrelated since its "Fixed".
https://redmine.pfsense.org/issues/3749

sense1138 · Jan 25, 2015, 3:41 AM

and the bricking part is that it starts to boot and immediately says "BTX halted". Whether on the upgraded hard drive install, or a fresh USB stick.

kejianshi · Jan 25, 2015, 3:44 AM

Seems like most people having issues didn't remove their packages before update, as recommended.

sense1138 · Jan 25, 2015, 3:49 AM

I must have missed the section on the auto update page that warned to do anything beyond update. :(

WHich package would cause that? Captive portal isnt an installed package, its default.. i had nmap as the only installed package.

kejianshi · Jan 25, 2015, 3:51 AM

I wouldn't think nmap would crash it.

sense1138 · Jan 25, 2015, 4:39 AM

yeah im not sure.. Even a freshly made usb thumb drive couldn't boot, getting the BTX error. so i made one with 2.1.5 on it, booted up fine.. re-installed, now trying to restore original config.. will just stay off 2.2 for a while.

kejianshi · Jan 25, 2015, 4:46 AM

Sorry - Maybe they will 2.2.1 pretty quick. I always worry about hardware falling off the support list with big OS updates.

My hardware is pretty old. I'm waiting to be told one day "sorry - we don't support your ancient box anymore"

Joshy · Jan 25, 2015, 12:21 PM

BTX errors have been linked to using SATA controllers that aren't set to AHCI in the system's BIOS for other FreeBSD installs (and derivatives). What hardware are you using and can you check to see if your BIOS settings are set to AHCI for your controllers?

Also you might want to check for any BIOS updates that exist.

sense1138 · Jan 25, 2015, 10:08 PM

I'll have to take a look when I can shut it down again.. It had been working without issue on 2.1.5 with the current bios settings.. nothing was touched on the motherboard between 2.1.5 and 2.2.

The motherboard is pretty ancient, maybe 5 years old at this point.