WatchGuard FireBox gets past post but wont Boot



  • He all, my firebox have been sitting on a shelf for a while ever since i switched over to a pfsense VM. But now I want to switch back to my firebox but it wont boot.

    It gets past the memory test i get the beep then it goes to booting OS and just sits there (please see attached pic). I've tried baud 9600 and 115200 with myu nullcable to see whats going on but i get the same in putty (please see attached pic)




  • Netgate Administrator

    Looks like a bad terminal setting somewhere if that line of characters is increasing.

    Same terminal setup you used previously? Terminal software, cable etc?

    Steve



  • Everything default except for the baud rate.


  • Netgate Administrator

    But the line of characters is increasing?

    Do you see any other output? From the BIOS if you hit TAB?

    If you hold the down button while powering on it will attempt (and fail) to boot into safe mode but should at least give some output.

    Otherwise I'd start to question the terminal setup or cable unless it's proven on something else. The hardware itself could have an issue, those boxes are all relatively ancient with large hour counts on most.

    Steve



  • yes the values are increasing

    i tried hitting tab at boot but i dont get anything

    its a rocker switch

    @stephenw10:

    But the line of characters is increasing?

    Do you see any other output? From the BIOS if you hit TAB?

    If you hold the down button while powering on it will attempt (and fail) to boot into safe mode but should at least give some output.

    Otherwise I'd start to question the terminal setup or cable unless it's proven on something else. The hardware itself could have an issue, those boxes are all relatively ancient with large hour counts on most.

    Steve


  • Netgate Administrator

    Yes the power button is a rocker switch but the LCD has 4 cursor buttons. If you hold the 'down' cursor button while powering it on the BIOS will see that and trigger a different boot sequence.

    An increasing line of hashes like that really does look like a bad console setting somewhere though.

    Steve



  • will try that thanks.