ReadyNAS 3220 Locking up after upgrading to 6.2

Your logs indicate that one of your disks is failing.

What firmware did you last do a factory reset (wipes all data, settings, everything) on?

Why have you set such a high NFS thread count?

Also I noticed two subvolumes for the kplatte user in different cases.

mdgm wrote:
Your logs indicate that one of your disks is failing.

Hmm all drives are showing healthy. We did replace a drive about a month ago. Does it say which drive is failing?

mdgm wrote:
What firmware did you last do a factory reset (wipes all data, settings, everything) on?

Never did a factory reset but think this one came with 6.1.4 on it.

mdgm wrote:
Why have you set such a high NFS thread count?

No idea on this one. Not even sure how to set or change this??

mdgm wrote:
Also I noticed two subvolumes for the kplatte user in different cases.

Yeah not sure why there is 2users shares for me. Might been original account i tried setting up.

Sent you a PM.

OK thanks will get that drive replaced and see if that stops the lockups. But strange that it only started locking up when updated to 6.1.9 and 6.2
Aslo RAIDAR still shows status is Support:64764 Is that an issue and how can I get it out of support mode?

We didn't change anything related to NFS in 6.1.9 or 6.2. The issue occurring after the update is a coincidence.

That still being enabled is not an issue.

Leaving it enabled would help with troubleshooting though if you like I can turn that off.

OK new drive should be here tomorrow. Hopefully that will resolves the lockup.

Replaced drive on Friday took 20 hours to rebuild. NAS locked up again last night.
any other ideas to try? Maybe should turn off tech support mode if can that is only thing i can see different from when running 6.1.8.

That is not tech support mode, but rather Secure Diagnostics mode.

If it was in tech support mode (a boot menu option) you wouldn't be able to access the UI, your data etc.

Secure Diagnostics mode would not be the cause of the lockups.

Can you send a fresh set of logs if you haven't already?

Did you stop readynasd as suggested before the backup jobs ran?

Have you updated to the production 6.2.1 release yet?

mdgm wrote:

That is not tech support mode, but rather Secure Diagnostics mode. If it was in tech support mode (a boot menu option) you wouldn't be able to access the UI, your data etc. Secure Diagnostics mode would not be the cause of the lockups. Can you send a fresh set of logs if you haven't already? Did you stop readynasd as suggested before the backup jobs ran? Have you updated to the production 6.2.1 release yet?

Updated to production release 6.2.1 Did not try to stop readynasd will do that tonight
Will send fresh log file.
Here is latest TOP info from when it locked up.

top - 05:21:10 up 20:48,  1 user,  load average: 8.53, 4.12, 3.33
Tasks: 179 total,  11 running, 168 sleeping,   0 stopped,   0 zombie
%Cpu(s):  0.2 us, 50.3 sy,  0.0 ni, 24.8 id, 24.7 wa,  0.0 hi,  0.0 si,  0.0 st
KiB Mem:   3938476 total,  3482344 used,   456132 free,      600 buffers
KiB Swap:  5232636 total,    15708 used,  5216928 free,  2364720 cached

  PID USER      PR  NI  VIRT  RES  SHR S  %CPU %MEM    TIME+  COMMAND
  612 root      20   0     0    0    0 R 100.1  0.0   4:21.24 kswapd0
 5080 root      20   0     0    0    0 R  99.8  0.0   5:36.97 nfsd
 3111 KPlatte   20   0  263m 5904 3620 S   0.3  0.1   0:22.02 smbd
27627 root      20   0 28548 1276  880 R   0.3  0.0   0:51.35 top
    1 root      20   0 48344 2244  364 S   0.0  0.1   0:01.12 systemd
    2 root      20   0     0    0    0 S   0.0  0.0   0:00.19 kthreadd
    3 root      20   0     0    0    0 R   0.0  0.0   0:12.45 ksoftirqd/0
    6 root      rt   0     0    0    0 R   0.0  0.0   0:00.10 migration/0
    7 root      rt   0     0    0    0 R   0.0  0.0   0:00.10 watchdog/0
    8 root      rt   0     0    0    0 S   0.0  0.0   0:00.04 migration/1
   10 root      20   0     0    0    0 S   0.0  0.0   0:01.30 ksoftirqd/1
   11 root      20   0     0    0    0 R   0.0  0.0   0:09.79 kworker/0:1
   12 root      rt   0     0    0    0 S   0.0  0.0   0:00.09 watchdog/1
   13 root      rt   0     0    0    0 S   0.0  0.0   0:00.05 migration/2
   15 root      20   0     0    0    0 S   0.0  0.0   0:03.01 ksoftirqd/2
   16 root      rt   0     0    0    0 S   0.0  0.0   0:00.10 watchdog/2
   17 root      rt   0     0    0    0 R   0.0  0.0   0:00.06 migration/3
   19 root      20   0     0    0    0 R   0.0  0.0   0:00.35 ksoftirqd/3
   20 root      rt   0     0    0    0 R   0.0  0.0   0:00.10 watchdog/3
   21 root       0 -20     0    0    0 S   0.0  0.0   0:00.00 khelper
  271 root      20   0     0    0    0 S   0.0  0.0   0:00.04 sync_supers
  273 root      20   0     0    0    0 S   0.0  0.0   0:00.00 bdi-default
  275 root       0 -20     0    0    0 S   0.0  0.0   0:00.00 kblockd
  454 root      20   0     0    0    0 S   0.0  0.0   0:00.00 khubd
  463 root       0 -20     0    0    0 S   0.0  0.0   0:00.00 md
  568 root       0 -20     0    0    0 S   0.0  0.0   0:00.00 rpciod
  569 root      20   0     0    0    0 S   0.0  0.0   0:01.03 kworker/1:1
  607 root      20   0     0    0    0 S   0.0  0.0   0:00.01 khungtaskd

========================================
= Making "Support: #####" message disappear =
========================================

"Support: #####" simply means that SUPPORT SSH was enabled at the bottom of the page SYSTEM->SETTINGS in SUPPORT section (not the same as regular SSH bottom at the top of the SYSTEM->SETTINGS page under SERVICES section), or perhaps a Netgear Support agent enabled it when the unit was in tech support mode, so that they could test the NASes functionality when it comes up in normal mode. It means that an engineering or netgear level 3 agent has highly secure and encrypted access to the NAS via SSH if they need it. We can only set this up if the Remote Access policy is accepted.

The "Support: #####" message is held in memory in /run/.os_status file. It will go away after reboot since its held in volatile mem folder /run.

To make the "Support: #####" go away do this: Go to SYSTEM->SETTINGS->SUPPORT enable and disable it, now reboot the unit or instead of reboot login via SSH and type:

echo "6.2.1" > /run/.os_status
# Replace 6.2.1 with current firmware number.