Updated a TS-453bT3 (primarily used as an own cloud) from 5.2.4.3079 (2025.03.21) to 5.2.5.3145 (2025.05.26) several days ago.
Haven’t observed any issues with the update, FWIW.
~~ S
Firmware came with new TVS-h874. Multiple problems migrating because I didn’t know the old firmware. Hard to determine when the old until dies. Anyway…fix most everything except the firmware sync error because of different versions. Tried downgrading and upgrading without success. The fan on the unit for the CPU runs at MAX speed. I’m assuming this is a firmware issue, Manually setting System to 60% and CPU to 45% keeps them happy. CPU stay around 40C and drives in the 25-30C range. It’s also possible running with the cover off overheats the CPU as it’s not getting the proper airflow. Even at MAX, it was hovering around 75C.
Any suggestion to get rid of “The drive has come from a device with firmware version…” would be appreciated. Everything works correctly and I have backups, but would rather not have to factory reset and delete and restore everything just to fix it.
Thanks!
i have a ts-853a which is on the approved list. but not able to download. only previous version available. any ideas why?
The reason you didn’t receive an auto-update notification might be due to our canary deployment mechanism. You can find more details about it here:
Why does my NAS not update to the newest firmware version via automatic updates or the Check For Updates button? | QNAP
In the meantime, you can always download the latest firmware version directly from our Download Center.
Hi Steve, this FAQ appears to be very out-of date with respect to the firmware versions that use canary deployment. Can this be updated please?
@SteveKo also, that document says:
If your QNAP NAS device was not selected to participate in a canary release, you can wait until the canary release becomes a wide public release at which point your system will be able to update using the Check For Updates feature or automatic updates.
Is there a way for admins to opt-out of canary releases? These might be interpreted to be more advanced than beta releases, but clearly are not trusted enough by QNAP for production use. 
I suggest the NAS admin should be able to choose their level of acceptable risk based on their NAS usage.
2 Likes
i do have one thing to add and its this: why put it in the supported list if i cant install it. i manage about 30 plus different qnaps and this just makes it a pain in the you know what! and i used to use that list to upgrade the firmware on all qnap nases at the same time to save time. thats all i got to say about it and am moving on and changing subjects.
Thanks for the reminder. I’ll inform the internal team to adjust the FAQ content.
1 Like
Hi @OneCD @David5
Just to clarify, our canary releases only affect whether your NAS automatically receives update notifications.
Even if your device isn’t part of a canary release, you can still get the latest firmware information by going to Control Panel > System > Firmware Update > Check For Updates.
1 Like
Thank you Steve.
If I may ask it differently: how can a NAS admin avoid being one of the canaries who is “randomly selected to participate” in the release? If I’m running a production NAS, I don’t want to get a notification the newest firmware is now available for my NAS, only to find after installing it that it contains bugs that prevent my NAS working as it should, and will require me to advise QNAP of these bugs. I’d rather not be randomly chosen as an early firmware adopter on a production system.
On my various development NAS, there’s no issue.
Maybe notification of canary releases should be only to those who were willing to accept beta releases? Those admins are at-least a little more tolerant of issues, and understand the process to report bugs.
Thanks for raising this important point. I want to clarify that canary releases are not beta versions. Instead, they’re a phased rollout of our official firmware versions.
If you prefer not to receive automatic update notifications on your production NAS, you can simply disable the auto-update notifications. This will allow you to manually check for and install updates when you’re ready.
Thanks for your understanding!
Thank you Steve, that does help. 
Same issue here as well, after the update to 5.2.5.3145 it sluggish in performance and when logging into the QNAP TS-853A webgui the CPU load is sitting at 98% for a while and after a while it calms down to 45-65% CPU load. In the past the CPU load would be around 2-10% when jumping around in the webgui and if one didn’t do anything it would sitt at 1-2% and when having clients active accessing files via SMB it would be around 5-10%. So something is significantly wrong with this release.
Could you please tell us your NAS model?
Using TS-853A.
5.2.5.3145 - Creating a shared folder “Enter path manually” no longer takes an edit in that field - it will error saying the path doesn’t exist. It will allow selecting a pre-existing folder only. It won’t actually CREATE a new folder if you want to specify the path.
If after creation, I go into the Shared Folder’s “Edit Properties”, I can edit said field there as expected, and it will create the desired missing folder from that operation.
example folder structure and I want to add a Lizards share under Animals:
/Public
/Homes
/Animals
> Birds
> Cats
> Dogs
/Supplies
/Equipment
Create screen “Enter path manually” previously allowed me to navigate to select Animals, and then cursor into the field and append /Lizards or if I knew the path just type it in /Animals/Lizards - it now turns pink and errors that the path doesn’t exist.
If I just submit it as /Animals then it ends up under [/share] as:
Lizards → CACHDEV1_DATA/Animals/
I need it to be as follows and must return in to ‘Edit Properties’ to get it to create the folder
Lizards → CACHDEV1_DATA/Animals/Lizards/
I don’t know exactly when this behaviour changed; been several months since I last created a folder with a manual path. Field takes a desired not yet existing path on older unit running 4.3.3.x
after I updated the firmware it rebooted to an “non active” volume tried going back to previous firmware and its still gone… I scanned it with md_checker and this is what it found … if anyone can advise me what command line i need to put to assemble it with MDADM i would appreciate it because it would b my 1st time doing it …tks
RAID metadata found!
UUID: 51b4d1c5:6b9dc918:c81fd799:a9d57195
Level: raid5
Devices: 10
Name: md1
Chunk Size: 512K
md Version: 1.0
Creation Time: May 31 07:47:04 2025
Status: OFFLINE
Enclosure | Port | Block Dev Name | # | Status | Last Update Time | Events | Array State
NAS_HOST 1 /dev/sdl3 0 Active Jul 18 19:14:41 2025 132717 AAAAAAAAAA
NAS_HOST 2 /dev/sdk3 1 Active Jul 18 19:14:41 2025 132717 AAAAAAAAAA
NAS_HOST 3 /dev/sdh3 2 Active Jul 18 19:41:56 2025 133962 .AAAAAAAAA
NAS_HOST 4 /dev/sdi3 3 Active Jul 18 19:41:56 2025 133962 .AAAAAAAAA
NAS_HOST 5 /dev/sdg3 4 Active Jul 18 19:41:56 2025 133962 .AAAAAAAAA
NAS_HOST 6 /dev/sdj3 5 Active Jul 18 19:41:56 2025 133962 .AAAAAAAAA
NAS_HOST 7 /dev/sda3 6 Active Jul 18 19:41:56 2025 133962 .AAAAAAAAA
NAS_HOST 8 /dev/sdb3 7 Active Jul 18 19:41:56 2025 133962 .AAAAAAAAA
NAS_HOST 9 /dev/sdf3 8 Active Jul 18 19:41:56 2025 133962 .AAAAAAAAA
NAS_HOST 10 /dev/sde3 9 Active Jul 18 19:41:56 2025 133962 .AAAAAAAAA
[~] # mdadm
Usage: mdadm --help
for help
You should probably create a support ticket rather than messing around.