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).
1 Like
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.
I’m in the same boat.
I regret buying the QNAP. I’ve had it less than a year and am thinking I would’ve got better value from a boat anchor.
Again, you are complaining about issues and calling it a waste when you are using beta software. Beta means you will likely have issues. It’s why I haven’t touched hero 6 yet.
Did you bother to read, and understand how I got here?
I was asked by support to install the patch to fix the problem. The problem is still there.
Well, since all you said in this post is that you bought a boat anchor - no.
All you are doing is trashing the product. That’s not beta testing.
OK Grasshopper?
Why don’t you take in to consideration your other reply to me in a different thread. I’ve run out of dealing with idiot tokens today, I’ll come back to reply tomorrow. But the short of it is, I had a non-beta non-working QNAP TS-464 from the start. After pulling the unit apart and running memory soak tests (hardware all ok), I was asked to upgrade. Then, the ACL 2.0 nightmare began. Then, support asked me to install the beta patch as it fixes my problem.
I’ll ruin the surprise for you - it did not.
Like i said in my other reply to you, don’t make it look like you’re the muscly bloke in the gym who is a retard and no-one wants to talk to. Be more helpful.
First of all, where did you say this? I’ve looked in your other post which was posted in a thread about Container Station and some issues another user had. Your issue has nothing to do with Containers.
All you did was come in here and say the thing is a piece of junk. Instead of starting a new thread asking for help. I don’t know why QNAP would tell you to upgrade a TS-464 to QuTS Hero beta.
So why don’t you actually tell us the problems you have had and go into detail in your own thread about it.
This was your FIRST post in the other thread:
mingmanhk
this always happened to me, and should not be expected after investing a considerable amount of money in the T464. In raising a support ticket - I was asked to install something that bricked my media drive (has been applying ACL 2.0 for over a week and a half). This is a pile of crap.
I will install a different OS on it if I can’t get stability, or bloody normal performance expected from a QNAP NAS!
The other thread was all about issues this user had with a Container Station folder. Now you just came on and said “This happened to me…”
What happened to you? What did it have to do with Container Station?
If you would like help, please post your actual problem in its own thread and we will try to help you out. If you look at my posts (feel free to do so), you will see I’m not some “muscle” guy idiot just picking at people. But you came in and posted something that didn’t at all talk about your issue and then started trashing the product.
So please, what was the issue you had and then let’s talk about how we can fix it. I get the beta introduced additional problems, but I’m not entirely sure why they told you to install a beta version of QuTS hero to try to fix something…