TOS 7.0.0791 Official Release (x86) is Released for Update

[plexjellyfin]

Model: TerraMaster F6-424 Max
TOS Version: 7.0.0791 (x86)

Immediately after upgrading to TOS 7.0.0791, my NAS became unstable. Before the update, it was operating normally.

The NAS boots successfully and works normally for several minutes, then becomes completely unreachable.

Symptoms:

* TOS web interface stops responding.
* SMB shares become unavailable.
* TNAS Desktop reports the NAS offline.
* The NAS eventually stops responding to network pings.
* Recovery requires a forced power cycle.

Immediately after the update I also received the notification that shared folder permission conversion had started and that shared folders might be inaccessible until the conversion completed. I’m not sure if that process ever finished successfully.

Troubleshooting already performed:

* Multiple reboots and power cycles.
* Switched Ethernet ports and cables.
* Verified DHCP network configuration.
* Tested using both hostname and IP address.
* Tested from multiple browsers.

To troubleshoot, I continuously monitored both network connectivity and the TOS web interface.

The failure sequence is always the same:

1. The NAS boots normally.
2. Network connectivity is normal.
3. The TOS web interface responds normally.
4. After several minutes, the web interface begins failing.
5. Shortly afterward, the web interface becomes unreachable.
6. Finally, the NAS stops responding to network pings and all services become unavailable.

This happens even when the NAS is left completely idle after boot with no user interaction.

Has anyone else experienced this on TOS 7.0.0791 with the F6-424 Max?

Is this a known issue, and are there any recommended diagnostic steps before attempting a TOS recovery or reinstall?

[TMzethar]

F4 SSD im unable to save my SMB custom setting, without this settings my MacBook TimeMachine backup wont run.
These settings are in place for months so the latest update(s) introduced this issue.

Looks like the colon (":") isn't allowed in custom configs at the moment. We'll check it out and see if we can improve this. We will review this behavior and explore potential improvements. Any developments will be communicated to you.
As a short‑term workaround, you may edit /etc/samba/smb-customize.conf directly to achieve the desired Samba configuration.

[TMzethar]

We haven't seen or heard of any other crashes like this with the 7.0.0791 update. Do you remember which TOS version you were on before the update?

Assuming it's not a system update or hardware issue, here are two likely causes based on similar cases:

If you're running lots of services, plus Docker containers and VMs without RAM limits, OOM (Out‑of‑Memory) could kick in and kill critical processes. Try to stop as many of those as you can in the short time the system stays up.

If your volume is Btrfs with quotas enabled, and you did things like snapshot restore, deletion, or heavy writes before the update, Btrfs background tasks might be hogging resources and blocking other services. You'll usually see HDD LEDs flashing constantly — that means Btrfs is cleaning up space and defragmenting. Just let it finish and don't power off.

[storageninja]

F4 SSD im unable to save my SMB custom setting, without this settings my MacBook TimeMachine backup wont run.
These settings are in place for months so the latest update(s) introduced this issue.

Looks like the colon (":") isn't allowed in custom configs at the moment. We'll check it out and see if we can improve this. We will review this behavior and explore potential improvements. Any developments will be communicated to you.
As a short‑term workaround, you may edit /etc/samba/smb-customize.conf directly to achieve the desired Samba configuration.

Thanks for restoring this. I’ll test the TimeMachine apple backup without the custom settings first.

[joka388]

The hard drive sleep mode still isn't working, unless you use Jayjay's workaround.

Code: Select all

systemctl stop smartmontools.service

[zeratyx]

Hi,
I upgraded to TOS7 on my F2-423 NAS, and it indicates that the boot order does not match the factory settings, even though I configured it correctly! What should I do ?

One or more of your drives might still have an old boot partition lying around.

Try rebooting a few times — you might get lucky and boot into the system. If you do, migrate the system to each drive in turn to overwrite those old boot partitions, then move it back to your preferred system drive.

You could also do a fresh TOS 7 reinstall and choose a different system drive — that should overwrite the old boot partitions on the other drives.
（If you see a prompt to “Delete/Format,” do not proceed; select a different drive instead. This may be because the target drive contains an older partition format or is being used as an SSD Hyper Cache.）

If you run into trouble, you can book a remote engineer session here:
https://salesiq.zohopublic.com/signatur ... 97d0be8892

Hello
Thank you for your help. The message disappeared when I restarted after removing the non-system disks. It's therefore possible that I have a problematic partition on one of the disks, as TMzethar indicated. How can I identify and delete this partition?

[sianderson]

both mine updated to 7.0.0791 all looking good so far, no issues spotted

took the time to migrate my VMs from virtual box to the VM's app and verified they now auto start (believe that was an issue with virtual box)

[zeratyx]

Hi,
I upgraded to TOS7 on my F2-423 NAS, and it indicates that the boot order does not match the factory settings, even though I configured it correctly! What should I do ?

One or more of your drives might still have an old boot partition lying around.

Try rebooting a few times — you might get lucky and boot into the system. If you do, migrate the system to each drive in turn to overwrite those old boot partitions, then move it back to your preferred system drive.

You could also do a fresh TOS 7 reinstall and choose a different system drive — that should overwrite the old boot partitions on the other drives.
（If you see a prompt to “Delete/Format,” do not proceed; select a different drive instead. This may be because the target drive contains an older partition format or is being used as an SSD Hyper Cache.）

If you run into trouble, you can book a remote engineer session here:
https://salesiq.zohopublic.com/signatur ... 97d0be8892

Hello
Thank you for your help. The message disappeared when I restarted after removing the non-system disks. It's therefore possible that I have a problematic partition on one of the disks, as TMzethar indicated. How can I identify and delete this partition?

I found it, thank you. However, I have an F2-423 and it's displaying F4-423, how do I correct that ?

[sianderson]

has TOS7 been released OTA to the 424 yet? or is it still a manual update?

[TMzethar]

I found it, thank you. However, I have an F2-423 and it's displaying F4-423, how do I correct that ?

Hi.
I've sent you the F4-423.zip model modification file via forum private message.
Please follow the steps below to modify your device to F4-423:
1. Remove all SATA drives, M.2 SSDs, and USB drives (including the internal USB drive).
2. Prepare an empty USB drive and format it to FAT32.
3. Unzip the F4-423.zip file and copy all the extracted files to the FAT32‑formatted USB drive.
4. Connect an HDMI monitor to observe the program execution progress.
5. Plug the USB drive into the NAS USB port and power on the device. The program will run automatically.
6. Once the program execution is complete, power off the device, reconnect all your SATA drives, M.2 SSDs, and USB drives (including the internal one), and resume normal use.