SG-8860-1U No Console
-
hy,
made an update via putty and after a reboot, the pfsense does not start and the console usb does not work on win10. checked with a secound sg-8860 > works fine. what can i do?
-
What did you actually update? You don't say in your post...
Jeff
-
@akuma1x i made an update via putty pfsense from 2.3.x to 2.4.x . protocol said that everything is fine and pfsense made an reboot. i think i have screenshots, if you need...
-
@rhorvath said in SG-8860-1U No Console:
@akuma1x i made an update via putty pfsense from 2.3.x to 2.4.x . protocol said that everything is fine and pfsense made an reboot. i think i have screenshots, if you need...
It's my understanding that with the update from 2.3 to 2.4, and even some newer versions, there is a noticeable delay. The FreeBSD software itself had a major version upgrade somewhere in there along the way - basically FreeBSD 11.2 and PHP 7.2. You may have not given the system enough time to complete the upgrade/install.
Did you follow any of the upgrade guide suggestions found here:
https://www.netgate.com/docs/pfsense/install/upgrade-guide.htmlJeff
-
@akuma1x i did.... first step, update 2.2 to 2.3, works fine... reboot, update 2.3 to 2.4. after automaticly reboot i gave 30 minutes time, but the pfsense did not start and usb console does not work. i can not say that the usb worked before, because i made the updates via console.
do you have any ideas for installing directly without a working usb console?
-
You cannot install without serial console.
What does the status LED do when you try to boot it?
-
@derelict: is permanently green
-
Then you should have console output.
https://www.netgate.com/docs/pfsense/solutions/sg-8860-1u/connect-to-console.html
-
@derelict, i do not have. the windows pc does not have an com port online. if i take a secound sg-8860 and i connect this one, i have an com port on windows online. so i think its not a windows or driver or cord problem. any ideas?
-
If you get serial console on one 8860 and not another using the same terminal device and cable, I would open a ticket at https://go.netgate.com/ so warranty status can be determined.
