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

Does it only do this at warm reboot? If you shutdown then power up with the PWR button does it start normally?

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

@stephenw10 OK.Thanks

@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.

@stephenw10 Yes, both ends are 1000 auto by default and I have tried fixing them to 1000 FDX fixed with no luck. Also - If I limit the client uplink to 100Mbps so the speed cannot really put heavy pressure on the 2100, the problem still arises. So it's most definitively an issue with the stability of the link or some buffer bursting as seen from the builtin 5 port switch side.

@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.

Nice. Weird though.

@stephenw10 Thanks for letting me know there were backend issue, I think it would be helpful if Netgate posted an announcement when there are issues, maybe some details, and an ETA to restore service. It would save a little headache for some of us.