TOS 6.0.750 (X86) is Released for Update

[OrionXie]

I'm very sorry for the bad experience you had. If convenient, please move to LiveChat to schedule a remote meeting with our customer service. We will arrange an engineer to confirm this issue with you. Thank you for your understanding.

[OrionXie]

I apologize for the poor experience you've had. Here are some steps you can try to resolve your issue:

1. Restart the device and attempt again.

2. Check the network by verifying the default gateway and DNS server:
- Ensure the Ethernet cable is properly connected to the router or switch. To rule out cable issues, try using a different cable and retry.
- Verify that your router has the DHCP server enabled. Without a functioning DHCP server on your network, an IP address cannot be assigned to the TNAS.
- Confirm that your computer and TNAS are on the same network. If they are connected to different routers or switches, the device may not be found.
- If your computer or network has firewall, security systems, or antivirus software, check if these are blocking the TNAS. If so, remove the TNAS from the block list, or temporarily disable the firewall or antivirus software and re-enable them after the TNAS initialization is complete.

Try different search methods:
If everything checks out above, try alternative methods to locate your device. Here are common approaches:
- Directly enter: http://tnas.local in the browser's address bar (this method only works for uninitialized devices as the name changes post-initialization).
- Install the TNAS PC client on a Windows or macOS computer and use it to search for the device. It is recommended to use version 5.2.186 or higher of the TNAS PC client. During installation, if you're a Windows user, choose 'Trust' when Windows Defender prompts you about trusting the software; if you're a macOS user, allow the client to run in 'System Preferences > Security & Privacy' if prompted that the software is from an untrusted publisher. Versions available: TNAS PC 5.2.186 for Windows / TNAS PC 5.2.xxx for macOS.
- Find the IP through the router by logging into the router's configuration page and obtaining the TNAS's IP address from the list of connected devices.
- Use third-party tool 'Advanced IP Scanner'. Download Advanced IP Scanner for Windows.

3. Verify that TNAS.oline is functioning correctly on the TNAS.

4. If none of these solutions work, consider reinstalling the system. Reinstallation does not format the hard drive data, but configurations need to be set up again. If you have any concerns about data issues, do not proceed and contact us via LiveChat immediately.

[Ziptr]

I apologize for the poor experience you've had. Here are some steps you can try to resolve your issue:

1. Restart the device and attempt again.

2. Check the network by verifying the default gateway and DNS server:
- Ensure the Ethernet cable is properly connected to the router or switch. To rule out cable issues, try using a different cable and retry.
- Verify that your router has the DHCP server enabled. Without a functioning DHCP server on your network, an IP address cannot be assigned to the TNAS.
- Confirm that your computer and TNAS are on the same network. If they are connected to different routers or switches, the device may not be found.
- If your computer or network has firewall, security systems, or antivirus software, check if these are blocking the TNAS. If so, remove the TNAS from the block list, or temporarily disable the firewall or antivirus software and re-enable them after the TNAS initialization is complete.

Try different search methods:
If everything checks out above, try alternative methods to locate your device. Here are common approaches:
- Directly enter: http://tnas.local in the browser's address bar (this method only works for uninitialized devices as the name changes post-initialization).
- Install the TNAS PC client on a Windows or macOS computer and use it to search for the device. It is recommended to use version 5.2.186 or higher of the TNAS PC client. During installation, if you're a Windows user, choose 'Trust' when Windows Defender prompts you about trusting the software; if you're a macOS user, allow the client to run in 'System Preferences > Security & Privacy' if prompted that the software is from an untrusted publisher. Versions available: TNAS PC 5.2.186 for Windows / TNAS PC 5.2.xxx for macOS.
- Find the IP through the router by logging into the router's configuration page and obtaining the TNAS's IP address from the list of connected devices.
- Use third-party tool 'Advanced IP Scanner'. Download Advanced IP Scanner for Windows.

3. Verify that TNAS.oline is functioning correctly on the TNAS.

4. If none of these solutions work, consider reinstalling the system. Reinstallation does not format the hard drive data, but configurations need to be set up again. If you have any concerns about data issues, do not proceed and contact us via LiveChat immediately.

