@atteast I just had to do this, the FOXCONN 5010 PVA050C12Q was a direct replacement. $4.92 on Ebay. Supposedly rated for Service life: 50000 hours, but I'll have to get back to you on that.

@w0w Thanks very much for the details/info. I will look through it and see if they say anything about mitigation. It does not matter whose fault it is. It still reflects badly on Netgate, too.

If you think ACB was configured I can check for recent backups if you send me the NDI of the failed 1100 in chat.

Tangentially, Proxmox has a few ways to assist with that. See https://pve.proxmox.com/pve-docs/chapter-sysadmin.html#network_pin_naming_scheme_version and the next few sections in the document.

Nothing I'm aware of. Not yet.

Just as a followup, I have been unable to solve this issue, and it happens with two different 2100’s. So the workaround for now is to use mvneta0 as the uplink to the switch carrying multiple VLANs in a 802.1q trunk (leaves the builtin 5 port switch out of the inter VALN routing). At some point I will try with another managed switch model to see if it’s the specific Switch/SG-2100 combination only, or a general issue.

Mmm, I don't think that is the same issue. Your device is rebooting but fails to find a boot device. That bug refers to a failure mode where it never tries to reboot after shuting down. Though it's clearly similar.

@froussy said in Netgate 7100 with SFP+ module: server room at 17 degree celcius? My room is about 23c and mine was getting in the high 80's. With the fan it is in the mid 60's. So for you, a solid maybe, watch the temps.

Yes. But not that device because it's SATA. The 4200 only supports NVMe drives.

I would reinstall 25.07 clean and restore the config into it if you have any doubt. As long as you have the config file and a recovery image on a memstick you will be able to recover so I would probably try upgrading first. The Device Tree Blob (DTB) is a file that ARM devices use to define the hardware present to the OS. The DTB file is present in the EFI System Partion (ESP). It's loaded into from there memory and passed to the OS by uboot.

@marcosm @stephenw10 Yes, I tried a power brick with a similar power rating as an initial troubleshooting step.

The uboot commands sound somehow familiar to me, but actually I cant remember if I needed to do so. I cant even remember which version of pfSense was the curretn at this time when adding the m.2 SATA, 21.x or 22.x? Regards

@andrew_cb Thanks Andrew, yes cross-posted to reddit as well.

@mmkkoo https://docs.netgate.com/pfsense/en/latest/troubleshooting/disk-lifetime.html

Yup it's a display issue if the system creates a log entry with no host name: https://redmine.pfsense.org/issues/15411 You can just wait for the offending entry to move off the displayed logs.

@stbellcom said in 6100 Failed eMMC replaced with NVme but now no longer reboots: so we went the next drastic step and that is remove the eMMC from the board. Got any pictures of this process, that show the location of the eMMC chip(s) or tips for someone who wants to try it?

I can confirm the Netgate 1100 runs very well with dual WAN, and failover takes but a moment. In my case FTTP (300/50) + LTE (30/10 typical but an upcoming provider swap may improve that). No issues with throughput or performance. Given your intended deployment I see you might end up with double- (or even triple-) NAT. This may cause you issues with throughput because of fragmentation/retries due to the squeezing of the MTU size with adding so many headers. Also, one lesson learned from having a radio-based element in the WAN setup - in my case LTE, but probably applies to Starlink, too* - dial-up the latency numbers on the gateway monitoring. Ping times may grow to over 2000ms under load so we don't want the gateway monitor to think it's down just 'cause it's busy! (the only Starlink I have access to is in a production environment. I don't think my colleagues would be happy if I 'borrowed' it just to test a hunch)

@ddbnj Solved it. I removed an interface still pointing to the SFP. New environments are error free now.

Nice.