[Help] F4-210 Sorta responding

[sparky256DSL]

This morning my F4-210 NAS was beeping when I woke up. I was able to log into the Web interface but it wasn't responding for most functions. I managed to power the NAS off, thinking rebooting it might resolve the issues. Now it will power on and all lights light up but it will not respond at all with the drives in the bays. If I remove the drives from the bays, I can get it to a point where it is discoverable by the TNAS PC software, it will respond to ping, allows me to change the IP with the TNAS PC software, and allows me to SSH over port 22 into it with the root/Admin123 creds - although no commands seem to be valid once I'm logged in. It will also pull an IP from a DHCP server if I have one setup on that network. I'm attaching my laptop directly to the NAS but have also tried with it on the normal network.

I read several forum posts and tried everything I could find. I attempted the TFTP and USB methods to reload the image. I tried with exFAT, FAT32, and FAT on different USB sticks and I tried renaming the image to the *wrt*.bin name found in a few of the posts by copy and pasting it to ensure it was exactly the same. I tried with the disks in, disks out, and even after pulling the internal USB device. The process never seems to complete, even after leaving it for hours after each attempt.

I pulled the internal battery and waited 10m like described in another post. Still not working.
I tried to reflash the internal USB with the image using etcher, which seems to have taken but did not resolve the issue.
I was not in the middle of an update and the NAS is/was running TOS 4.2.44 for most of 2025.
There were no space issues and a few days ago the NAS had over 9TB free space.
I've tried http on port 8181 and https on 5443. I've tried both http and https without providing a port (default ports 80/443).

I'm at a loss as to what to try next. Any suggestions?

Thanks!

[MikeZhang]

Based on your description, the NAS hardware appears to be functioning properly, and the issue is likely related to the system. However, without any log information, it is difficult to determine the exact cause.

We recommend trying to reinstall the TOS system, which may resolve the problem. Please note that reinstalling will erase system configurations, including user accounts and permission settings, but it will not affect the data on your hard drives. You can follow the instructions here: viewtopic.php?f=76&t=423

If you encounter any uncertainties during the reinstallation process, you can contact the official online support for assistance.