@cmb:
That sounds like this:
https://doc.pfsense.org/index.php/Upgrade_Guide#Console_Problem_Workaround
though that shouldn't have just started out of nowhere, it would have happened on the first reboot post-upgrade to 2.2.2 for systems that were affected.
The workaround there will get it to boot quickly. Then if you upgrade to 2.2.3, that won't happen again.
Sorry for the late reply.
Dude, you're a life saver.
Thank you so much.
I did exactly that :
To work around the issue, restart the system and activate option 3 at the pfSense logo boot menu for the Loader Prompt. At the loader prompt, enter:
unset boot_serial
boot
Then I updated to 2.2.3
Then rebooted normally.
And everything's good!
Thanks again!
@muswellhillbilly:
PS: I had something similar happen to me a while back. If all else fails, you ought to be able to boot into single-user mode (shows in your YouTube clip), navigate to the /conf folder and pick up the config file by copying it to a USB stick.
I did try the single-user mode and the same problem was occurring before the fix above.
@muswellhillbilly:
@BlazeStar:
And of course I don't have a recent backup of my config :'(
When you do get your system back up, you can do the following (this is one of many ways to do pretty much the same thing):
1. Log onto your pfSense system on the command line. Write a shell script thusly and save it in your /root folder. Call it something like 'backup.sh':
#!/bin/sh
cd /conf
cat <<end |="" ftp="" 'ftp:="" username:password@myftp.site.com="" '<br="">put ./config.xml
END
Obviously, substitute 'username', 'password' and 'myftp.site.com' for your corresponding site and credentials.
2. Create a cron job: 00 5 * * 1-5 /root/backup.sh. This will upload your system's config file at 5am every working day.</end>
Thank you that's very wise, i'll be creating that cron job for sure!
