TOS 6.0.770 (X86) is Released for Update

[TMeric]

Fred, thank you for your assistance. The engineer just informed me that the issue has been resolved and the root cause has been identified. The problem occurred because you had used TOS6.0.750 and modified the default https port (5443) before upgrading to TOS6.0.750. This caused remote access to be unavailable after upgrading to versions 750 and 770. The solution is to modify the https port once, which will allow TNAS.online to re-listen to the configuration file.
This issue will only occur if the following conditions are met:

1.The device was upgraded to TOS6.0.750;
2.The default https port (5443) was modified before upgrading to TOS6.0.750;
3.The https port has not been modified since upgrading to TOS6.0.750.

If other users have not used TOS6.0.750 or have not modified the https port, they will not encounter this issue. If any user who has used TOS6.0.750 faces this problem, they can try modifying the https port themselves. You can refer to this link for further guidance: viewtopic.php?t=8715.

[thierrys73]

Bravo et Merci fred tout est ok

[Joesh]

Successful update without any problems

[Arendatr]

Not worked Docker Manager

[seb]

Hello, all seems good on my side after upgrading my F2-423. No issues noticed.

[Claus]

Hallo,
bei eingerichteten Hypercache laufen die Festplatten nach Neustart eine Ewigkeit. Rad5 Prozess !!!
Ohne aktivierten Hypercache ist nach Neustart alles ruhig.

[samius]

After the update from 694 to 770, shortcuts for third-party applications are not displayed on the desktop.

[rfbjr]

Was away, just installed on both F2/F4-223. The issue I had with Hyper Cache is gone. The reboot as part of the update process was fine. Then another reboot of the F4 did not trigger hours of disk activity. I did not have to delete/re-create the Hyper Cache after the update. I'll start checking other aspects later.

[sianderson]

deleting from the recycle bin over a network share doesn't seem to reclaim the disk space (although files disappear from #recycle folder)

however it does seem to reclaim it when using the "empty recycle bin" option from the file manager within TOS

anyone else experiencing this now trying to figure out how to reclaim the space?

[TMvalen]

Hello, regarding the volume capacity display issue, we have confirmed that the system is operating normally. This is caused by the different space release mechanisms between the ext4 and Btrfs file systems. ext4 updates the capacity display immediately after deleting files, while Btrfs uses a delayed reclamation mechanism and requires some time to reflect the space changes. We recommend waiting for a moment after deleting large files before checking the capacity status.