SG-2100 Fail After Update
-
I'm not sure if this is the same problem mentioned by a couple of other people or not. My scenario:
About a week ago, I decided to update my SG-2100 with the latest release. I started the update and then got busy with other stuff. After I got home, I tried to VPN into the SG-2100 and failed (I believe it was an invalid password error). Then I remembered that I hadn't rebooted the SG-2100 after the update. I wasn't able to get back to it until today so I tried to log onto the graphical console but I received a "bad user name or password" error. I thought that was odd because I hadn't changed either so I thought I should just reboot the box. Up until that point, I had internet access and, from a user perspective, everything except the VPN server appeared to be working fine, including access to the graphical console even though I was getting an error on the userid/password. After the reboot, I got nothing. The box appears to boot properly (circle has a fast blinking blue light that is then joined by the square with a fast blinking blue light and then the diamond does the same. After 5 seconds or so, the circle light and the square light turn off and the diamond light changes to a slow blinking blue light) but I have no internet access from my workstation, attempts to access the graphical console via a browser go unanswered and the box does not respond to pings. I also added a 192.169.1.x ip address to my workstation just in case the box had some how been reset to its default 192.168.1.1 address but it had the same symptoms as with the "normal" ip address.
I haven't tried to connect to the USB console yet so I'm not sure whether it will respond or not. Any suggestions as to what may have happened and how I get this box running again?
Thanks
-
Yup, you will need to connect to the serial console to see what's actually happening there. You will need to do that to reinstall if you end up having to anyway.
https://docs.netgate.com/pfsense/en/latest/solutions/netgate-2100/connect-to-console.html
Steve
-
Yup. I figure out the problem once I got into the console. When I tried to access the tools menu, I received a fatal error telling me that there was not enough room to create a lock file. Deleted one of the BE files and I was off to the races.
