Unlocking encrypted volume hangs at 43% after updating to QTS 4.5.2.1630 Build 20210406. Unwanted app stops & restarts

[cserl]

Ticket was sent to QNAP with the following failure description and screenshot. Device: TS-1277 with 2 WD10 in Raid1.
Main symptoms:
System becomes unresponsive
Unlock operations stalls
Applications are stopped unwantedly, eg. Virtualization Station, Container Station, etc.

The firmware was just updated to the latest QTS 4.5.2.1630 Build 20210406 and rebooted. After the reboot I performed following steps:

1. I Navigated to Storage and Snapshots > Storage > Storage and Snapshot.

2. I started unlocking four encrypted volumes one by one entering the key manually. I observed that after entering the key for one volume and before jumping over to the next volume to be unlocked, the user interface stopped refreshing and the unlocking status was not displayed for about 10 seconds. If I return here to reenter the key for the volume previously entered, it was accepted again, without error message.

3. I observed that the unlock operation started.

4. I observed that unwanted applications stops took place, eg. virtualization station, container station, etc.

The system became unresponsive, see attached screenshot.

5. I observed that the unlock operation hanged at 43%, see attached screenshot. I waited for more than an hour which is unusually long time.

6. From time to time the system became so much unresponsive that the following error message was displayed: "The server is busy or the network is disconnected!
Make sure the NAS can be reached and then reload the page."

A similar unresponsiveness was happening with the previous firmware version as well, but it was not so dramatical as after the firmware refresh.

Please fix the software, so that unwanted applications stops and restarts do not happen during the unlocking process.

Please speed up the unlocking process. Even in the normal case waiting 20 minutes was unacceptably long time. Now hanging is even worse.

See earlier similar phenomena reported 3 years back:
viewtopic.php?t=147308
viewtopic.php?t=142774

[Felixxx]

It seems that Qnap discontinued this firmware version.
I'm looking for specific news.

[Guapo81]

Ticket was sent to QNAP with the following failure description and screenshot. Device: TS-1277 with 2 WD10 in Raid1.
Main symptoms:
System becomes unresponsive
Unlock operations stalls
Applications are stopped unwantedly, eg. Virtualization Station, Container Station, etc.

Hi,

It's "good" to see that I'm not the only one having these exact same problems. Been having them on my TS-h886 since the beginning of january when I first installed the system.
I'm running QuTS-hero OS h4.5.1.1582 and have the exact same symptoms in exactly the same order as you described.

Allthough annoying, I found out that it doesn't necessarily have to be a show stopper, when you apply the following;
Start the system and wait for it to fully boot, then apply patience (take first beer), then wait for the phenomenon where all the apps start misbehaving by stopping and restarting out of the blue, this happens with all the apps installed in my case. (Approx. 5 to 10 min after boot)
After that wait (take second beer) till all the apps have restarted again and system gets into steady state.
After that start unlocking your encrypted volumes / folders (and take a third beer while you're at it, because indeed this takes a long time also).

After applying this order and patience the system gets in a steady state where everything seems to function just properly.
I also experienced that when you make the mistake of starting to unlock the encrypted folder during this unwanted restart of apps, the system will hang completely and become unresponsive.

Hope they find a fix for this, because like I mentioned it is annoying... (and bad for the liver in the situation as described above...)

[cserl]

Hi,
thank you for confirming the exact same behavior. We can be sure that this is a fault by design.
See also reported here from a 3rd source:
https://www.reddit.com/r/qnap/comments/ ... _twice_on/

I wonder why none of the enterprise users initiate a lawsuit since the system behavior is not as advertised.
Problems known to Qnap for 3 years now, they didn't give a **.

[Guapo81]

I wonder why none of the enterprise users initiate a lawsuit since the system behavior is not as advertised.
Problems known to Qnap for 3 years now, they didn't give a **.

Apparently it doesn't seem to happen on all systems I guess. I have been using and still are using encrypted folders on my TVS-682 as well, running QTS.
Strangly enough with that system I've never had this same problem nor am I able to reproduce it on that box...
Also if this was a problem for many users / units, one would expect more community users to reply in a topic like this, but it remains surprisingly still...

For me it's a riddle where this problem lies, since my first guess was that the new QuTS Hero OS was to blame, but apparently this is not the case.
Have to keep fingers crossed I guess and hope they find it and fix it.

[holger_kuehn]

I'm using encrypted shares as well without any trouble, but the OP said encrypted volume. Might be the difference here ....

[Guapo81]

I'm using encrypted shares as well without any trouble, but the OP said encrypted volume. Might be the difference here ....

True, I've been struggling a bit with this naming of storage items since my new system (TS-h886), running QuTS hero, is ZFS file system, so no volumes there, but shared folders / LUN's in storage pools. But with this system I'm having the exact same problems as described (where it comes to unlocking the shared folders).
On my "old" system (TVS-682) I have a more classic setup with one legacy volume; there I use encrypted shares indeed, but without problems.

I agree we're maybe not speaking of exactly the same setup, but still the problems / symptoms are completely the same.

[Ron1963]

I have two volumes on a storage pool. One of those is encrypted and I installed build 1630 this morning on my 251D. No problems with unlocking. Disclaimer, there is only one 18TB disk in the NAS, so no Raid.