RN3220 - Management service offline after 6.4.2 update #26481705

[G-Dog]

Hi,

We have lost access to management services since we upgraded to firmware 6.4.2. Was able to log in to the box via SSH and the error is with the readynasd service that is not starting. When checking the status of the service the following is returned;

++++++++++++++++++++++++++++++++++++++++++++++++++++++

root@NAS:~# systemctl status readynasd
readynasd.service - ReadyNAS System Daemon
Loaded: loaded (/lib/systemd/system/readynasd.service; enabled)
Active: activating (start) since Tue, 16 Feb 2016 12:56:39 +0000; 1min 9s ago
Main PID: 3741 (readynasd)
Status: "Importing DB"
CGroup: name=systemd:/system/readynasd.service
├ 3258 /usr/sbin/readynasd -v 3 -t
└ 3741 /usr/sbin/readynasd -v 3 -t

Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.

++++++++++++++++++++++++++++++++++++++++++++++++++++++

root@NAS:~# systemctl status readynasd
readynasd.service - ReadyNAS System Daemon
Loaded: loaded (/lib/systemd/system/readynasd.service; enabled)
Active: deactivating (stop-sigterm) (Result: exit-code)
Process: 3741 ExecStart=/usr/sbin/readynasd -v 3 -t (code=exited, status=255)
Status: "Importing DB"
CGroup: name=systemd:/system/readynasd.service
└ 3258 /usr/sbin/readynasd -v 3 -t

Feb 16 12:57:59 NAS readynasd[3741]: rndb_create() ==> 3 (10136ms)
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.

I have reinstalled the operationg system without success. Has any body got any suggestions as to what could be stopping this service starting up properly?

[JennC]

Hello G-Dog,

Welcome tot he community!

What was the FW version prior to updating to 6.4.2? Are you still able to access the shares? 

Try rebooting the NAS, please and see if same problem

Regards,

[G-Dog]

Hi,

Thanks JennC, nice to be here 🙂

The prior version was 6.4.1, unfortunately I can't access any of the shares or iSCSI links I had set up. Have tried a reboot and still no joy....

[JennC]

Hello G-Dog,

It does seem we have no choice but to contact support center this time. I checked your profile and did not find RN516 registered.

Run RAIDar and see if it detects your NAS, you should be able to download logs using it too.

Regards,

[G-Dog]

Uhm, I don't know where the RN516 has come from - I have an RN3220! It is registered but over 90 days old so no support 😞

RAIDar cannot download the logs anyway so all in all, I'm stuffed!

Thanks anyway....

[JennC]

Hello G-Dog,

You have indicated RN516 on the title of this topic 🙂

Anyway, checking on the registration of your RN3220, it was not registered right, it has no SN on the registration. Have it ready so it can be corrected and contact support as this problem you have appears to be volume went offline after the FW update.

Regards,

[mdgm-ntgr]

I have fixed the thread title. So you did a defrag and the unit became unresponsive then somehow updated the system to 6.4.2?

[G-Dog]

Hi,

Thank you!

The NAS is being used for backups so there is a lot of changing data. I decided to run a defrag a few weeks ago and it took the box down so a support ticket was logged. The box came back up on a reboot and appeared to be fine. Most support desks I speak to ask that the firmware/software is up to the latest version before they can investigate so seeing that 6.4.2 was available I ran the upgrade. Things were running fine for about a week and then the unit became unresponsive. Right now the power led is flashing and there is drive activity on 2 of the disks but I only have SSH access.

Hope that clarifies.

[JennC]

Hello G-Dog,

I checked your case submission and found that it is being handled by a higher tier and about to escalate it for remote fix. You have provided the right email address where the NAS was registered to. Let's wait for Marc who is assigned to your case to process it.

Regards,

[mdgm-ntgr]

I can see support is working on this on case #26481705 now.

[JennC]

Hello G-Dog,

Please get back to your online support case. Support is trying to remote in but unable to and is asking you to relaunch it.

Regards,

[defcon84]

I have the same issue after upgrading from 6.3.8 to 6.4.2.

