TOS 7.0.0567 Beta (X86) is Released for Update

[Shadeofspirit]

F2-425 plus
Does not boot after update. For serveral hours there is a notification "Loading..., please wait!"
Both ips (connected to independed networks) are accessable via ICMP (ping).
I had already tried differend browsers, cash cleaning, mobile app, etc.

Does anybody knows how to fix such issue?

[EriChan]

Regarding the issue you reported that the app update count badge on the taskbar is not displaying, we failed to reproduce it during internal testing. Please clear your browser cache and try again.

[rfbjr]

Ok sure, question though if an app is updated after you are logged on to the webgui, will that icon get updated in real time?

[Joesh]

Successfully update, no problem appear, open TOS desktop on firefox or chrome no problem

[Felix]

Just noticed the app count showing updates isn't working on the taskbar. I thought I saw it earlier for the update to Terrasync earlier, but just now I opened the apps and saw the update for Cloudsync pending.

It might be because the page still has cached resources after the update or the network update check is not timely. Try logging into TOS Desktop again to see if it works normally.

[Felix]

F2-425 plus
Does not boot after update. For serveral hours there is a notification "Loading..., please wait!"
Both ips (connected to independed networks) are accessable via ICMP (ping).
I had already tried differend browsers, cash cleaning, mobile app, etc.

Does anybody knows how to fix such issue?

I fully understand the problem you are experiencing. Based on your provided instructions, I have outlined detailed troubleshooting and repair steps. Please try the following steps in order:

First, please confirm that your NAS device has SSH access enabled.

If possible: Use a terminal (such as CMD/PowerShell on Windows or Terminal on macOS) to try connecting to your device using the command `ssh username@NAS_IP_address`.

If this doesn't work or is not enabled: You can try connecting the HDMI port on the back of the NAS directly to a monitor or TV using an HDMI cable to check if there is system output information on the screen. This helps determine the device's status.

After successfully logging in through the terminal, please execute the following command to check disk space usage:

Code: Select all

df -h

Pay close attention to the "Usage" or "Available" space in the line `/` (root directory) in the output.

Scenario 1: The `/` directory is full (100% usage)

If the `/` directory usage reaches 100%, core system services may stop responding due to the inability to write logs or temporary files, resulting in your inability to access the NAS. At this point, to ensure data security and avoid accidentally deleting important system files, it is strongly recommended that you do not perform the cleanup operation yourself.

Please contact the official support team directly; they can provide the most professional assistance. Please contact our online support through the official website homepage for assistance with file cleanup.

Scenario 2: / Directory Still Has Free Space

If there is still available space in the root directory, the problem may lie with critical service processes. Please perform the following operations in order:

Restart Critical Services
Try restarting the TOSDaemon and Nginx services. You can usually use the following commands:

Code: Select all

systemctl restart TOSDaemon.service

Code: Select all

systemctl restart nginx.service

Repair Nginx Configuration (if the previous step failed)
If you find that the Nginx service cannot start, it is likely that its configuration file has a problem. You can try overwriting the existing configuration with the default configuration file to repair it. Please execute the following three commands in sequence in the terminal:

Code: Select all

cp /etc.default/nginx/nginx-extend.conf /etc/nginx

Code: Select all

cp /ec.default/nginx/nginx-http.conf /etc/nginx

Code: Select all

cp /etc.default/nginx/nginx.conf /etc/nginx

Reboot the device. After completing the above operations, regardless of whether the service starts successfully, please execute the reboot command to make all changes take effect:

reboot
If you encounter any difficulties at any stage, or need more detailed guidance, you can always go to the official website homepage, where our online support team will provide you with real-time chat assistance.

[Felix]

F2-425+ Updated. No obvious anomalies except the desktop icons/nav bar failed to appear. Normal browser (Firefox) refresh did not make a difference (twice) had to use the desktop F5 option to fix.

This issue is caused by some pages and programs not fully starting after the TOS update. Did you refresh the page by right-clicking the TOS desktop and pressing F5 to restore it? Does this problem persist after use? We're noting this down for now because we haven't been able to reproduce your issue. If this problem recurs, please contact our engineers online through the official website for troubleshooting to determine the cause. Thank you for your understanding and support.

[Felix]

F2-424 Updated: Similar to my earlier viewtopic.php?p=56445#p56445

I just noticed that when a usb device is mounted, and the dashboard is open, the usb eject dialogue is hidden behind the dashboard panel.

F2-221 Updated. No issues - desktop appeared as normal after login.
The older, simpler systems work better

Thank you for your positive feedback. The issue of the USB ejector being obstructed is already in our fix plan and is expected to be fixed in a future version. Please stay tuned for future update announcements.

[Shadeofspirit]

Hi, thanks for the response.
SSH was enabled but it does not work now.
Also, i had tried to connect monitor and keyboard, but, for some reason, i could not login - 'Login incorrect' (i had checked in password manager my password). Is there any kind of special user used for local access?
is there any way, for example, re-install but keep existing data (there are about 2Tb of data)
The overall config is 32GB Ram, 2*8TB HDD(in traid)

[Felix]

Thank you for your feedback!

We have confirmed that the issue exists and have submitted it to our product team. The issue will be addressed in a future version.