CCTO: https://forum.netgate.com/topic/134042/sg-1000-stuck-in-boot-loop-after-initial-configuration/2
a. Open Putty application and follow the settings in pre-requisite section below.
b. Once you successfully connected follow the steps below:
- At the console press any key to interrupt the boot loader when you see:
Hit [Enter] to boot immediately, or any other key for command prompt.
At the prompt enter: boot -s
That will boot in single user mode to a question asking for a path to the shell, just press return to reach the # prompt. - At the # prompt run the following command:
/sbin/fsck -y /
Run the fsck command at least 6 times; Repeat the command until no errors are reported, even if fsck claims the filesystem has been marked “clean”.
- Reboot by running: /sbin/rebootThe fastert way to get you back up and running is to re-install.
That should do it but if it’s a larger filesystem issue, fastest way to get you back up and running is to re-install. Here’s how to do that https://www.netgate.com/docs/pfsense/solutions/sg-1000/reinstall-pfsense.html
PRE-REQUISITE:
https://docs.netgate.com/pfsense/en/latest/solutions/sg-1000/connect-to-console.html
PuTTY in Windows
Open PuTTY and select Session under Category on the left hand side. Next, set the Connection type to Serial. Then, set Serial line to the console port that was located above, in Locate the Console Port Device, and the Speed to 115200 bits per second.
Click the Open button and the console screen will be displayed.
An example of using PuTTY in Windows.
PuTTY in Linux
Open PuTTY from a terminal by typing sudo putty. Next, set the Connection type to Serial. Then, set Serial line to /dev/ttyUSB0 and the Speed to 115200 bits per second.
Click the Open button and the console screen will be displayed.
An example of using PuTTY in Linux.
GNU screen
In many cases screen may be invoked simply by using the proper command line, where <console-port> is the console port that was located above.
sudo screen <console-port> 115200
If portions of the text are unreadable but appear to be properly formatted, the most likely culprit is a character encoding mismatch in the terminal. Adding the -U parameter to the screen command line arguments forces it to use UTF-8 for character encoding:
sudo screen -U <console-port> 115200
Terminal Settings
The settings to use within the terminal program are:Speed
115200 baud, the speed of the BIOSData bits
8Parity
noneStop bits
1Flow Control
Off or XON/OFF. Hardware flow control (RTS/CTS) must be disabl