root@SKNAS02:~# systemctl status readynasd
readynasd.service - ReadyNAS System Daemon
Loaded: loaded (/lib/systemd/system/readynasd.service; enabled)
Active: activating (start) since Fri, 19 Feb 2016 11:06:41 +0100; 5min ago
Main PID: 2248 (readynasd)
Status: "Importing DB"
CGroup: name=systemd:/system/readynasd.service
└ 2248 /usr/sbin/readynasd -v 3 -t
Feb 19 11:06:42 SKNAS02 readynasd[2248]: readynasd log started
Feb 19 11:06:42 SKNAS02 readynasd[2248]: readynasd started. (restarted=0)
Feb 19 11:06:43 SKNAS02 readynasd[2248]: DB (main) schema version: 19 ==> 19
Feb 19 11:06:43 SKNAS02 readynasd[2248]: DB (queue) schema version: new ==> 0

very annoying, does someone have a fix for this?

[defcon84]

root@SKNAS02:~# systemctl status readynasd                                       readynasd.service - ReadyNAS System Daemon
          Loaded: loaded (/lib/systemd/system/readynasd.service; enabled)
          Active: activating (start) since Fri, 19 Feb 2016 11:17:11 +0100; 26s ago
        Main PID: 3357 (readynasd)
          Status: "Initialize"
          CGroup: name=systemd:/system/readynasd.service
                  ├ 2248 /usr/sbin/readynasd -v 3 -t
                  ├ 3357 /usr/sbin/readynasd -v 3 -t
                  └ 3382 /bin/sh -e /run/proc_readynasd.dZUxOv

Feb 19 11:17:12 SKNAS02 readynasd[3357]: readynasd log started
Feb 19 11:17:12 SKNAS02 readynasd[3357]: readynasd started. (restarted=0)

a step further, still inusable.

top - 11:18:52 up 13 min,  1 user,  load average: 5.24, 4.54, 2.93
Tasks: 200 total,   1 running, 199 sleeping,   0 stopped,   0 zombie
%Cpu(s):  1.9 us,  5.8 sy,  0.0 ni, 71.1 id, 21.0 wa,  0.0 hi,  0.1 si,  0.0 st
KiB Mem:   2036452 total,  2004060 used,    32392 free,       20 buffers
KiB Swap:  1047932 total,        0 used,  1047932 free,  1232596 cached

  PID USER      PR  NI  VIRT  RES  SHR S  %CPU %MEM    TIME+  COMMAND
 2026 root      20   0     0    0    0 D  12.6  0.0   0:33.48 btrfs-cleaner
 3160 root      20   0     0    0    0 S   9.3  0.0   0:03.01 kworker/u8:1
  612 root      20   0     0    0    0 S   0.7  0.0   0:01.47 kswapd0
 2241 root      20   0  127m 7376 3792 S   0.7  0.4   0:05.40 apache2
 2637 admin     20   0  132m 9768 5912 S   0.7  0.5   0:00.31 apache2
 2239 root      20   0  127m 9644 6188 S   0.3  0.5   0:00.08 apache2
 2320 admin     20   0  132m 9948 6000 S   0.3  0.5   0:01.16 apache2
 3641 root      20   0 28592 3024 2480 R   0.3  0.1   0:00.05 top
    1 root      20   0 49572 5772 3440 S   0.0  0.3   0:02.24 systemd
    2 root      20   0     0    0    0 S   0.0  0.0   0:00.00 kthreadd
    3 root      20   0     0    0    0 S   0.0  0.0   0:00.05 ksoftirqd/0
    5 root       0 -20     0    0    0 S   0.0  0.0   0:00.00 kworker/0:0H
    6 root      20   0     0    0    0 S   0.0  0.0   0:01.00 kworker/u8:0
    7 root      20   0     0    0    0 S   0.0  0.0   0:00.47 rcu_sched
    8 root      20   0     0    0    0 S   0.0  0.0   0:00.00 rcu_bh

Very high load, can't see why.

Only SSH works.

[StephenB]

defcon84: After btrfs-cleaner completes, the system should run normally.

Also, it'd be better to use your own thread, as your issue could be different (and even if it isn't, working with multiple posters on the same thread gets very confusing).

[defcon84]

Ok, ill do that next time 🙂

I had contact with netgear support, they indeed said that ill have to wait until the defrag was ready.

Or boot in readonly and copy the files, set the nas to factory default and copy the files back.

I think im going to wait. hopefully it will be done on monday.