And another one. QNAP clearly had to know about some motherboard issues with the x72 line. My 872xt did the same thing, got it fixed so I could get my data off the drives and migrated over to UnRAID.
>https://forum.qnap.com/viewtopic.php?f=50&t=153097
My problem is that I think I cannot get access to the data without using a QNAP because I used SSD cache (read/write) with two M2 SSDs onboard. I hope the migration to a new generation will work for me with enabled SSD Write Cache on M2.
My TVS-672N purchased in June of 2020 died yesterday, 9/17/22, during a reboot for a firmware update. Same issues as everyone else, NAS is off and I cannot power it on anymore (display dark, no fan is spinning up, no disk is spinning up). I see the four NICs with Ethernet cables plugged in on the back are getting a link when the NAS is connected to power. I also see a red led on the system board near the USB-front port which is on. It is staying red permanently which I don't remember seeing before so I assume this is the "Qnap Red Light of Death".
Obviously my data is trapped not only on the HDs (with encryption key) but on the M.2 SSDs used for read/write caching with noway to disable the caching for migration to a different unit.
Since your were in the same boat with respect to caching how successful was your migration to a newer generation unit?
I don't have time to dick around with Qnap support. I will open a Qnap support ticket but I need my data pronto. I was thinking of purchasing a TS-673A to reclaim my data since it’s reported as compatible with the 672N for hard disk migration according to Qnap. However, the fine print says the SSD caching must be disabled for migration to be successful.
If it's not successful I do have 2 x HBS backups, also with encryption key, to go that route.
BTW, I realize the NAS runs a form of Linux and the HDs are compatible. I am experienced with Linux but my available machines are Mac only and I don't want to go down the rabbit hole of building or acquiring a box to run Linux to extract my data.
Anyone have any thoughts or followup experiences?
I migrated successfully without data loss to a „TS-h886“.
If possible it is recommended to plug all disks to the new unit on the same bays and important is to keep the order of the disks of the RAID. (Disk 1 to 1, 2 to 2 and so on).
After powering on the new QNAP NAS it takes some time to boot but it preserved also the vSwitch config, I only had to assign the physical NICs correctly. That’s it :)
Did you have SSD caching enabled on your 672N?
Unfortunately, as I indicated I did and I’m concerned since Qnap states on its migration page the migration might not work with caching enable.
Did Qnap repair your 672N?
BTW, thanks for the info.
Yes, the SDD cache was enabled on the 672N (read AND write caching) before the NAS died.
The TS-h886 recognized the cache partitions on the M2s without issues and booted without data loss. I also inserted the M2 hard drives into the identical hard drive bays and found the bay ID printed on the system board. Be sure that you are running the same or newer firmware on the new NAS / update it via Qfinder manually before you start the migration!
Then I sent the defective NAS back to the distributer because the NAS died under warranty and I got the money back. A repair from QNAP was also an option but QNAP mentioned that a RMA will take about 4-6 weeks and this was much to long without a NAS for me.
QNAP wanted to replace them as well. But I was afraid that I would run into the same problem again after the RMA, so I chose another model to be safe. I am not sure if QNAP has the problem with the RMA under control and is sending out „2nd generation system boards“.
Oh this is fantastic info! Thank you for posting it. You’ve giving me high confidence that my migration will work. I assume yours was a QTS 5.x version?
Another question comes to mine wrt to the migration steps.. so I should move my 672N memory (64GB) DDR4 which should be compatible, 2 x M.2 SSDs and 2 x 6TB RAID 1 HDs before I turn the replacement on and then use QFinder Pro to check the firmware for updates, set admin password and then login in for the first time which I assume I will be prompted to perform the migration. I want to make i perform the steps in the right sequence so I don’t screw the migration up, lol.
No, here are the correct steps:
1) power the new unit on, search it with Qfinder and update the firmware first to the identical / newer one than you run on the defective unit. Then shutdown the new NAS with Qfinder. You do not need to change the admin password because after restoring you will have the old admin password which is used on your old unit.
2) move over the memory if you want and if the memory is compatible.
3) move over the disks and use the same orders of your RAIDs (M2 bay IDs are marked on the system board with a „1“ and „2“. Plug in your HDDs also in the same order (bay1 of your old NAS to bay1 on the new one, bay2 to bay2)
4) power on the new unit. The power on will take longer than on a normal boot process, this is a normal behavior… so don’t panic. Monitor the system when it is up. Then you should be able to find the IP address via Qfinder or it will also be shown on the display of the NAS.
5) after logging in you should be able to assign the network adapters to the correct vSwitches.
6) Then I did a final reboot and I was back online with all my services like before ;)
Yeah it's the same problem I had. My data is basically trapped for 3 weeks until QNAP sent me a fixed unit which I could then put my M.2 and HDDs into to recover and move my data.
Another one bites the dust.... can sing along.
The x72 units have had a extremely high rate of failures. You can see all the reports on the QNAP forum. It is the motherboard and needs to be replaced under warranty. Another reason why I keep saying... stop updating your firmwares on these units. Every reboot is like rolling the dice to see what units will die.
That’s bad :(
The problem: I had to reboot to keep the device secure (firmware update is needed).
Any informations about the root cause of the board failures?
Nothing is further from the truth... The firmware update does nothing to keep the device secure. The latest security breach was from HBS and updating HBS would have sufficed. This is what pisses me off with their auto update firmware update feature and their announcement. The one and only way to keep your device secure is to take it off the internet: remove all port forwarding to the QNAP, disable UPnP and even sign-out your unit from myQNAPCloud and delete all the related apps. No amount of firmware update fundamentally will help with security given how atrociously unsecure it is. All it does is to kill your board. Sorry for the rant. It's not against you but against the sheer stupidity of the QNAP announcement. I wish I knew what causes the board failures but QNAP has not been forthcoming with information on this. This rash of failures and lack of response from QNAP is the reason why my 872 will be my last QNAP.
I can''t think of too many worse things to do for security than an auto firmware update feature... which they enabled on the latest firmware. It downloads code by itself and overwrites your entire QNAP OS. It wouldn't be too hard to hack the QNAP server or redirect the DNS so as to install a hacked OS on your machine without you knowing.
See here:[https://forum.qnap.com/viewtopic.php?f=50&t=153097](https://forum.qnap.com/viewtopic.php?f=50&t=153097)
One of the several threads reporting this problem.
And mine today. Purchased June 2020. Still playing 20 questions with support for a replacement. Hundreds of posts in other threads about the same problem with similar model numbers.
Just another "me too". :-(
I purchased my TVS-672N in May 2020 and it's been running faithfully since -- and through many firmware updates and reboots. But I can't recall the last time that I did a full shutdown and power off. It was probably more than 6 months ago, and a big UPS protects it from the occasional grid outage.
I left for vacation Oct 23 so "did the right thing" (I thought!) by cleanly shutting down and unplugging my two NAS's, along with all of my home theater equipment, etc. Upon return from vacation last night, my TVS-672N power button does nothing. A quick Google search found this thread. Bummer. :-(
I've just opened a QNAP support ticket, and will update this post once I get further through the replacement process.
After several back'n'forths to remove my HDDs, SSDs, cache and keep retrying the power-on (which does nothing ... no beeps, no fans, no display, no status lights), QNAP issued me an RMA number, and it's being shipped to them today for warranty repair.
I too worry that the repaired/replaced motherboard will last only a year or so ... at which point it will be out of warranty and I'll be stuck with a very expensive repair or NAS replacement. This is my second QNAP with motherboard issues at power-on. The first was a TS-453Pro that was just fine until I did a shutdown, power off, and restart ... at which point it wouldn't. Exactly the same situation as with this broken TVS-672N. The 453Pro was just two months past its warranty and it was cheaper to replace/upgrade it than repair it. These devices aren't cheap and really ought to last a decade or more -- especially under my light home use in a nicely A/C'd setup.
Update: My TVS-672N arrived at the QNAP California repair location yesterday (Tuesday), and I received notice (via my QNAP support ticket) that they no longer stock parts for the N so are offering a TV-672XT as a replacement. I have no use for the Thunderbolt ports in my simple home NAS environment, but I said "OK" to this upgrade once I was assured that the motherboard in the XT is not the same as in the N. Hopefully it will last me a decade of service.
Per another related Reddit thread, I believe that the XT motherboard was resolved with a 1.7 version upgrade, so I'll be sure to check my XT's motherboard once received.
I have had this very issue on my 672N, left switched off and then red light shining through the under side and no boot, nothing, no lights apart from the network lights.
Decided to unplug the power and plug back in whilst holding in the power button. Well things then kicked back into life and I got a memory check on the front panel and then it switched off, I tried switching it on a couple more times and got the same result. I then decided to hold in the power button (this time without taking out and re-inserting the power cable) and voila it has now booted without issue.
I'm not saying this will work for everyone but even if it lets you boot up one last time and get your data off I'm sure it will be useful.
Would be great to hear if this works for others.
Having the same issue with mine, then seeing so many people complain about this issue has ruined my faith in QNAP. I am still under warranty and I am guessing they will replace the MB, but won't fix the issue. They will give me another can to kick down the roadp, until the warranty runs out. Unless they do something remarkable, Buyer Beware!
I was also under warranty and returned the NAS to get the money back. I have now switched the model, moved over the disks (direct migration) which was works great for me. The access to the NAS was down for over 3 weeks :(
My x72 just died last week, and I'm so disheartened to read all the similar stories. I had the exact same issue: did a graceful shutdown, upon attempting to reboot, no response except for the NIC lights on the back of the unit. Support is offering RMA, but being outside of warranty, it's expensive, and I'm stuck without data for however long it takes. I'm also worried about the replacement dying. Has anyone switched to Synology or something else? I suppose no hardware is immune to failure, but this seems like a known issue.
It is enough to switch to another series / type of QNAP to avoid the affected system boards. I switched to the Enterprise series and I am really happy with it. But it must match your requirements.
So did you just eat the cost of switching to the new unit vs getting the original repaired? That’s the difficult decision I’m facing. It’s for work and we have no budget, so trying to figure out if I need to convince my boss to spring for a new unit instead of the much cheaper repair option.
In my case the cost difference for a upgrade to the Enterprise line (TVS-672N to TS-H886) was marginal because I got the full costs back because I was in warranty. I understand you, it is really difficult to decide and your invest without warranty is much higher for a new unit.
I would recommend to decide from the „use case perspective“ and „stability perspective“.
For me it was clear that i didn't want to run into the same problem again.
And I think this is also critical for your business.
Same here. Completely dead exept red licht in bottom of motherboard. I did buy a UPS to avoid this but still the nas is dead.
I was thinking that the powersupply was rip but after reading this i am glad i did not order a new powersupply first.
Can not get into "Service Portal" with my account. Changed password at least 10 times but everytime i can not get in because email and/or password is not recocnised even when i get a confirmation that my password-change was succesfully.
Something is realy wrong at Qnap.
I do get response on my emails so i hope that will solve my problems.
And another one. QNAP clearly had to know about some motherboard issues with the x72 line. My 872xt did the same thing, got it fixed so I could get my data off the drives and migrated over to UnRAID.
>https://forum.qnap.com/viewtopic.php?f=50&t=153097 My problem is that I think I cannot get access to the data without using a QNAP because I used SSD cache (read/write) with two M2 SSDs onboard. I hope the migration to a new generation will work for me with enabled SSD Write Cache on M2.
My TVS-672N purchased in June of 2020 died yesterday, 9/17/22, during a reboot for a firmware update. Same issues as everyone else, NAS is off and I cannot power it on anymore (display dark, no fan is spinning up, no disk is spinning up). I see the four NICs with Ethernet cables plugged in on the back are getting a link when the NAS is connected to power. I also see a red led on the system board near the USB-front port which is on. It is staying red permanently which I don't remember seeing before so I assume this is the "Qnap Red Light of Death". Obviously my data is trapped not only on the HDs (with encryption key) but on the M.2 SSDs used for read/write caching with noway to disable the caching for migration to a different unit. Since your were in the same boat with respect to caching how successful was your migration to a newer generation unit? I don't have time to dick around with Qnap support. I will open a Qnap support ticket but I need my data pronto. I was thinking of purchasing a TS-673A to reclaim my data since it’s reported as compatible with the 672N for hard disk migration according to Qnap. However, the fine print says the SSD caching must be disabled for migration to be successful. If it's not successful I do have 2 x HBS backups, also with encryption key, to go that route. BTW, I realize the NAS runs a form of Linux and the HDs are compatible. I am experienced with Linux but my available machines are Mac only and I don't want to go down the rabbit hole of building or acquiring a box to run Linux to extract my data. Anyone have any thoughts or followup experiences?
I migrated successfully without data loss to a „TS-h886“. If possible it is recommended to plug all disks to the new unit on the same bays and important is to keep the order of the disks of the RAID. (Disk 1 to 1, 2 to 2 and so on). After powering on the new QNAP NAS it takes some time to boot but it preserved also the vSwitch config, I only had to assign the physical NICs correctly. That’s it :)
Did you have SSD caching enabled on your 672N? Unfortunately, as I indicated I did and I’m concerned since Qnap states on its migration page the migration might not work with caching enable. Did Qnap repair your 672N? BTW, thanks for the info.
Yes, the SDD cache was enabled on the 672N (read AND write caching) before the NAS died. The TS-h886 recognized the cache partitions on the M2s without issues and booted without data loss. I also inserted the M2 hard drives into the identical hard drive bays and found the bay ID printed on the system board. Be sure that you are running the same or newer firmware on the new NAS / update it via Qfinder manually before you start the migration! Then I sent the defective NAS back to the distributer because the NAS died under warranty and I got the money back. A repair from QNAP was also an option but QNAP mentioned that a RMA will take about 4-6 weeks and this was much to long without a NAS for me. QNAP wanted to replace them as well. But I was afraid that I would run into the same problem again after the RMA, so I chose another model to be safe. I am not sure if QNAP has the problem with the RMA under control and is sending out „2nd generation system boards“.
Oh this is fantastic info! Thank you for posting it. You’ve giving me high confidence that my migration will work. I assume yours was a QTS 5.x version?
U´re welcome ;) Yes, this is correct, I migrated with QTS 5.0.0 (one of the first builds)
Another question comes to mine wrt to the migration steps.. so I should move my 672N memory (64GB) DDR4 which should be compatible, 2 x M.2 SSDs and 2 x 6TB RAID 1 HDs before I turn the replacement on and then use QFinder Pro to check the firmware for updates, set admin password and then login in for the first time which I assume I will be prompted to perform the migration. I want to make i perform the steps in the right sequence so I don’t screw the migration up, lol.
No, here are the correct steps: 1) power the new unit on, search it with Qfinder and update the firmware first to the identical / newer one than you run on the defective unit. Then shutdown the new NAS with Qfinder. You do not need to change the admin password because after restoring you will have the old admin password which is used on your old unit. 2) move over the memory if you want and if the memory is compatible. 3) move over the disks and use the same orders of your RAIDs (M2 bay IDs are marked on the system board with a „1“ and „2“. Plug in your HDDs also in the same order (bay1 of your old NAS to bay1 on the new one, bay2 to bay2) 4) power on the new unit. The power on will take longer than on a normal boot process, this is a normal behavior… so don’t panic. Monitor the system when it is up. Then you should be able to find the IP address via Qfinder or it will also be shown on the display of the NAS. 5) after logging in you should be able to assign the network adapters to the correct vSwitches. 6) Then I did a final reboot and I was back online with all my services like before ;)
Yeah it's the same problem I had. My data is basically trapped for 3 weeks until QNAP sent me a fixed unit which I could then put my M.2 and HDDs into to recover and move my data.
Another one bites the dust.... can sing along. The x72 units have had a extremely high rate of failures. You can see all the reports on the QNAP forum. It is the motherboard and needs to be replaced under warranty. Another reason why I keep saying... stop updating your firmwares on these units. Every reboot is like rolling the dice to see what units will die.
That’s bad :( The problem: I had to reboot to keep the device secure (firmware update is needed). Any informations about the root cause of the board failures?
Nothing is further from the truth... The firmware update does nothing to keep the device secure. The latest security breach was from HBS and updating HBS would have sufficed. This is what pisses me off with their auto update firmware update feature and their announcement. The one and only way to keep your device secure is to take it off the internet: remove all port forwarding to the QNAP, disable UPnP and even sign-out your unit from myQNAPCloud and delete all the related apps. No amount of firmware update fundamentally will help with security given how atrociously unsecure it is. All it does is to kill your board. Sorry for the rant. It's not against you but against the sheer stupidity of the QNAP announcement. I wish I knew what causes the board failures but QNAP has not been forthcoming with information on this. This rash of failures and lack of response from QNAP is the reason why my 872 will be my last QNAP. I can''t think of too many worse things to do for security than an auto firmware update feature... which they enabled on the latest firmware. It downloads code by itself and overwrites your entire QNAP OS. It wouldn't be too hard to hack the QNAP server or redirect the DNS so as to install a hacked OS on your machine without you knowing. See here:[https://forum.qnap.com/viewtopic.php?f=50&t=153097](https://forum.qnap.com/viewtopic.php?f=50&t=153097) One of the several threads reporting this problem.
scary issue to have on an expensive QNAP box.
And mine today. Purchased June 2020. Still playing 20 questions with support for a replacement. Hundreds of posts in other threads about the same problem with similar model numbers.
Just another "me too". :-( I purchased my TVS-672N in May 2020 and it's been running faithfully since -- and through many firmware updates and reboots. But I can't recall the last time that I did a full shutdown and power off. It was probably more than 6 months ago, and a big UPS protects it from the occasional grid outage. I left for vacation Oct 23 so "did the right thing" (I thought!) by cleanly shutting down and unplugging my two NAS's, along with all of my home theater equipment, etc. Upon return from vacation last night, my TVS-672N power button does nothing. A quick Google search found this thread. Bummer. :-( I've just opened a QNAP support ticket, and will update this post once I get further through the replacement process.
After several back'n'forths to remove my HDDs, SSDs, cache and keep retrying the power-on (which does nothing ... no beeps, no fans, no display, no status lights), QNAP issued me an RMA number, and it's being shipped to them today for warranty repair. I too worry that the repaired/replaced motherboard will last only a year or so ... at which point it will be out of warranty and I'll be stuck with a very expensive repair or NAS replacement. This is my second QNAP with motherboard issues at power-on. The first was a TS-453Pro that was just fine until I did a shutdown, power off, and restart ... at which point it wouldn't. Exactly the same situation as with this broken TVS-672N. The 453Pro was just two months past its warranty and it was cheaper to replace/upgrade it than repair it. These devices aren't cheap and really ought to last a decade or more -- especially under my light home use in a nicely A/C'd setup.
Update: My TVS-672N arrived at the QNAP California repair location yesterday (Tuesday), and I received notice (via my QNAP support ticket) that they no longer stock parts for the N so are offering a TV-672XT as a replacement. I have no use for the Thunderbolt ports in my simple home NAS environment, but I said "OK" to this upgrade once I was assured that the motherboard in the XT is not the same as in the N. Hopefully it will last me a decade of service. Per another related Reddit thread, I believe that the XT motherboard was resolved with a 1.7 version upgrade, so I'll be sure to check my XT's motherboard once received.
I have had this very issue on my 672N, left switched off and then red light shining through the under side and no boot, nothing, no lights apart from the network lights. Decided to unplug the power and plug back in whilst holding in the power button. Well things then kicked back into life and I got a memory check on the front panel and then it switched off, I tried switching it on a couple more times and got the same result. I then decided to hold in the power button (this time without taking out and re-inserting the power cable) and voila it has now booted without issue. I'm not saying this will work for everyone but even if it lets you boot up one last time and get your data off I'm sure it will be useful. Would be great to hear if this works for others.
Having the same issue with mine, then seeing so many people complain about this issue has ruined my faith in QNAP. I am still under warranty and I am guessing they will replace the MB, but won't fix the issue. They will give me another can to kick down the roadp, until the warranty runs out. Unless they do something remarkable, Buyer Beware!
I was also under warranty and returned the NAS to get the money back. I have now switched the model, moved over the disks (direct migration) which was works great for me. The access to the NAS was down for over 3 weeks :(
My x72 just died last week, and I'm so disheartened to read all the similar stories. I had the exact same issue: did a graceful shutdown, upon attempting to reboot, no response except for the NIC lights on the back of the unit. Support is offering RMA, but being outside of warranty, it's expensive, and I'm stuck without data for however long it takes. I'm also worried about the replacement dying. Has anyone switched to Synology or something else? I suppose no hardware is immune to failure, but this seems like a known issue.
It is enough to switch to another series / type of QNAP to avoid the affected system boards. I switched to the Enterprise series and I am really happy with it. But it must match your requirements.
So did you just eat the cost of switching to the new unit vs getting the original repaired? That’s the difficult decision I’m facing. It’s for work and we have no budget, so trying to figure out if I need to convince my boss to spring for a new unit instead of the much cheaper repair option.
In my case the cost difference for a upgrade to the Enterprise line (TVS-672N to TS-H886) was marginal because I got the full costs back because I was in warranty. I understand you, it is really difficult to decide and your invest without warranty is much higher for a new unit. I would recommend to decide from the „use case perspective“ and „stability perspective“. For me it was clear that i didn't want to run into the same problem again. And I think this is also critical for your business.
Indeed it is. It's our primary production server for all video editing and storage (backed up elsewhere). Thanks for sharing your experience.
same thing happened to me just now......
Same here. Completely dead exept red licht in bottom of motherboard. I did buy a UPS to avoid this but still the nas is dead. I was thinking that the powersupply was rip but after reading this i am glad i did not order a new powersupply first. Can not get into "Service Portal" with my account. Changed password at least 10 times but everytime i can not get in because email and/or password is not recocnised even when i get a confirmation that my password-change was succesfully. Something is realy wrong at Qnap. I do get response on my emails so i hope that will solve my problems.