[Help] No Access F6-424Max After TOS 6.0.750 Update – Not Detected on Network

[spleenrun]

That guide also works even if you don't install TOS on M.2 SSD

But honestly, it feels like TerraMaster is continuing this “lottery-style” approach to solutions…
There’s the “If TOS is installed on M.2 SSD” method viewtopic.php?t=7178 , and then there’s Method B viewtopic.php?t=423 — both are mentioned as potential fixes, but how are we supposed to choose which one to trust?

It’s really hard to know what the official and safe procedure is when everything sounds like trial and error.

[crisisacting]

That guide also works even if you don't install TOS on M.2 SSD

… There’s the “If TOS is installed on M.2 SSD” method viewtopic.php?t=7178 , and then there’s Method B viewtopic.php?t=423 — both are mentioned as potential fixes, but how are we supposed to choose which one to trust?

It’s really hard to know what the official and safe procedure is when everything sounds like trial and error.

Although "method B" may be applicable, it's from years before your 424 series TNAS device was launched & for the previous versions of TOS; you should only be using the other guide.

It does seem that you might have a defective unit, so if you can exchange it from the retailer you bought it from, do that. Otherwise, you'll need to go through the warranty process with TerraMaster.

And as you admitted on your own accord that you're not that technical, you are likely over your head here & seem to need something simpler. Maybe look at a WD or Seagate NAS instead; those are as basic as possible.

[spleenrun]

Thank you for the advice regarding which guide to follow — that’s helpful.

Yes, my NAS has become “defective” following an official firmware update from TerraMaster, but until just three days ago, it was working perfectly and I was quite satisfied with it.

If using a TerraMaster NAS requires engineering-level expertise, then clearly I’m not the target audience.
But in that case, maybe TerraMaster should make that clearer in the marketing of their so-called “consumer-friendly” models.

[crisisacting]

…
If using a TerraMaster NAS requires engineering-level expertise, then clearly I’m not the target audience. …

One definitely benefits from knowing their way around an Ubuntu-adjacent Linux build to make certain finer adjustments to current TOS builds & it helps during troubleshooting for much of the current builds, however you don't need to be an engineer to follow the guides and get general changes in place.

You bought what's the highest available TNAS from their current consumer lineup & it should not become unstable nor unusable from an update that was deemed to be part of their stable releases.

This community forum really isn't the right place to seek the proper troubleshooting that their support should be able to provide you if they stand behind their products.

[spleenrun]

You're right — I probably exaggerated when I mentioned needing to be an engineer. That was more out of frustration than anything else.

That said, the damage is done — I'm a TerraMaster customer now, and my priority is simply to find the least painful solution to recover access to my NAS and data.

I’m really glad this community forum exists, because honestly, it’s been more helpful than the official live chat support so far.
For example, during the chat, I was advised to use Method B, including performing a hot swap of drives, which sounds very risky.
As you pointed out — and I truly appreciate it — that method is far too outdated for my current model.

Thanks again for your input and guidance.

[rvescovi]

Hi, I had exactly your situation but I decided to not proceed on reinstall any release. I only resumed the networkd, hostnamed and iptables manually connecting in console via HDMI + keyboard. Now NAS is working but any restart will bring back to the network problem isolation.

These issues seems related to errors 203/EXEC when spawn the services at boot but if you start manually (not as service systemctl) it works.

In the meantime I will wait a further update which probably will fix these situation.

[spleenrun]

Hi, I had exactly your situation but I decided to not proceed on reinstall any release. I only resumed the networkd, hostnamed and iptables manually connecting in console via HDMI + keyboard. Now NAS is working but any restart will bring back to the network problem isolation.

Thank you for sharing your experience — I really appreciate it.

I also connected via HDMI + keyboard with help from TerraMaster support and typed a few commands (though I can’t remember exactly which ones), but unfortunately, it didn’t lead to any result in my case.

If you have some time, I’d be very grateful if you could share a quick tutorial or the steps you followed.
I’d definitely prefer trying your method rather than jumping straight into a full TOS reinstallation using the reset button.

Thanks again!

[rvescovi]

Hi, sure. This is what I did:

A) Connect HDMI and KEYBOARD and restart the NAS and logged in console mode with your main account

B) FIRST STEP: I discovered that .750 assigned an IPV6 but not an IPV4, so I did these commands to resume LAN:

ip addr add (put here your old ipv4 address in this format x.x.x.x)/24 dev eth0
dhclient -r
dhclient

Now with this you have GW and DNS, and I check that the NAS was reachable through ping and UI from another PC. But I discover that INTERFACE TAB in SETTINGS cannot the shown with a POPUP error, so:

C) SECOND STEP: I went back to the console HDMI direct connection (which I still leave up & running) and I started manually the whole service network stack with this command from

/lib/systemd/systemd-networkd

And this bring back the NAS LAN functionalites. So I leave this session open and simply disconnect keyboard and HDMI.

Next I went to the INTERFACE TAB in SETTINGS to verify all the configurations.

Now my NAS is working from LAN and WAN but if you restart it you need to redo at least A) + C).

I'm in this situation now waiting they fix all the issues but at least I can use it.

[MikeZhang]

Please check method B if you need to reinstall TOS
viewtopic.php?f=76&t=423

[spleenrun]

Hi, sure. This is what I did:

Thank you so much for taking the time to share these detailed steps — I really appreciate it!

I’ll definitely try to follow your method. The only issue is that I’m not 100% sure what the last IPv4 address of the NAS was… I tried to assign a few different ones manually via TNAS for PC, but nothing seemed to work.

Also, I have a quick question:
Can I leave the HDMI and keyboard connected and simply switch my monitor input between my Windows PC and the NAS during the whole process — and even after the temporary fix is in place?
Or is it necessary to disconnect the HDMI from the NAS for Windows to fully regain control of the screen?

Thanks again for your help — it’s a relief to finally see a workaround that doesn’t involve reinstalling everything!