u/EslamMohamed94

F2-425 Plus (TOS 7.0.0777) intermittently goes completely unreachable while the hardware stays up — only a forced power-off recovers it. Anyone seen this?

Hoping someone here has run into this. My F2-425 Plus (TOS 7.0.0777) has now, more than once, suddenly become completely unreachable on every network at the same time — no web UI, no TNAS app discovery, no Tailscale, no response to ping. The power and drive LEDs stay solid white the whole time and the unit is clearly still powered and running; it's only the networking/OS side that seems to lock up.

What I checked while it was in the hung state:

- Connected it directly to a laptop with an Ethernet cable, router and switch removed from the path entirely. Cleared the ARP cache and broadcast-pinged the local subnet and the link-local (169.254.x.x) range — no ARP/MAC response.
- Confirmed it showed fully offline in Tailscale.
- Port scans and pings all timed out.
- Plugged a monitor into the HDMI port during the hang — no signal at all.

The only thing that brought it back was a forced power-off (press and hold the power button) followed by a normal boot. After that it comes up completely healthy, no filesystem issues, and runs fine again until the next occurrence. The logs from before the reboot don't survive, so I haven't been able to capture anything from the actual moment it locks up.

Current setup, in case it's relevant:

- F2-425 Plus, TOS 7.0.0777, kernel 6.12.63
- Docker, managed with Portainer
- Jellyfin, two AdGuard Home containers, and Tailscale — all running as containers
- Btrfs / TRAID storage

Questions:

- Has anyone seen TOS 7 go fully unreachable like this while the hardware stays powered and healthy?
- Any reliable way to get logs that survive the reboot on TOS (persistent journald, remote syslog, serial/HDMI console output) so I can capture the next occurrence?
- Anything specific to TOS 7.0.0777 worth knowing about here?

Thanks in advance.

I’ve built a homelab centered on a NAS, and I’m planning to add a Mac as a compute node. Would appreciate your thoughts on the architecture and the Mac choice.

Current NAS setup:
- TerraMaster F2-425 Plus running native TOS
Currently running (Docker via Portainer): AdGuard Home (×2 one for LAN, one bound to Tailscale IP for remote), Tailscale (VPN, no ports exposed), Jellyfin (media, with QuickSync transcoding)
Remote access: Tailscale only
DNS: AdGuard as network DNS + ad-blocking, with a unified nas.home name (split-horizon: LAN IP at home, Tailscale IP away)

Backups (planned): Btrfs snapshots + WORM, external USB drive, offsite immutable copy (Backblaze B2). Following 3-2-1.

Planned Mac purchase (compute node): Deciding between:
- Mac Mini M4 Pro
- Mac Studio M4 Max (base)

Plan: move the heavy apps to the Mac (Jellyfin, Immich, Nextcloud, possibly a media-automation stack, and local AI/Ollama), keeping the NAS as storage + always-on network services (AdGuard/DNS, Tailscale). Mac would read data from the NAS over 10GbE via SMB.

What I’d like your opinion on:
1.Mac Mini (more RAM + storage) vs Studio (stronger chip, less RAM/storage) for a container-heavy + some AI workload?

2.Any concerns with the Mac reading media/photos off the NAS over the network (speed, reliability, SMB mount stability)?

3. Anything you’d change about the overall architecture or the NAS-as-storage / Mac-as-compute split?

My use case: mainly media streaming, photo backup/management (Immich), file storage/backups, and some local AI experimentation. Not doing heavy video editing.
Thanks