TOS 6.0.530 Official Version Released

[philh]

Relax, this is easy to fix.
Most likely you had folders named Media on two different volumes before the upgrade, and Media on Volume 3 was set as a shared folder.
The upgrade resets the configuration so that the Media folder on Volume 1 is automatically used as a shared folder. You can rename it and reboot TNAS to make the Media on volume 3 visible.

Great, that solved the issue.
My overall experience is a little bit mixed.
I had to reinstall docker to be able to use it and sometimes after a reboot its not available on the cmdline.

I noticed that apt is available and i was able to install htop.
Is this intended?

[star]

This was very helpful for flashing the initboot USB drive.

But please don't stop after reading the first post. Carry on to the end.

what do you mean specificly ? be precise please? we have many people with corrupted usb and the tmusbflash do not seem to work.

[star]

TerraMaster Engineer managed to help me update to tos 6 on t6-423
apperently even if you remove the m.2 hypercache in the terramaster tos 5.1.145 it does not clean the m.2 and that is what caused the update to get stuck.

as for why the usb boot loader was corrupted we still do not know the cause it seems. but he said they will fix it good luck people

as for the guide on how to fix the initboot usb drive. a new guide is on its way since old way is not reliable

[nperiannan]

Thank you for providing this information. My setup mirrors yours—I also had a hypercache enabled on the M.2 drive, which I deleted when I encountered the update issue. However, I’m now experiencing two problems:

1. After removing the hypercache, it hasn’t fully cleared.
2. This partial removal is causing the boot loader to crash.

It would be helpful if the upcoming TOS 6.0 build includes fixes for both of these issues.

[Gremlin]

I would think that, in 5.1.145, after removing the hypercache you could secure erase the nvme/ssd used for caching. That would give you a clean drive to work with. Or just remove the drive after deleting the cache and before updating. (Just guessing). Of course in Tos 6 you would also have the option to wipe the drive.

[nperiannan]

I reset the NAS to its factory defaults and tried the process again, as expected this process prompted me to wipe the M.2 drive before installing the TOS 5.1.145. Immediately after that(You guys pointed where the problem is, so I did not create hypercache), I upgraded to version 6.0.530, and it went through without any issues. I now feel that the TOS is more mature than I initially thought—it's faster, provides more information during RAID and backup configurations, and overall feels more polished. I was also able to register my product with TerraMaster, and everything looks fresh compared to version 5.1.145.

The only thing I noticed is that full-screen mode isn't available (or maybe it's been moved elsewhere). Everything else seems to be in good shape, but I’ll need more time to explore. Overall, I highly recommend upgrading to TOS 6.0 if you can—it’s definitely an improvement over the older version and eliminates the need for other NAS OS options like OpenMediaVault or DSM (forgive me, Synology users—I’ve never used it, but I think TOS 6.0 covers all the essentials). Thanks to everyone who offered advice, and kudos to Team TerraMaster for their professionalism!!!!

[Tricky]

I'm confused is this supposed to be an update for those with an F5-221 who are running the TOS 6.0.229 or is this something different I am seeing people saying they have updated their F5-221, but it still says the updates for 6.0.229 are still to come which TM said well over a month ago.

[Gremlin]

I'm confused is this supposed to be an update for those with an F5-221 who are running the TOS 6.0.229 or is this something different I am seeing people saying they have updated their F5-221, but it still says the updates for 6.0.229 are still to come which TM said well over a month ago.

No, it isn't supposed to be; but some people like to live dangerously {or not bother reading the instructions}.
It has been said that some (older) 221 models will not be able to run TOS6 > .229, so the rest of us wait to see if TM can fix this. I have live data on my .221 model, so I content myself by testing on a later model to make sure things I want to work actually do (and what changes have been made).

[nperiannan]

I tried to configure TOS 6.0 on my F2-423 and encountered the following issues: (Concerns #1 and #4 are impacting functionality, while the remaining items are merely observations and can be tolerated.)

1. The Cloud Sync feature for Dropbox fails to load the login page, preventing me from setting it up.
2. Some sections, such as UPS power settings and Media Server App, still display Chinese fonts even though I've selected English as the language.
3. The Hyper Cache now supports only two modes, whereas it previously offered four.
4. The SSDP broadcast interval for DLNA/UPnP, along with Media Server settings, is no longer available.
5. Unable to log in as the admin user, despite the account existing. The system consistently reports an incorrect password.

[Gremlin]

All sound like symptoms of a failed update. Not anything to do with TOS6 in itself.