@stephenw10 said in flashing blue lights after update failed: Yes, if you just got the device and don't know it's history or have a complex config on it already then I would just reflash it with 21.05.2 clean. Open a ticket with us to get the recovery image: https://go.netgate.com/ Steve i just opened the ticket. thanks for the help. cheers

Just as an update for whoever might run into this, we haven't experienced it since the "available version" zabbix items have been disabled and rebooting the gateways afterwards. That has been over 2 months ago. You can check more info in my previous comment. There is still the open question on why do the processes get stuck during this check, but since this isn't that important, I'm going to leave it like this.

@stephenw10 OK, I'll give it a try tonight when I'm done with my work, in case I manage to screw the whole thing up... :) I'll post the results (I have an old Linksys router as a backup...) Thank you again for the help. -N

Nice news, the SG-3100 is a very good home device. And yes, the 22.01 Dev runs very solid and nice on it. Looks like a very nice Release Version is incoming...

@1amt0ny can confirm the WD SN520 NVMe SSD - 256 GB works perfectly fine in my box. Set it up with ZFS as explained in https://forum.netgate.com/topic/168038/proper-steps-for-zfs-pave-re-install-on-6100

@jonathanlee I see subnetting like creating cubicles. As long as you have them your good, however yes if I just had LAN everything that is bad. Thanks for pointing that out. No Any Any rules.

Ah, OK. That's on the 5100 so not some issue specific to the 6100 eMMC. Certainly it's possible it may fail at some point, as any component might. There is no known problem with the 5100 eMMC either though. The write life of the eMMC, which is what usually concerns people, should be easily sufficient for the expected life if the device in normal use. That will be reduced if the device ends up swapping continually or you have installed packages that create a lot a logs. It can also be extended by installing without SWAP and enabling RAM disks but that is not necessary with eMMC. I only do that on the few test devices I have still running from CF or if I ever run anything from USB directly. Both of which have far far more limited write life. However, as you say, if for some reason the eMMC does fail it's possible to install an NVMe drive. Steve

Does it appear in Advanced > SDIO Config ? I wonder if it's trying to detect and setup the connection there still. I don't expect it to appear in that SATA config section, it doesn't on the one I have here either. It's not a SATA device. Though I note you don't appear to have the enable/disable option there at all. Steve

Toggling the repo should work. It may not have refreshed the pkg if you did it too quickly. Any device that is running a development snapshot and pulled the bad repo details at that time will need to be corrected manually. Steve

@teratronic With headless devices (no screen keyboard), I advise you to look and do what is proposed here : How to Run a pfSense Software File System Check This one Upgrading pfSense Software contains also useful information. Both are Netgate video's. These guys know what they talk about : they created the devices. What we all do wrong, just to gain several minutes, and loosing hours afterwards as a result : Before thinking of upgrading : Check free disk space. Do so using console or SSH access. Check if, during the boot cycle, there are no mount errors (see first video). Check that you have a local (USB) copy of the current config.xml. Check that you have a copy of the current version of pfSense ready on a USB. Because you have multiple devices, you can easily test faulty PSU's. Bit be careful : bas PSU's can do harm to the disk : not physical, but on a written 'bit' level. On the next boot, your device refuses to boot ... For any pfSense, a good PSU is import. As important as a good UPS. An UPS is not mandatory, an UPS is only important if your internet connection is important to you.

Yes, connect to the console and see where it's rebooting: https://docs.netgate.com/pfsense/en/latest/solutions/netgate-2100/connect-to-console.html You can probably escape the boot loop. Styeve

You can tell if it's even POSTing correctly by the fan speed. The fans come on a full speed and remain there if Coreboot is not running to set the controller. If will do that if, for example, the RAM size is changed and it needs to retrain. During that time the fans are loud and there is nothing on the console, it can take ~5min. Have you ever connected to the serial console in the past on that XG-7100? You can return it for diagnostics at cost. You should open a ticket with us here: https://go.netgate.com/ Steve

Ok, thanks for the clarification @stephenw10

@hax2021 said in SG-1000 issues pfSense 2.4.0-BETA: Card did not respond to voltage select! You saw https://docs.netgate.com/pfsense/en/latest/solutions/sg-1000/faq.html ? If possible, check the SSD. Contact support.

@clazmania Well, the ultimate fix was to re-image and restore the config...problem solved. Just in case anyone else has a similar issue.

@deuce I sent mine back under warranty and they reflashed the firmware and did some other things to it. They saw exactly what I had been experiencing (mine would continually restart during the reboot, meaning it never even got to the point of running).

Is it exactly 1 hour? The black diamond LED flashing fast indicates it's booting. So the first thing I would be doing is checking the logs to see any any cause for a reboot has been recorded. If nothing is there I would try hooking up the serial console and wait for it to next happen. The review the console log. Something might be shown there that the system is unable to log to the filesystem. If it's already been re-installed though you should open a ticket with us about this. Steve

@bmeeks Thanks Thanks... So update. Suricata and pfBlockNG has been disabled. pfBlockerNG I might re-enable, by all the advise here, unlikely to enable Suricata again. And it seems neither might have been the root cause, that it seems was a damaged modem, Had the local Telco guy check the line, he came back, line's 100% but when he does test from his side against my modem it refuses to sync above 8Mbps... so the last bit of yesterday was to pull a old modem out of a box, configure it as per my network, where I was previously maxing out at 3/5-4Mbps I'm now getting 7-8 Mbps... so hoping he will enable my line for faster this morning and we will then get even better ... I'm so waiting for the 200-300 Mbps fiber in January. Will advise later when this has been done and what I found. So far, thanks for comments. G

@steveits Thanks for the quick reply!