QTS version 5.2.6.3195 (should be the most recent one)
Disks: 4x WD30EFRX HDD 3TB which are really old. The disks are configured as RAID5 and one big file system containing 4 shares plus user homes.
Yesterday evening all of a sudden my TS-453D did not answer anymore.
I performed a hard shutdown and rebooted the NAS over night.
Qfinder detects it under its normal IP address, but I cannot login via Browser. Qfinder shows a yellow disk icon saying something like “HDD full or in an unnormal state” (translated from German). I can connect via SMB to the shares, this shows me 1.88TB available, so disks are not full.
After connecting to the shares I cannot move into a folder or perform any other file operation. Any operation times out, SMB connection gets dropped.
I could login via ssh and gave the command to reboot in maintenance mode, but it shows only “processing” but nothing happens since hours.
LEDs:
1: “i”-LED shows green
2: Network LED shows blinking yellow: indicates traffic
3: is off
4: 1st HDD is very busy blinking green
5-7: HDD 2,3,4 blinking green from time to time
Very strange: The Plex server on the NAS is still operational, I can watch films on my TV…
I expected after a HDD crash I still would have access to the GUI and could identify the issue. But in this state I cannot identify the root cause.
Has the NAS itself an issue?
Or only one HDD, which one?
Hi @JimBimm sorry that the QTS 5.2.6.3195 has a known issue that cause the increase of CPU usage, you can refer to this post
Qfinder detects it under its normal IP address, but I cannot login via Browser
Rolling back to QTS 5.2.5 should can resolve the CPU problem. But you mentioned that you can not login it via browser, you may need to open a support ticket on the Customer Service website and use Team Viewer to allow the support team to remotely downgrade your NAS.
We’ve confirmed with the Support Team that the issue has been resolved.
Just a quick reminder: sometimes these types of problems are caused by aging or failing hard drives. For data safety, please be sure to regularly check your drive’s health status.
If you have any other questions, please feel free to ask. Thanks!
the support was extremely good, thanks a lot to QNAP for providing such an outstanding service!
After several failing attempts I finally was able to reboot the NAS is Rescue Mode, so the supporter could immediately act when he called me and took over via Teamviewer. First he downgraded the Firmware to v5.2.5 and then mounted the drives again. Second step was to rsync all the data to an external USB-Drive. During this we found that HDD#1 had an issue.
Bottomlined I would say this incident was a combination of a firmware issue and a failing (really old) harddrive.
In the meanwhile 2 new HHDs are syncing in RAID1 and waiting for further installation. From my perspective the issue is solved. Except: The NAS frequently reminds me to upgrade the Firmware to v5.2.6. I will not do that for sure and wait for the next revision.
Thanks again to QNAP, your support is great, I will spread the good news not only in this forum.
