Netgate 4100 circle shows red LED

JeGr

@stephenw10 said in Netgate 4100 circle shows red LED:

Mmm, that doesn't sound good. Have you opened a support ticket yet? I would do so if not.

That would be the next stop. Wanted to check here first about the LED status as that was an unknown. Now I've learned that one - so next stop seems support ticket.

Thanks a lot!
\jens

CharlieMiller008

@JeGr @stephenw10

What ever happened on this ticket? I, too, have a amber circle that continues to light no matter what I do. Buttons are 'clickable' - removed from power - still flash, then amber circle.

stephenw10

Open a ticket with Netgate TAC:
https://www.netgate.com/tac-support-request

CharlieMiller008

@stephenw10 Thank you sir.

I filed a ticket, and it turns out the unit is considered no longer functional.

The troubleshooting confirmation steps were to check with the console for any output on power up. After we determined no output on the serial connection, the unit was considered dead.

stephenw10

Mmm, unfortunately that may be the case if there's no output at all.

If it's out of warranty I would try opening the case and removing the CMOS battery. And any expansion cards/drives you may have installed. You have nothing to lose by trying it.

Steve

CrKlom

@CharlieMiller008

I have the exact same problem! So weird..
Netgate 4100 Orange/Red light - No Console

To summarize it, I had a local circuit breaker failure which happens to host my Netgate 4100, and my device is stuck in standby mode (orange/redlight) and I have no console output. Followed instructions, 10sec power button push, removing the CMOS battery etc...
I talked to someone who is more knowledgeable on hardware/software programming and he looked at my board and you can see the green mini LED's on the board working and he said that you should at least have console output but the device is stuck in standby mode.
He think the device might be bricked due to a software (bios) issue on the last upgrade.

Did you had any luck on getting it working again, or reimbursement from netgate?

CharlieMiller008

@CrKlom pray you are within the terms your hardware warranty :)

arri

Add me to the list. Had a 4100 go down due to wear on the eMMC which may have been exacerbated by a well meaning but ill informed tech pulling the power to the board to reset it.
It booted up and showed the console with the USB installer successfully once so I figured it was worth getting some new storage to salvage these 4100's I've got. After locating a B Keyed M.2 NVMe and physcially installing on the board there was no longer a console connection at all during power up. Just the orange circle of death and no activity on the USB.

Then I pulled the NVMe out and tried again to no avail.

I also tried pulling the CMOS battery for a few minutes.

Pressing and holding the power button appears to attempt to do something after about ten seconds (it was non responsive with a five second push) according to the eight diagnostic led's changing on the circuit board but still no output on the console, no activity on the USB key and the orange circle of death remains. In this post power button pushed for 12 second state the lit led's on the board are:
FLASH (immediately above RESET)
V3P3A

In its steady state after applying power or after pressing the power button after the above press and hold the following led's on the board are lit:
PWRGD
PWRGD
PWRGD
V3P3A

arri

Ultimately the only recourse for this (and subsequently additional) 4100s that died on me was to remove the emmc by desoldering it. Then I was able to boot the installer properly and install to NVMe. While not for the inexperienced, desoldering the eMMC really wasn't to difficult given the designers left plenty of room around it to work.

cboling

@arri THANK YOU! I lack the reputation needed to upvote your comment, but THANK YOU! I never even thought about ripping that chip out.

Here's my story:

Dec 25: router died. (Merry Christmas! At least it didn't harm too many other people.) Serial console worked; diagnosed a bad eMMC w/ help from TAC. Found an M.2 drive that worked, and reinstalled the OS then restored settings from backup.

March 30: Died again! This time the console's dead. Tried "everything".
Found your post mentioning desoldering it. Found a chip labeled "Kingston" and decided that must be it (but looked up part# to confirm). Attacked the face of the chip with a flamethrower, er, butane utility lighter, while mercilessly gouging and stabbing it with a sharp little screwdriver. Continued punishment until it flew screaming off the PCB, carrying PCB traces with it. Regretted not using more flame and less physical force. Scraped off traces still hanging on, ensured that nothing left on the board was touching anything that it shouldn't.

Powered it up with fire extinguisher nearby (and video camera running in case it went up in a glorious ball of flame and made my son scream as it tried to do to him what I did to it) and...it booted! Replaced heat sink grease (even dabbed some on the RAM chips that were naked before), wadded up a ball of masking tape and set it on top of the battery to replace the retainer clip that we broke earlier, and screwed everything back together.

Back in operation! No data loss this time -- best outcome possible. Lesson learned: A bad eMMC that was "harmless" before can become "harmful" 3 months later!