TOS 5.1.34 (X86) is Released for Update

[TMRyan]

WARNING!
Since the new version of TOS 5.1 system requires more storage space, if your initial system was TOS 4.x and system partition is 2GB, please do not update to this version.
To check the free space of your system partition,
Go to "TOS > Control panel > System Info > Overview", and check free space from the item of "/" .

Release Notes

Applicable models: F2-220, F2-420, F4-220, F4-420, F5-420, F2-221, F2-421, F2-422, F4-221, F4-421, F4-422, F4-223，F5-221, F5-225, F5-421, F5-422, F8-421, F8-422, F2-223, F4-223, F2-423, F4-423, T6-423, T9-423, T12-423，T9-450;


This update includes the following bug fixes and optimization for the previous version:

Bugs fixed

• Fixed the bug that hard disks in some models of TNAS fail to hibernate;

• Fixed the bug that the application center may not be able to obtain the latest application information;

• Fixed the bug that the Multimedia Server was interrupted and exited unexpectedly;

• Fixed the bug that some applications that relie on TOSdeamon do not properly start after the system reboot;

• Modified the mount parameters of btrfs file system to reduce file system corruption risks caused by abnormal shutdown or power failure;

• Modified btrfs quota configuration to reduce system resource usage;

Important Notes

• This update is only for TOS 5.1.33 or later versions. If your TOS version does not meet the requirements, please update to TOS 5 by reinstalling TOS.

• The kernel of TOS 5.1 has been updated to 5.15. Since the Linux kernel has removed the Intel Celeron J1800/J1900 GPU drivers from 5.15, the models of this platform no longer support GPU hardware video acceleration. If you are a user of this series of models and need to use GPU hardware video acceleration, do not update TOS 5.1! Models involved: F2-220/F2-420/F4-220/F4-420/F5-420

• Under normal circumstances, the system update will not affect the data in your hard drives, but for your data safety, it is strongly recommended that you back up your data before the update!

How to update your TOS?

Manual update:
1. Download the update package: TOS 5.1.34 (md5：5068bafd87e414dc94a923697f74619f)
2. Go to TOS > Control Panel > General Settings > system;
3. Under the "Manual update", upload the update package;
4. Click "Apply";
5. After the system update is complete, you need to refresh your web browser;
6. Your TNAS's IP address may change after the system update, if you are not able to connect to your TNAS with the previous IP, you need to search the new IP again with the TNAC PC client;

TNAS PC:
After updating to TOS 5.1.34, you need to update your current TNAS PC to 5.0.33 or a later version, or you may not able to search your TNAS device.
1. TNAS PC 5.0.33 for Windows OS
2. TNAS PC 5.0.33 for macOS

It is recommended that you uninstall the previous version before installing this version of TNAS PC.

Issue report
If you encounter issues during use, please report to the corresponding TerraMaster official forum, or email your issue description and screenshots to pm(at)terra-master.com

[Juan87]

F2-221 with USB D4 - Updated to .34 from .33 with no more incidents, to me, than those known from the previous version:
-It is necessary to unmount and shut down the USB disks prior to the new installation. Unlike the previous level, when turning on again
D4, the discs are mounted immediatily without problems.
-A ghost Usbshare keeps appearing. In my case, usbshare5, which is physically located in VOLUME1 (¿VOLUME1 with 6TB, prior to .24 and VOLUME2, 8TB replacing another 6TB prior just before .24, each volume on its own drive?). This phantom usbshare5 can be used perfectly, but... BETTER NOT, just in case...
My apps work fine.
Thanks for the effort.

[MDvP]

Not working on F4-220. Updating from v5.1.33 counts to 100%, then rebootet with the 5 min delay, but then all HDD lights are red, Nas goes to bootloader and shows "no harddisks installed".
I pulled the hdds, powercycled and tried to install the v5.1.34 ins file. Installation went to 100%, rebootet and also goes to bootloader showing no hdds installed. Now i've newly installed the v5.1.33 same way and it works.

[dhfh522]

Time zone still defaults to GMT on reboot in this release and has to be manually refreshed.

[desallesp]

Hi, Update went normally but when it was done I can't log back into it. I get a white screen. Mounted Drives are currently not accessible.
However when I check my router client list, I do see the TNAS connected and its IP Address. I have tried one manual restart so far.
I have a F5 422

[gaz2k1uk]

updated from 5.1.33, cannot log in. I get to the white screen saying "Loading..., please wait"???

[gaz2k1uk]

Was requested to re-inialitise upon reboot, its downloaded TOS again. Stuck back on 5.1.33 and had to set up settings again. This is becoming a joke.

[desallesp]

{L_BUTTON_AT}gaz2k1uk

How do you reinitialize to 5.1.33? Do you lose data?

[TMroy]

updated from 5.1.33, cannot log in. I get to the white screen saying "Loading..., please wait"???

Does it appear "Loading..., please wait!" or a white screen when accessing the web? We noticed that this happens because the btrfs-transaction and btrfs-cleaner process has been busy cleaning up file system data when the system restarts, taking up a lot of CPU resources and causing you to fail to load the page when you log in. We don't yet know exactly what is causing the process to keep busy. It can last for hours if you want to wait for it to be finished.

May I ask if you have enabled the "file system snapshot", and if you have a lot of snapshots? Have you deleted snapshots or deleted data in large quantities recently?
Is your storage pool newly created in TOS 5, or was it created in 4.2? The additional information you provide will greatly help us find the cause of the problem. Thanks!

[MDvP]

How do you reinitialize to 5.1.33? Do you lose data?

I've used methode 2 from viewtopic.php?f=76&t=423
I do not lose any data, only have to restore the settings. Also apps and docker were there after reinstall. (I've saved settings and made backup before update, but do not need to use the backup)
Also have to rebuild the media index to make dlna work again.

@TMRyan, @TNroy
Can you confirm that this update is also for F4-220 with it's older j1800 processor? Then i'll try again to update.