Update: after several emails with the support, I finally got the confirmation, that the motherboard in my unit is V1.7 (fixed version).
Glad yours is fixed!
Mine is at the repair shop about now!
Jon,
I have a TS-451, TS-563, and a TS-873A. KC0AKZ had a TS-451 with the bad CPU problem, and now has a TS-473A.
I have observed over the years with QNAP that 1) They are VERY slow to adopt any new features, security or otherwise. 2) They customize everything just enough to force lockin. 3) QuTS Hero has the worst testing/quality control I’ve ever seen on a NAS appliance.
It is time to try TrueNAS - what I’ve been doing over the holiday, getting that to run on my QNAP hardware.
KI0OB
I have no issues with anything QNAP. That’s completely different than a hardware issue that has been well known for many years.
I find QuTS Hero to be quite good. I’m not messing with the beta because I don’t want to deal with that on my main NAS units. But the beta problems people find are due to the fact that it’s in, well, Beta. I’d expect there to be issues.
Once you do some testing - try loading the disks into a different NAS and some of the other more complex recovery scenarios, you quickly find that QNAP is very ‘impolite’ and is a bit ‘flaky’ is the only way I can describe it. Mind you it all seemed to work okay back on QTS, but QuTS hero seems to be kindof a mess. For example, if you have multiple pools and the ‘system pool’ dies, you are screwed - can’t get to the others anymore either.
My favorite, is when I reinitialized a nas recently to find out that it didn’t install the ‘storage manager’ app because - there isn’t a place to install to until you create a pool, but I couldn’t create a pool without storage manager.
This topic was about the x72 chipset problem, so don’t mix this up with the C2000 LPC signal issue that maaany manufacturers plagued (like Cisco, Syno,etc)
I’ve done at least one or two recoveries of my NAS running Hero. I am not certain what you mean by it being impolite. Yes, you can’t do bare metal restores, but I had no issue restoring data.
I think some of the stuff about the storage manager app was due to using Hero 5.3. I’ve stayed away from that as I tried it bt didn’t like the new look and it really added nothing to anything other than high availability. It was not a fully baked solution. I think many of these issues will be taken care of in version 6, but I am staying away form that until it goes into production and maybe even then I’ll wait a while.
And @dolbyman is correct. The x72 series had a completely different issue. You can’t fix it with a resistor. There’s an IC on the board that goes bad.
Oh and regardless if you are running TrueNAS, QTS, QuTS Hero or whatever, hardware issues will still be the same.
Finally, I see your user name is “qnapused2bgud.” If you are going to come on this forum and spread FUD about QNAP, please leave. Seriously.
Same situation here with my TVS-872XT.
For those unaware, the TVS-672XT and TVS-872XT share the same motherboard architecture, and they suffer from the exact same failure pattern: sudden shutdown and the infamous “Red LED” on the motherboard (VRM/MOSFET failure).
My unit died recently. QNAP Support refused to cover it as a hidden defect and quoted me 818€ for a motherboard replacement.
I have decided to challenge this. I have documented my full case (including the fact that support is ignoring Certified Legal Mail) on Reddit to warn other users.
You can read the full timeline here: https://www.reddit.com/r/qnap/comments/1qb2xbg/warning_qnap_tvs872xt_red_led_of_death_support/
It is disheartening to see so many units failing the exact same way without a recall program.
Keep us informed. We paid $900 for a TVS-472XT motherboard replacement that was 4 months out of warranty.
I guess I didn’t learn my lesson… Nick repaired my TVS-472XT in 2024 after a software update caused the discussed ‘no activity except a red led’ issue as the unit was just out of warranty. Well it happened again last week doing a software update, a year past Nicks 1 year warranty 
I did many software updates in the years following the first failure so I was thinking that problem was behind me. I really don’t want to repair the unit again if it’s destined for another failure. My plan is to place my Iron horse drives in standard external enclosure and build up a linux pc to perform the few NAS functions I use.
My question is: how do I now read the 4 perfectly good 12T drives without using a TVS? I’d like to retrieve my data. Raid 5, ZFS format
Any Help would be most welcomed
Thank you! - Tom
@tomL you’re probably way past this, but for completeness you should be able to cleanly recoverable on any Linux box with OpenZFS, no QNAP dependency.
Has anyone seen any of the 872XT units fail with the updated v1.7 mobo? QNAP shipped me a brand new replacement unit in 2021 with v1.7 mobo, serial Q207I14xxx. I’m planning to finally move this unit from QTS to QuTS, and reading these post makes me nervous to major update it.
And is QuTS the right move on this old dog with the i5-8400T and 64GB RAM? I’ve just never moved it to QuTS given that’s when it seems to die on us!
-Qmann
I’m pretty sure the revised board fixed the issue. I think the original board used the Intel Apollo Lake chipset. It was one of the supporting chips that has the issue. The redesigned board (no audio output) does not use the same chipset.
Also Hero runs fine on the i5. Just a better experience on the i7. I think my 672XT had an i3 in it originally and Hero ran just fine. Slightly faster than the V1500B on my TS-873A.
V 1.7 is a pretty old one still, there was newer ones later on. Can’t check anymore due to the lack of old forum acccess.
But I think the production code needs to my higher than Q21 to be safe.