TOS 7.0.0791 Official Release (x86) is Released for Update

[RyanYang]

Target Users:
Users currently running TOS 7.0.0746 or later versions.

Note:
If your TOS version is TOS 6, please refer to the TOS 7 update instructions first.
Important: This update is only applicable to TOS 7.0.0746 and newer. Users with older versions must first upgrade to 7.0.0746 before applying this update.

Here, we sincerely thank @nitzer71, @JSCFORCE, @greentower, @Gremlin, @qidi4feet, @Konstantin, @rfbjr, @sianderson, @snapsh0t, @k.wechselberger, @Zymphad, @crisisacting, @EgorA, @apvm, @DCCentR, @joka388, @Nitrokalel, @dgmigdot, @OlRedRooster, @Hendrik, @OttO1916, @ambul and others for your sharing and feedback. Your support helped us quickly identify and fix multiple issues.

Update Notes
Bug Fixes:
1. Fixed an issue where icons might display abnormally after multiple switches when multiple tabs were opened in File Manager.
2. Fixed an issue where MTU configuration became invalid after system reboot when MTU was set and OVS function was enabled.
3. Fixed an issue where system log time was one hour earlier than daylight saving time.
4. Fixed an issue where the Apply button was not properly grayed out when the device name was not modified.
5. Fixed an issue where OpenClaw could not delete users properly via CLI.
6. Fixed an issue where OpenClaw could not create shared folders properly via CLI.
7. Fixed an issue where IP address could not be obtained properly after re-enabling a disabled network interface when directly connected to a computer.
8. Fixed an issue where plugging or unplugging a USB device caused ongoing SMB transfer tasks to be interrupted.
9. Fixed various other known issues.

Important Information:
1.Updating the system theoretically will not affect the data on your hard drives, but for safety, please make sure to back up your data in advance.
2.Before updating, ensure that your primary volume (usually volume1) has at least 3GB of available space. Insufficient storage space may cause the update to fail.
3.After the update, the IP address of your TNAS may change. Please use the TNAS PC desktop client to search for and reconnect to the device.

Update Procedure:
1.Go to TOS > Control Panel > General Settings > System > Update, and click "Check for updates."
2.Follow the prompts to update the system.
3.After the system update is complete, you may need to refresh your browser.
4.The TNAS IP address may change after the update. If you cannot connect to your TNAS using the previous IP address, use the TNAS PC client to search for the new IP address.

Client Downloads:
1. Download TNAS PC 5.2.548 for Windows OS.
- MD5: 72701B52336AF9FD8B97A6BE9D5D5A7C
2. Download TNAS PC 5.2.548 for macOS (x86 architecture).
- MD5: BAA63A179C43F73965EA9C31EEB9D61E
3. Download TNAS PC 5.2.548 for macOS (ARM architecture).
- MD5: BB933DA867058884C4ADFE44EAD24AFC
4. Download TNAS PC 5.2.548 for Linux.
- MD5: 06FE93F9FFE47147854A34F28D57FCC2
5. TNAS mobile for Android: Please search for "TNAS mobile" in the app store to install.
6. TNAS Mobile for iOS: Please search for "TNAS mobile" in the App Store to install.

[crisisacting]

Installing onto test bed units currently; will post if any issues appear in the coming days.

When will a .ins image become available for clean installs & the initboot that's being issued privately for TOS 7, will that become a public build in the coming weeks/months?

Trying to strategize future unit deployment processes & would like a clearer timeline regarding those two aspects.

[snapsh0t]

3. Fixed an issue where system log time was one hour earlier than daylight saving time.

This is now correct in the system log (hurray) but still wrong in Media index last run.

[greentower]

F4-424 Pro(BIOS MADN0101.V05): update ok
F4-425 Plus(BIOS MTWL0101.V05): update ok
F5-422(BIOS MAPL0304V22): update ok
F4-423(BIOS 5.19): update ok

[TMzethar]

3. Fixed an issue where system log time was one hour earlier than daylight saving time.
This is now correct in the system log (hurray) but still wrong in Media index last run.

We will confirm the anomaly you have raised. Any further developments will be communicated to you accordingly.

[User009]

Installing onto test bed units currently; will post if any issues appear in the coming days.

When will a .ins image become available for clean installs & the initboot that's being issued privately for TOS 7, will that become a public build in the coming weeks/months?

Trying to strategize future unit deployment processes & would like a clearer timeline regarding those two aspects.

That's what I'd like to know as well

[TMzethar]

Hi. As with upgrading to TOS 7, there are a few things to keep in mind when installing TOS 7 by flashing a new USB boot drive.
The new USB boot image specifically for TOS 7 can now be downloaded here:
viewtopic.php?t=6433

[Gremlin]

I don't see it.

[TMzethar]

Sorry, the previous link was wrong. It's been corrected now.

[Gremlin]

Updated F2-221, F5-221, F2-424, F2-425Plus. And Tnas-PC*

Now both -424 and -425 show a LAN1 connection as well as alb-Bond on Lan1 and Lan2. While this is not a direct issue it is **** annoying.
The Good News: New Version of Tnas-PC no longer shows the errant LAN1 connection in it's listing. Plus WOL now appears to work on alb-Bond connections.

*Is 'Surrogate Com' a part of Tnas-PC? My windows 11 system always has issues with it while updating Tnas-PC. If I opt to try and close, it fails. If I opt to ignore it, it appears to update - but that does not feel "good". I have taken to deleting Tnas-PC entirely and re-installing it. Makes me feel better about the installation, but seems totally unnecessary. The down-side is that details that should be remembered also are deleted - I don't use Terrasync options, but I am guessing that some of that info may be 'lost' as is 'Access History'.