Thank you for your reply. I understand they have to follow a process in their response, but these are obvious things that I had already tried before resorting to the forum. Until now I had no problems, but when installing the latest update. 750, something seems to have gone wrong and hence my initial question. If they do not have more solutions, I will have no other option but to reinstall (I wanted to avoid because I have many configurations done that I did not want to perform again), but I also wanted to make sure that this problem would not be repeated when reinstalling as it is a somewhat cumbersome process to start from 0 again.

[Ziptr]

Finally I have chosen to reinstall the system TOS6 from 0 since I imagine that coming migrated from TOS5 a few updates has caused some incompatibility that has caused this problem. For now everything working properly after reinstall.

[OttO1916]

This update package is applicable to the TOS 6 beta version, but since you have installed 6.0.688 and upgraded to 6.0.694, it is recommended to reinstall 6.0.750.

Hi.
Well, I'm stubborn so I didn't do a fresh install: I upgraded my F2-221-6.0.688and6.0.694-monster to 6.0.750-00004
(if it wouldn't work anyway I had to reinstall - takes a lot longer)

After upgrade and reboot:
- Can access the box remotely.
- Can make a system backup and reboot without crippling the OS.
- Network/InterFaceTab is available again, and NIC's can be modified. (TAB refused to open after upgrade to 6.0.694)
- StoragePools/Volumes/Shares, Users/Groups/ACLs all survived.
- (File)Services and all BackupTools work fine.
- System running smoothly - no crazy disk activity.
Basically that's all i need...

Until now I didn't find anything that doesn't work, will do some more testing next week.
After that I can infect my F5-221 with 6.0.750.

[spleenrun]

Hi,

After updating my TerraMaster F6-424Max to TOS 6.0.750, I’ve lost all access to the NAS. The device powers on normally, and I can hear the hard drives spinning and working continuously, but I can’t reach the system through the web interface, TNAS PC, or network file access.

It’s been over an hour since the update, and nothing seems to respond. I’ve also tried restarting the NAS, but the problem remains.

Everything was functioning perfectly before this update.
Could you please help me resolve this issue?

Thank you in advance for your support.

Best regards,

[rfbjr]

F2-223 updated fine.

F4-223 after the post install, disk activity has started been going 1.5 hrs so far, still going.
Once it quiets down, I'll reboot it again. I think it's the Hyper Cache. If the disk activity starts up again, i'll wait until idle then delete the hyper cache, reboot then re-create the cache. Final test will be another reboot after all that. Since this only seems to happen after a release update, testing is limited. (If another post of mine shows up, sorry I thought I posted this earlier but don't see it)

Yes, the second reboot after applying 750, there was disk activity for over 2hrs. Deleted the Hyper Cache, rebooted, waited 5min or so, no disk activity. Created the Hyper Cache waited 5min or so then rebooted. After system came up quiet disks.
So my thinking is (and I'll try to remember myself) is to delete the Hyper Cache then install the new release and see what happens.

[rvescovi]

Hi, it looks like we are in few posting here that we loose connection to the NAS after updating to .750.

I was able to resume the network after connecting the NAS to HDMI and keyboard, reboot and log into in console mode. During the boot I saw many ERR and retry on network interface. So logged in and discovered NAS eth0 bring an IPV6 but not an IPV4 addr.

So I did:
ip addr add x.x.x.x/24 dev eth0
dhclient -r
dhclient

And now the NAS is again connected to the LAN and WAN but I cannot open the INTERFACE TAB in the MENU, and I'm pretty sure I'll back to the issue if I restart.

Probably there are some changes on network configuration which is not working well in this update at least in my case.

Hoping someone can explain how to fix it.

---------

In the journal I saw many errors on

systemd-networkd.service: Failed to execute /lib/systemd/systemd-networkd: Operation not permitted

[TMeric]

Hello, we recommend that you check the device status at your convenience. In the local network, verify if the NAS is accessible and if the system update was successful. You can also use the TNAS PC application to search and check if the IP address has changed. Is the TNAS.online service enabled?

[TMeric]

Hello, may I ask which version you upgraded from to TOS6.0.750? Are you able to search for your NAS device using the TNAS PC application? It’s possible that the IP address changed after the update. If the issue persists, you can try connecting a monitor via HDMI and send us a photo of the displayed content to help with the analysis. If there are no errors on the current display, you can also try restarting the NAS and recording a video of the output on the monitor with your phone, then send it to our technical support email: [email protected].