I was testing beta since release. I noticed significantly faster responses on web interface, what was nice. Firstly everything was working well, but recently I tried to connect USB drive with shared folder what was not visible in Windows (only in File Station). I checked permissions, all was set correctly (and worked in QuTS 5.x). When I tried to change permissions, I got ACL (-2) error, so I tried to upgrade to ACL 2.0 and then the hell started. Since then the NAS freezes randomly, loosing connection to SMB shares and File Station cannot be opened. It seems like some process freezes in the NAS randomly. After restart it always work well for a random period of time. Sometimes it is a few minutes, sometimes a few hours. When it stop working, restart again help for a random time, and then again and again …
All this started with upgrade to ACL 2.0, before that SMB shares were working well.
Hi PaveIP, sure it is a problem and we like to analyze further. Would you please go to Help Desk app and file a ticket sharing the system log from there? Thank you for your sharing!
I already opened a ticket Q-202512-63204. If you need any further assistance, please just let me know. I believe that this is not a problem of memory modules as the NAS was working perfectly till ACL 2.0 upgrade.
I believe I have found the cause of the instability issue. I have read somewhere that it may be caused by HBS 3, so I stopped all the scheduled backups and for now it is running stable about 24 hours. I suppose that these backups were the cause. In my case the only open issue is the USB share in Windows, I still get the ACL (-2) error, when I try to update share permission and I cannot see it in any Windows PC. The USB disk is NTFS formatted and when connected directly to PC it works well, also I can see it in File Station and access it via FTP when connected to the NAS.
Finally I got USB share to work in Windows PC. I enabled and disabled back ABSE and ABE on USB share and it appeared and working in Windows PC. I still get ACL (-2) error, when I try to change permission, but the share is now visible.
What I am absolutely disappointed about is the QNAP support approach. They did not help at all. They asked for logs, then they told me that I have additional memory module and they blame memory module for everything and won’t do anything until I remove this memory module. I was really expecting more from the support. I case of HW issue, I would understand that, but in case we voluntarily do a beta testing, I would really expect better support. I think that next time, I will wait for final version. Sorry, but this is not support that I expect during beta testing.
The memory bit is QNAP’s first line of defense. We all go through it. They insisted some problems I was having was due to memory until I ran their memory test and proved it wasn’t. Now they never ask me this any longer.