Enabled SPC on TNAS F8 Plus - Now I can't access

[MacHack]

As per the title - I enabled the SPC function and the F8 Plus TNAS rebooted.
I'm now unable to see it on the network or access it. The power button is green - A short press does nothing!?
What should I do?

[TMzethar]

May I ask what version of TOS you are currently using? We will verify what you mentioned.

[TMzethar]

We have observed a similar situation in TOS 6.0.512 and are troubleshooting the issue.
If you need to resume using it, you can contact us via the technical support email or the customer service window on the official website to arrange an engineer to handle it remotely for you.
Or if you don't care about the existing configuration and user information, you can reset TOS. (When the device is powered off, use a pin to continuously press and hold the RESET button on the back of the product. While keeping the RESET button pressed, briefly press the power button to start the device. Wait for approximately 30 seconds until you hear three consecutive "beep beep beep" sounds, then release the pin. Next, use the TNAS PC client software to perform a new search for the TNAS device and follow the client's instructions to restart the TOS system initialization process.)

[MacHack]

Thank you for your response.

I can confirm I am using the latest version of TOS 6 version 6.0.519
I have completed a reinitialisation and reinstall of the OS - the TNAS is up and running again. I’ll wait for future OS upgrade before enabling SPC

[pacorabanna]

I'm experiencing the same issue. After enabling SPC, my NAS is no longer accessible through the web interface, although it's assigned an IP address (confirmed via terminal using `ip a` and the TNAS app).

Terramaster devices have great hardware, but the software feels unfinished and inadequately tested. This is incredibly frustrating.

Anyway, is there a way to disable SPC from the command line?

[pacorabanna]

PS: I'm on the latest version and my model is F6 424 max. Thanks!

[TMlinda]

You can try restarting the device and logging in to the system in TNAS PC. In addition, can you log in to the terminal using SSH?

[JasonKitty]

If you can use SSH to log into the terminal, use terminal SSH to access the NAS.
Then run
sudo systemctl stop spc.service
sudo systemctl disable spc.service I hope this works.

[pacorabanna]

You can try restarting the device and logging in to the system in TNAS PC. In addition, can you log in to the terminal using SSH?

Sorry for my later reply, I've been busy and did not have time to log in to this forum. I've been able to fix the problem in the meantime.
I would like to highlight the primary reason for the issue with my TerraMaster NAS. The main problem arose after I installed two NVMe SSDs and created a new volume on the NAS. Consequently, the device was unable to boot. I managed to reboot by removing the two NVMe SSDs and discovered that one of them was no longer functioning. It seems the NAS may have caused the failure of this NVMe SSD, since it was working fine previously (both brand new drives). I have since initiated an RMA process for the faulty NVME drive, but the question remains as to how this occurred.

To resolve the boot issue, I had to remove all hard drives and reset the configuration. Fortunately, I had a backup of my configuration (*.bin file), which allowed me to restore the main settings. No data was lost on the main Volume (RAID), though data on the NVMe was lost since it was configured as RAID 0. Luckily, I had only installed it a few days prior, so I did not lose significant data.

I believe the TerraMaster team should investigate this matter. The NVMe drives I used were two Western Digital Black SN770, each with a capacity of 1TB. Regarding SPC, I had enabled it before rebooting the device and initially thought it might have caused the configuration issues. However, I am no longer certain this was the case, and I doubt SPC was responsible. I recommend that users of Terramaster NAS systems test settings one at a time and reboot the device after enabling each major setting. This approach helps in identifying any issues that may arise after enabling a particular settings.

Another problem I encountered with my NAS (F6-424 Max) is that when installing new drives, the system renames the volumes after reboot. Let me explain. If a volume is created, it assigns the next available number, which is logically correct. However, if a volume is created and then re-created, after a reboot, the NAS searches for the deleted volume. For instance, if you have an existing Volume 1 (main Volume), create Volume 2, and then delete Volume 2 for any reason, the NAS assigns Volume 3 to the new setup. If applications are installed on that Volume 3 and set as the main volume for applications, these apps will not function after a reboot. This is because the TerraMaster system renames Volume 3 back to Volume 2 after a reboot, causing issues with application availability and in extreme cases the system won't be able to boot, like in my case. This is a significant problem that should be addressed promptly in the next update. I've screenshots of the errors I got, in case the tech teams requires them for further investigation. Thank you for your attention.

[Marvined]

Ensure the TNAS is connected properly: Verify that the Ethernet cable is securely connected to the TNAS and your router/switch. Check the router's DHCP client list to see if the TNAS is receiving an IP address. If it's not visible, try a different Ethernet cable or port on the router.
I hope this helps.