Just switched from QTS, no problems so far!
Switched 1 week ago….I cannot express my regret enough. QNAP has offered to look at it, but its so messed up, their remote support fails. I can only send them logs. Re-initialized twice, losing all my AI data, so not super thrilled with losing facial recognition data on 54,000+ photos.
Switched to ACL 2.0. Worst mistake of my life regarding IT. Nothing but headaches and instability. For the love of GOD DO NOT UPGRADE ACL…if you head my advice, you may have no issues at all. Or at least you will be able to revert your way out of this mess. From research I have done, numerous people are having this issue. I can confidently say its either their own apps or own OS. How do I know these things?
I removed all non approved hardware. (even though it worked for over a year flawlessly on 5.2.x). I am now removing approved hardware (such as the video card). I have removed all non qnap Software, and now, we start removing all qnap software we can. Qsync and Qftp are next on the chopping block.
What is the issue? After about 1 hour, file manager stops accessing files, shares go non responsive, and it is so bad the OS can’t even perform a shut down or restart if its been on for more than 40 minutes to 1 hour. and as mentioned, tried to get an SSH key so their techs can look around…their own remote support app is so broken it can’t execute that task correctly.
So in conclusion, I know have an 84 Terabyte paper weight because of this half baked beta. Its bad enough I am opting out of beta as soon as 6.0 stable comes out, and so bad I am looking into how to move to a different brand altogether. Just have to figure out how I am moving a 50TB volume without having to get a crap load of new drives.
QNAP, your ACL 2.0 is pure IT nightmare fuel, and was rolled out long before it was ready.
For Reference I have a TS-1655 with 128GB of RAM, 2 Corel Edge TPU co-processors, and an NVIDIA card installed. Previously had a QNAP card with cache drives installed (pulled those already).
Had probably the same issue. Was in touch with the support team. Got word yesterday that a fix is coming in the following beta release.
My system has been stable for a couple of weeks, but it happened again, after the packages updates from today.
Latest beta not available yet.
For anyone interested, here’s the ssh way to reboot when reboot fails:
echo 1 | sudo tee /proc/sys/kernel/sysrq && echo b | sudo tee /proc/sysrq-trigger
This triggers an instant reboot.