TerraMaster Forum

Network storage F2-212.
I have updated the system from version 5.1.73 to the public test version 6.0.585. In version 6.0.585, there were some problems with completing tasks to turn off F2-212 at a given time. I decided to reset the system to factory settings via the menu.
After restoring the factory settings, the system does not initialize. The network storage is turned on, three beeps sound, and a web page opens, but only with a background image. The TNAS PC application sees the network storage over the network and, when trying to log in, opens the same empty page with a background image in the browser. Connection via SSH and port 9222 is performed without problems. It looks like the script is not running on the webpage.
How can I initialize (install) the system?
Thank you.

We sincerely apologize for the inconvenience caused. Please refer to the following link to reinstall the TOS system.
viewtopic.php?t=423

TMjack wrote: ↑22 Feb 2026, 15:05 We sincerely apologize for the inconvenience caused. Please refer to the following link to reinstall the TOS system.
viewtopic.php?t=423

I've tried different ways, clearing the cache and different browsers. I also tried the direct connection to the computer, without the router. But the result is the same. The page opens in the browser with a blue background pattern without buttons or labels.
Maybe the web page is broken? How can I check it?

Could there be a reason for these errors? (the image below shows errors from the browser)
[url=https://postimg.cc/KKMN4mS1][img]

This issue is typically caused by a corrupted system installer. To fix this, we can log in via SSH and manually flash the rootfs file into the corresponding partition.

Preparation

Terminal Tools: PuTTY or MobaXterm are recommended.
Repair Resources:

• rootfs:

https://download2.terra-master.com/rootfs.img

• 2G Kernel Image:

https://download2.terra-master.com/kernel_2g.img


Step 1: Enter the Boot System

• Power on your TNAS without any hard drives installed.

• Once the network LED is lit, use the TNAS PC desktop client to search for your device and confirm its IP address.

• Log in via an SSH client (Default Port: `22`, User: `root`, Password: `root`).

Step 2: Download the Files

To ensure a successful operation, it is recommended to place the files in the `/tmp` (RAM) directory to avoid write failures caused by insufficient storage space.

Download the rootfs file:

Download the kernel file (Only if necessary):

Step 3: Confirm Partition Information

Before flashing, check the MTD partition table to identify the correct target partitions:

Typically:

• mtd2 corresponds to `firmware` (where the Kernel is stored).

• mtd3 corresponds to `rootfs` (where system files are stored).

Step 4: Perform the Repair

Flash the rootfs:
Flash the kernel (Only if necessary):

Step 5: Reboot the TNAS

Once the flashing is complete, execute the following command to force a reboot:

Thank you very much for your help!
But I must have done something wrong! It's my fault! Something went wrong and the device stopped starting at all. It turns on for two seconds and turns off immediately. Completely disconnecting from the power supply did nothing. I think the bootloader is corrupted. Are there any options to fix this? Thank you in advance for your help!

The method mentioned by EriChan above is related to what you referred to as 'bootloader'.

However, based on your description——“It turns on for two seconds and turns off immediately”, this is likely an issue with power supply or hardware.
Please use the original power adapter if possible. Check if there are any abnormalities such as dimming or flickering of the LED light on the power adapter.
If you have a different power adapter with the same interface and 12V output, you can replace it for testing to see if it's a power supply problem.

If the possibility of a power supply issue has been ruled out, it is very likely a hardware damage or fault.

Well. I think we can try to burn the firmware again. Is there any way to rewrite the firmware to the device? I searched the forums and found no information.

What is mentioned above is the only known method so far.

OK. I will try to send it back for reparing.
Thank you for your support!