ReadyNAS 2120 is working only for 4min

[Alein]

HI,

i have a problem with my 2nd 2120 unit.

It is strange but just at 1:45am it freeze, and since this time, after reboot NAS is able to work for ~4:33 minutes.

I am not able to see web interface, it freeze on progress bar.

SSH is working (4minutes), but PING is working all the time, only PING.

I was able to check HDD, and all ale in very good conditions.

root@NAS-A:~# smartctl -a /dev/sdc
smartctl 6.5 2016-05-07 r4318 [armv7l-linux-4.1.30.armada.1] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model: WDC WD4002FFWX-68TZ4N0
Serial Number: NHG3Y9NM
LU WWN Device Id: 5 000cca 243c1cb25
Firmware Version: 83.H0A83
User Capacity: 4,000,787,030,016 bytes [4.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 7200 rpm
Form Factor: 3.5 inches
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: ACS-2, ATA8-ACS T13/1699-D revision 4
SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Mon Apr 3 22:06:09 2017 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status: (0x80) Offline data collection activity
was never started.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 113) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 571) minutes.
SCT capabilities: (0x003d) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000b 100 100 016 Pre-fail Always - 0
2 Throughput_Performance 0x0005 135 135 054 Pre-fail Offline - 112
3 Spin_Up_Time 0x0007 142 142 024 Pre-fail Always - 455 (Average 474)
4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 1030
5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 0
7 Seek_Error_Rate 0x000b 100 100 067 Pre-fail Always - 0
8 Seek_Time_Performance 0x0005 128 128 020 Pre-fail Offline - 18
9 Power_On_Hours 0x0012 100 100 000 Old_age Always - 4218
10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 29
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 1166
193 Load_Cycle_Count 0x0012 100 100 000 Old_age Always - 1166
194 Temperature_Celsius 0x0002 181 181 000 Old_age Always - 33 (Min/Max 23/48)
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0
197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always - 0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]

SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

after login

No logon servers - interesting

Welcome to ReadyNASOS 6.6.1

Last login: Mon Apr 3 22:05:22 2017 from 172.26.12.230
root@NAS-A:~# df -h
Filesystem Size Used Avail Use% Mounted on
udev 10M 4.0K 10M 1% /dev
/dev/md0 4.0G 659M 3.0G 18% /
tmpfs 1009M 0 1009M 0% /dev/shm
tmpfs 1009M 424K 1009M 1% /run
tmpfs 505M 716K 504M 1% /run/lock
tmpfs 1009M 0 1009M 0% /sys/fs/cgroup
/dev/md127 11T 8.9T 2.1T 81% /data
/dev/md127 11T 8.9T 2.1T 81% /apps
/dev/md127 11T 8.9T 2.1T 81% /home
root@NAS-A:~# ifconfig
bond0 Link encap:Ethernet HWaddr 28:c6:8e:35:86:a8
inet addr:172.26.10.10 Bcast:172.26.10.255 Mask:255.255.255.0
inet6 addr: fe80::2ac6:8eff:fe35:86a8/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST MTU:9000 Metric:1
RX packets:603 errors:0 dropped:51 overruns:0 frame:0
TX packets:473 errors:0 dropped:8 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:101028 (98.6 KiB) TX bytes:78209 (76.3 KiB)

eth0 Link encap:Ethernet HWaddr 28:c6:8e:35:86:a8
UP BROADCAST RUNNING SLAVE MULTICAST MTU:9000 Metric:1
RX packets:250 errors:0 dropped:12 overruns:0 frame:0
TX packets:401 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:532
RX bytes:20746 (20.2 KiB) TX bytes:50898 (49.7 KiB)
Interrupt:26

eth1 Link encap:Ethernet HWaddr 28:c6:8e:35:86:a8
UP BROADCAST RUNNING SLAVE MULTICAST MTU:9000 Metric:1
RX packets:867 errors:0 dropped:46 overruns:0 frame:0
TX packets:262 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:532
RX bytes:115408 (112.7 KiB) TX bytes:39895 (38.9 KiB)
Interrupt:27

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:10 errors:0 dropped:0 overruns:0 frame:0
TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1014 (1014.0 B) TX bytes:1014 (1014.0 B)

root@NAS-A:~#

During night VDP is making backups, and some other backups are comming with RSYNC.

but during 4min, i am not able to check much.

When it freeze, I am able to write on SSH, but there is no output.

root@NAS-A:~# b
-bash: b: command not found
root@NAS-A:~# 1                               < freeze here
eqwe
qwe
qwegdgdfg
dfgdfg
dfg
dfg
d
fg

PS ~20 seconds before freeze

root@NAS-A:~# ps -AF
UID PID PPID C SZ RSS PSR STIME TTY TIME CMD
root 1 0 2 6893 5640 0 22:32 ? 00:00:05 /sbin/init
root 2 0 0 0 0 0 22:32 ? 00:00:00 [kthreadd]
root 3 2 0 0 0 0 22:32 ? 00:00:00 [ksoftirqd/0]
root 4 2 0 0 0 0 22:32 ? 00:00:00 [kworker/0:0]
root 5 2 0 0 0 0 22:32 ? 00:00:00 [kworker/0:0H]
root 6 2 0 0 0 0 22:32 ? 00:00:01 [kworker/u4:0]
root 7 2 0 0 0 1 22:32 ? 00:00:00 [rcu_sched]
root 8 2 0 0 0 0 22:32 ? 00:00:00 [rcu_bh]
root 9 2 0 0 0 0 22:32 ? 00:00:00 [migration/0]
root 10 2 0 0 0 0 22:32 ? 00:00:00 [watchdog/0]
root 11 2 0 0 0 1 22:32 ? 00:00:00 [watchdog/1]
root 12 2 0 0 0 1 22:32 ? 00:00:00 [migration/1]
root 13 2 0 0 0 1 22:32 ? 00:00:00 [ksoftirqd/1]
root 14 2 0 0 0 1 22:32 ? 00:00:00 [kworker/1:0]
root 15 2 0 0 0 1 22:32 ? 00:00:00 [kworker/1:0H]
root 16 2 0 0 0 1 22:32 ? 00:00:00 [khelper]
root 17 2 0 0 0 0 22:32 ? 00:00:00 [kdevtmpfs]
root 18 2 0 0 0 1 22:32 ? 00:00:00 [netns]
root 19 2 1 0 0 1 22:32 ? 00:00:03 [kworker/u4:1]
root 280 2 0 0 0 1 22:32 ? 00:00:00 [khungtaskd]
root 281 2 0 0 0 1 22:32 ? 00:00:00 [writeback]
root 283 2 0 0 0 1 22:32 ? 00:00:00 [crypto]
root 284 2 0 0 0 1 22:32 ? 00:00:00 [bioset]
root 286 2 0 0 0 1 22:32 ? 00:00:00 [kblockd]
root 295 2 0 0 0 1 22:32 ? 00:00:00 [ata_sff]
root 314 2 0 0 0 0 22:32 ? 00:00:00 [md]
root 405 2 0 0 0 1 22:32 ? 00:00:00 [kworker/1:1]
root 406 2 0 0 0 0 22:32 ? 00:00:00 [rpciod]
root 407 2 0 0 0 0 22:32 ? 00:00:00 [kworker/0:1]
root 412 2 0 0 0 1 22:32 ? 00:00:01 [kswapd0]
root 476 2 0 0 0 0 22:32 ? 00:00:00 [fsnotify_mark]
root 487 2 0 0 0 1 22:32 ? 00:00:00 [nfsiod]
root 494 2 0 0 0 1 22:32 ? 00:00:00 [cifsiod]
root 582 2 0 0 0 0 22:32 ? 00:00:00 [scsi_eh_0]
root 583 2 0 0 0 1 22:32 ? 00:00:00 [scsi_tmf_0]
root 586 2 0 0 0 0 22:32 ? 00:00:00 [scsi_eh_1]
root 587 2 0 0 0 1 22:32 ? 00:00:00 [scsi_tmf_1]
root 590 2 2 0 0 1 22:32 ? 00:00:06 [kworker/u4:2]
root 591 2 2 0 0 1 22:32 ? 00:00:05 [kworker/u4:3]
root 598 2 0 0 0 0 22:32 ? 00:00:00 [scsi_eh_2]
root 599 2 0 0 0 1 22:32 ? 00:00:00 [scsi_tmf_2]
root 602 2 0 0 0 0 22:32 ? 00:00:00 [scsi_eh_3]
root 603 2 0 0 0 1 22:32 ? 00:00:00 [scsi_tmf_3]
root 606 2 1 0 0 1 22:32 ? 00:00:02 [kworker/u4:4]
root 607 2 1 0 0 0 22:32 ? 00:00:03 [kworker/u4:5]
root 618 2 0 0 0 0 22:32 ? 00:00:00 [scsi_eh_4]
root 619 2 0 0 0 1 22:32 ? 00:00:00 [scsi_tmf_4]
root 622 2 0 0 0 0 22:32 ? 00:00:00 [scsi_eh_5]
root 623 2 0 0 0 1 22:32 ? 00:00:00 [scsi_tmf_5]
root 626 2 1 0 0 1 22:32 ? 00:00:03 [kworker/u4:6]
root 627 2 0 0 0 1 22:32 ? 00:00:01 [kworker/u4:7]
root 630 2 0 0 0 0 22:32 ? 00:00:00 [target_completi]
root 631 2 0 0 0 1 22:32 ? 00:00:00 [tmr-rd_mcp]
root 632 2 0 0 0 1 22:32 ? 00:00:00 [xcopy_wq]
root 635 2 0 0 0 1 22:32 ? 00:00:00 [irq/29-d00d0000]
root 739 2 0 0 0 1 22:32 ? 00:00:00 [raid5wq]
root 743 2 0 0 0 1 22:32 ? 00:00:00 [dm_bufio_cache]
root 775 2 0 0 0 1 22:32 ? 00:00:00 [ipv6_addrconf]
root 788 2 0 0 0 1 22:32 ? 00:00:00 [bioset]
root 795 2 0 0 0 1 22:32 ? 00:00:00 [deferwq]
root 805 2 0 0 0 0 22:32 ? 00:00:00 [kworker/0:2]
root 807 2 0 0 0 1 22:32 ? 00:00:00 [kworker/u4:8]
root 870 2 0 0 0 0 22:32 ? 00:00:00 [ubi_bgt0d]
root 952 2 0 0 0 1 22:32 ? 00:00:00 [kworker/1:2]
root 1004 2 0 0 0 0 22:32 ? 00:00:00 [bioset]
root 1005 2 0 0 0 1 22:32 ? 00:00:00 [md0_raid1]
root 1014 2 0 0 0 1 22:32 ? 00:00:00 [bioset]
root 1016 2 0 0 0 0 22:32 ? 00:00:00 [md1_raid6]
root 1020 2 0 0 0 0 22:32 ? 00:00:00 [btrfs-worker]
root 1021 2 0 0 0 1 22:32 ? 00:00:00 [kworker/u5:0]
root 1022 2 0 0 0 0 22:32 ? 00:00:00 [btrfs-worker-hi]
root 1023 2 0 0 0 0 22:32 ? 00:00:00 [btrfs-delalloc]
root 1024 2 0 0 0 0 22:32 ? 00:00:00 [btrfs-flush_del]
root 1025 2 0 0 0 0 22:32 ? 00:00:00 [btrfs-cache]
root 1026 2 0 0 0 0 22:32 ? 00:00:00 [btrfs-submit]
root 1027 2 0 0 0 0 22:32 ? 00:00:00 [btrfs-fixup]
root 1028 2 0 0 0 0 22:32 ? 00:00:00 [btrfs-endio]
root 1029 2 0 0 0 0 22:32 ? 00:00:00 [btrfs-endio-met]
root 1030 2 0 0 0 0 22:32 ? 00:00:00 [btrfs-endio-met]
root 1031 2 0 0 0 0 22:32 ? 00:00:00 [btrfs-endio-rai]
root 1032 2 0 0 0 0 22:32 ? 00:00:00 [btrfs-endio-rep]
root 1033 2 0 0 0 0 22:32 ? 00:00:00 [btrfs-rmw]
root 1034 2 0 0 0 0 22:32 ? 00:00:00 [btrfs-endio-wri]
root 1035 2 0 0 0 0 22:32 ? 00:00:00 [btrfs-freespace]
root 1036 2 0 0 0 0 22:32 ? 00:00:00 [btrfs-delayed-m]
root 1037 2 0 0 0 0 22:32 ? 00:00:00 [btrfs-readahead]
root 1038 2 0 0 0 0 22:32 ? 00:00:00 [btrfs-qgroup-re]
root 1039 2 0 0 0 0 22:32 ? 00:00:00 [btrfs-extent-re]
root 1040 2 0 0 0 0 22:32 ? 00:00:00 [btrfs-cleaner]
root 1041 2 0 0 0 0 22:32 ? 00:00:00 [btrfs-transacti]
root 1048 2 0 0 0 1 22:32 ? 00:00:00 [kworker/1:1H]
root 1052 2 0 0 0 0 22:32 ? 00:00:00 [kworker/0:1H]
root 1065 1 0 439 1236 0 22:32 ? 00:00:00 /usr/sbin/pilgrim
root 1077 2 0 0 0 1 22:32 ? 00:00:00 [kworker/1:3]
root 1087 1 0 5664 4456 0 22:32 ? 00:00:00 /lib/systemd/systemd-journald
root 1088 2 0 0 0 0 22:32 ? 00:00:00 [kworker/u5:1]
root 1109 2 0 0 0 1 22:32 ? 00:00:00 [bioset]
root 1110 2 0 0 0 1 22:32 ? 00:00:00 [md127_raid5]
root 1112 1 0 2425 3208 0 22:32 ? 00:00:00 /lib/systemd/systemd-udevd
root 1155 2 0 0 0 0 22:32 ? 00:00:00 [btrfs-worker]
root 1157 2 0 0 0 0 22:32 ? 00:00:00 [btrfs-worker-hi]
root 1158 2 0 0 0 0 22:32 ? 00:00:00 [btrfs-delalloc]
root 1159 2 0 0 0 0 22:32 ? 00:00:00 [btrfs-flush_del]
root 1160 2 0 0 0 0 22:32 ? 00:00:00 [btrfs-cache]
root 1161 2 0 0 0 0 22:32 ? 00:00:00 [btrfs-submit]
root 1162 2 0 0 0 0 22:32 ? 00:00:00 [btrfs-fixup]
root 1163 2 0 0 0 0 22:32 ? 00:00:00 [btrfs-endio]
root 1164 2 0 0 0 0 22:32 ? 00:00:00 [btrfs-endio-met]
root 1165 2 0 0 0 0 22:32 ? 00:00:00 [btrfs-endio-met]
root 1166 2 0 0 0 0 22:32 ? 00:00:00 [btrfs-endio-rai]
root 1167 2 0 0 0 0 22:32 ? 00:00:00 [btrfs-endio-rep]
root 1168 2 0 0 0 0 22:32 ? 00:00:00 [btrfs-rmw]
root 1169 2 0 0 0 0 22:32 ? 00:00:00 [btrfs-endio-wri]
root 1170 2 0 0 0 0 22:32 ? 00:00:00 [btrfs-freespace]
root 1171 2 0 0 0 0 22:32 ? 00:00:00 [btrfs-delayed-m]
root 1172 2 0 0 0 0 22:32 ? 00:00:00 [btrfs-readahead]
root 1173 2 0 0 0 0 22:32 ? 00:00:00 [btrfs-qgroup-re]
root 1174 2 0 0 0 0 22:32 ? 00:00:00 [btrfs-extent-re]
root 2348 2 8 0 0 0 22:33 ? 00:00:14 [btrfs-cleaner]
root 2349 2 0 0 0 1 22:33 ? 00:00:00 [btrfs-transacti]
avahi 2361 1 0 1042 2192 0 22:33 ? 00:00:00 avahi-daemon: running [NAS-A.local]
root 2362 1 0 1385 2312 0 22:33 ? 00:00:00 /usr/sbin/cron -f
root 2363 1 0 1585 3632 1 22:33 ? 00:00:00 /lib/systemd/systemd-logind
snmp 2364 1 0 3496 6828 1 22:33 ? 00:00:00 /usr/sbin/snmpd -f -Lo -u snmp -g snmp
avahi 2365 2361 0 1010 1220 1 22:33 ? 00:00:00 avahi-daemon: chroot helper
root 2366 1 0 472 1464 1 22:33 ? 00:00:00 /usr/sbin/wsdd2
root 2370 1 0 3264 2696 0 22:33 ? 00:00:00 /usr/sbin/mdcsrepaird -v
root 2371 2 0 0 0 0 22:33 ? 00:00:00 [bond0]
root 2410 1 0 442 1256 1 22:33 ? 00:00:00 /usr/sbin/raidard -S
root 2415 1 0 751 2156 1 22:33 ? 00:00:00 /sbin/mdadm -F -s -y -p /frontview/bin/md_event
root 2427 1 0 451 1368 1 22:33 ? 00:00:00 /usr/sbin/noflushd -d -n 120
message+ 2440 1 0 1544 2936 0 22:33 ? 00:00:00 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
root 2468 1 0 1216 2652 0 22:33 ? 00:00:00 /usr/sbin/connmand -n -r
root 2497 1 0 1981 4108 1 22:33 ? 00:00:00 /usr/sbin/sshd -D
root 2501 1 0 1110 2340 0 22:33 ? 00:00:00 /sbin/rpcbind -w
statd 2503 1 0 1156 2480 0 22:33 ? 00:00:00 /sbin/rpc.statd
root 2509 1 0 6325 6020 0 22:33 ? 00:00:00 /usr/sbin/nmbd
root 2515 2 0 0 0 0 22:33 ? 00:00:00 [nfsd4]
root 2516 2 0 0 0 0 22:33 ? 00:00:00 [nfsd4_callbacks]
root 2517 2 0 0 0 0 22:33 ? 00:00:00 [lockd]
root 2520 2 0 0 0 0 22:33 ? 00:00:00 [nfsd]
root 2521 2 0 0 0 0 22:33 ? 00:00:00 [nfsd]
root 2522 2 0 0 0 0 22:33 ? 00:00:00 [nfsd]
root 2523 2 0 0 0 0 22:33 ? 00:00:00 [nfsd]
root 2524 2 0 0 0 0 22:33 ? 00:00:00 [nfsd]
root 2525 2 0 0 0 0 22:33 ? 00:00:00 [nfsd]
root 2526 2 0 0 0 0 22:33 ? 00:00:00 [nfsd]
root 2527 2 0 0 0 0 22:33 ? 00:00:00 [nfsd]
root 2533 1 0 1117 1704 0 22:33 tty1 00:00:00 /sbin/agetty --noclear tty1 linux
root 2534 1 0 1072 1832 0 22:33 ttyS0 00:00:00 /sbin/agetty --keep-baud 115200 38400 9600 ttyS0 vt220
root 2540 1 0 724 1168 0 22:33 ? 00:00:00 /usr/sbin/rpc.idmapd
root 2543 1 0 1268 1884 0 22:33 ? 00:00:00 /usr/sbin/rpc.mountd --manage-gids --no-nfs-version 4
root 2548 1 0 7984 7532 1 22:33 ? 00:00:00 /usr/sbin/winbindd
root 2550 2548 0 7991 7992 0 22:33 ? 00:00:00 /usr/sbin/winbindd
root 2571 1 0 9499 12288 0 22:33 ? 00:00:00 /usr/sbin/smbd
root 2578 2571 0 8946 4956 0 22:33 ? 00:00:00 /usr/sbin/smbd
root 2579 2571 0 8946 4484 1 22:33 ? 00:00:00 /usr/sbin/smbd
root 2587 2548 0 8058 7204 0 22:33 ? 00:00:00 /usr/sbin/winbindd
root 2595 2548 0 7984 7032 0 22:33 ? 00:00:00 /usr/sbin/winbindd
root 2598 2548 0 8199 6736 1 22:33 ? 00:00:00 /usr/sbin/winbindd
root 2643 1 0 4271 8516 0 22:33 ? 00:00:00 /usr/sbin/apache2 -k start
root 2644 2643 0 438 1236 1 22:33 ? 00:00:00 apache_log
root 2645 2643 0 438 1176 0 22:33 ? 00:00:00 apache_log
root 2646 2643 1 4250 6548 0 22:33 ? 00:00:02 /usr/sbin/apache2 -k start
admin 2647 2643 0 4404 8584 0 22:33 ? 00:00:00 /usr/sbin/apache2 -k start
admin 2648 2643 0 4406 8600 0 22:33 ? 00:00:00 /usr/sbin/apache2 -k start
admin 2649 2643 0 4406 8600 1 22:33 ? 00:00:00 /usr/sbin/apache2 -k start
admin 2650 2643 0 4406 8600 0 22:33 ? 00:00:00 /usr/sbin/apache2 -k start
root 2651 1 8 14294 34308 0 22:33 ? 00:00:14 /usr/sbin/readynasd -v 3 -t
admin 2652 2643 0 4404 8584 1 22:33 ? 00:00:00 /usr/sbin/apache2 -k start
nastool+ 2653 1 1 28893 24012 0 22:33 ? 00:00:02 /apps/nastools-netdata/sbin/netdata -D -P /var/run/nastools-netdata.pid
nastool+ 2656 2653 0 1290 2636 0 22:33 ? 00:00:01 bash /apps/nastools-netdata/lib/arm-linux-gnueabi/netdata/plugins.d/tc-qos-helper.sh 1
root 2666 2653 3 852 2436 0 22:33 ? 00:00:05 /apps/nastools-netdata/lib/arm-linux-gnueabi/netdata/plugins.d/apps.plugin 1
admin 2909 2643 0 4404 8584 0 22:33 ? 00:00:00 /usr/sbin/apache2 -k start
root 2952 2 0 0 0 0 22:33 ? 00:00:00 [kworker/u5:2]
root 2967 2497 0 15748 10068 0 22:33 ? 00:00:00 sshd: root@pts/0
root 3052 2967 0 1407 3024 0 22:33 pts/0 00:00:00 -bash
nut 3181 1 0 1809 2448 0 22:33 ? 00:00:00 /lib/nut/snmp-ups -a UPS
nut 3183 1 0 685 1564 0 22:33 ? 00:00:00 /lib/nut/upsd
root 3196 1 0 628 1684 0 22:33 ? 00:00:00 /lib/nut/upsmon
nut 3197 3196 0 690 1856 0 22:33 ? 00:00:00 /lib/nut/upsmon
root 3203 2 0 0 0 1 22:33 ? 00:00:00 [kworker/u4:9]
root 3204 2 1 0 0 1 22:33 ? 00:00:02 [kworker/u4:10]
admin 3305 2643 0 4404 8588 0 22:33 ? 00:00:00 /usr/sbin/apache2 -k start
root 4215 1 0 463 1108 1 22:35 ? 00:00:00 /bin/sh /frontview/bin/apt-update.sh
root 4223 4215 0 1022 1648 1 22:35 ? 00:00:00 timeout 600 apt-get update
root 4224 4223 26 8471 30032 0 22:35 ? 00:00:10 apt-get update
root 4456 2497 2 15748 10964 0 22:35 ? 00:00:00 sshd: root@pts/1
root 4491 4456 0 1407 3212 1 22:35 pts/1 00:00:00 -bash
root 4525 4491 0 16406 5328 1 22:35 pts/1 00:00:00 journalctl -b
root 4526 4525 0 1012 1768 0 22:35 pts/1 00:00:00 pager
root 4676 3052 0 1290 2224 1 22:35 pts/0 00:00:00 ps -AF

What is going on with this unit?

[Alein]

and journal

as much as I was able to get

Journal as much as i was able to get

ournal as much as i was able to get
 
Apr 03 22:33:09 NAS-A connmand[2468]: eth0 {newlink} ignoring slave, index 2 address 28:C6:8E:35:86:A8
Apr 03 22:33:09 NAS-A connmand[2468]: eth1 {newlink} ignoring slave, index 3 address 28:C6:8E:35:86:A8
Apr 03 22:33:10 NAS-A apache2[2650]: [error] [client 192.168.97.102] Connect rddclient failed, referer: https://172.26.10.10/admin/
Apr 03 22:33:10 NAS-A apache_access[2644]: 192.168.97.102 "POST /dbbroker HTTP/1.1" 200
Apr 03 22:33:11 NAS-A apache2[2652]: [error] [client 172.26.12.230] Connect rddclient failed, referer: http://nas-a/admin/
Apr 03 22:33:11 NAS-A apache_access[2645]: 172.26.12.230 "POST /dbbroker HTTP/1.1" 200
Apr 03 22:33:12 NAS-A apache2[2909]: [error] [client 192.168.97.102] Connect rddclient failed, referer: https://172.26.10.10/admin/
Apr 03 22:33:12 NAS-A apache_access[2644]: 192.168.97.102 "POST /dbbroker HTTP/1.1" 200
Apr 03 22:33:12 NAS-A apache2[2649]: [error] [client 192.168.97.102] Connect rddclient failed, referer: https://172.26.10.10/admin/
Apr 03 22:33:12 NAS-A sshd[2967]: SSH: Server;Ltype: Version;Remote: 172.26.12.230-54719;Protocol: 2.0;Client: RebexSSH_1.0.6054.0
Apr 03 22:33:13 NAS-A sshd[2967]: SSH: Server;Ltype: Kex;Remote: 172.26.12.230-54719;Enc: aes256-ctr;MAC: hmac-sha2-256;Comp: none [preauth]
Apr 03 22:33:13 NAS-A sshd[2967]: SSH: Server;Ltype: Authname;Remote: 172.26.12.230-54719;Name: root [preauth]
Apr 03 22:33:15 NAS-A apache2[2650]: [error] [client 192.168.97.102] Connect rddclient failed, referer: https://172.26.10.10/admin/
Apr 03 22:33:15 NAS-A sshd[2967]: pam_winbind(sshd:auth): getting password (0x00000000)
Apr 03 22:33:15 NAS-A sshd[2967]: pam_winbind(sshd:auth): request wbcLogonUser failed: WBC_ERR_AUTH_ERROR, PAM error: PAM_AUTHINFO_UNAVAIL (9), NTSTATUS: NT_STATUS_NO_LOGO
N_SERVERS, Error message was: No logon servers
Apr 03 22:33:15 NAS-A sshd[2967]: pam_winbind(sshd:auth): internal module error (retval = PAM_AUTHINFO_UNAVAIL(9), user = 'root')
Apr 03 22:33:15 NAS-A apache2[2652]: [error] [client 172.26.12.230] Connect rddclient failed, referer: http://nas-a/admin/
Apr 03 22:33:17 NAS-A apache2[2909]: [error] [client 192.168.97.102] Connect rddclient failed, referer: https://172.26.10.10/admin/
Apr 03 22:33:17 NAS-A apache2[2648]: [error] [client 192.168.97.102] Connect rddclient failed, referer: https://172.26.10.10/admin/
Apr 03 22:33:18 NAS-A apache2[2650]: [error] [client 172.26.12.230] Connect rddclient failed, referer: http://nas-a/admin/
Apr 03 22:33:19 NAS-A apache2[2647]: [error] [client 192.168.97.102] Connect rddclient failed, referer: https://172.26.10.10/admin/
Apr 03 22:33:19 NAS-A apache2[2909]: [error] [client 172.26.12.230] Connect rddclient failed, referer: http://nas-a/admin/
Apr 03 22:33:21 NAS-A sshd[2967]: pam_winbind(sshd:account): valid_user: wbcGetpwnam gave WBC_ERR_DOMAIN_NOT_FOUND
Apr 03 22:33:21 NAS-A sshd[2967]: Accepted password for root from 172.26.12.230 port 54719 ssh2
Apr 03 22:33:21 NAS-A sshd[2967]: pam_unix(sshd:session): session opened for user root by (uid=0)
Apr 03 22:33:21 NAS-A sshd[2967]: SSH: Server;Ltype: Kex;Remote: 172.26.12.230-54719;Enc: aes256-ctr;MAC: hmac-sha2-256;Comp: none
Apr 03 22:33:21 NAS-A apache2[2648]: [error] [client 192.168.97.102] Connect rddclient failed, referer: https://172.26.10.10/admin/
Apr 03 22:33:21 NAS-A apache2[2652]: [error] [client 192.168.97.102] Connect rddclient failed, referer: https://172.26.10.10/admin/
Apr 03 22:33:22 NAS-A apache2[2647]: [error] [client 172.26.12.230] Connect rddclient failed, referer: http://nas-a/admin/
Apr 03 22:33:22 NAS-A apache2[2649]: [error] [client 192.168.97.102] Connect rddclient failed, referer: https://172.26.10.10/admin/
Apr 03 22:33:24 NAS-A apache2[2648]: [error] [client 192.168.97.102] Connect rddclient failed, referer: https://172.26.10.10/admin/
Apr 03 22:33:25 NAS-A systemd[1]: Reloading.
Apr 03 22:33:25 NAS-A apache2[2652]: [error] [client 172.26.12.230] Connect rddclient failed, referer: http://nas-a/admin/
Apr 03 22:33:26 NAS-A apache2[2909]: [error] [client 192.168.97.102] Connect rddclient failed, referer: https://172.26.10.10/admin/
Apr 03 22:33:26 NAS-A systemd[1]: Reloading.
Apr 03 22:33:28 NAS-A apache2[2650]: [error] [client 192.168.97.102] Connect rddclient failed, referer: https://172.26.10.10/admin/
Apr 03 22:33:28 NAS-A systemd[1]: Starting Network UPS Tools - power device driver controller...
Apr 03 22:33:28 NAS-A apache2[2652]: [error] [client 192.168.97.102] Connect rddclient failed, referer: https://172.26.10.10/admin/
Apr 03 22:33:28 NAS-A upsdrvctl[3159]: MIB search path: $HOME/.snmp/mibs:/usr/share/snmp/mibs:/usr/share/snmp/mibs/iana:/usr/share/snmp/mibs/ietf:/usr/share/mibs/site:/usr/share/s
nmp/mibs:/usr/share/mibs/iana:/usr/share/mibs/ietf:/usr/share/mibs/netsnmp
Apr 03 22:33:28 NAS-A upsdrvctl[3159]: Cannot find module (UCD-DLMOD-MIB): At line 1 in (none)
Apr 03 22:33:28 NAS-A upsdrvctl[3159]: Cannot find module (MTA-MIB): At line 1 in (none)
Apr 03 22:33:28 NAS-A upsdrvctl[3159]: Cannot find module (NETWORK-SERVICES-MIB): At line 1 in (none)
Apr 03 22:33:28 NAS-A upsdrvctl[3159]: Cannot find module (UCD-DISKIO-MIB): At line 1 in (none)
Apr 03 22:33:28 NAS-A upsdrvctl[3159]: Cannot find module (LM-SENSORS-MIB): At line 1 in (none)
Apr 03 22:33:28 NAS-A upsdrvctl[3159]: Cannot find module (HOST-RESOURCES-MIB): At line 1 in (none)
Apr 03 22:33:28 NAS-A upsdrvctl[3159]: Cannot find module (HOST-RESOURCES-TYPES): At line 1 in (none)
Apr 03 22:33:28 NAS-A upsdrvctl[3159]: Cannot find module (SNMPv2-MIB): At line 1 in (none)
Apr 03 22:33:28 NAS-A upsdrvctl[3159]: Cannot find module (IF-MIB): At line 1 in (none)
Apr 03 22:33:28 NAS-A upsdrvctl[3159]: Cannot find module (IP-MIB): At line 1 in (none)
Apr 03 22:33:28 NAS-A upsdrvctl[3159]: Cannot find module (TCP-MIB): At line 1 in (none)
Apr 03 22:33:28 NAS-A upsdrvctl[3159]: Cannot find module (UDP-MIB): At line 1 in (none)
Apr 03 22:33:28 NAS-A upsdrvctl[3159]: Cannot find module (NOTIFICATION-LOG-MIB): At line 1 in (none)
Apr 03 22:33:28 NAS-A upsdrvctl[3159]: Cannot find module (DISMAN-EVENT-MIB): At line 1 in (none)
Apr 03 22:33:28 NAS-A upsdrvctl[3159]: Cannot find module (DISMAN-SCHEDULE-MIB): At line 1 in (none)
Apr 03 22:33:28 NAS-A upsdrvctl[3159]: Cannot find module (UCD-SNMP-MIB): At line 1 in (none)
Apr 03 22:33:28 NAS-A upsdrvctl[3159]: Cannot find module (UCD-DEMO-MIB): At line 1 in (none)
Apr 03 22:33:28 NAS-A upsdrvctl[3159]: Cannot find module (SNMP-TARGET-MIB): At line 1 in (none)
Apr 03 22:33:28 NAS-A upsdrvctl[3159]: Cannot find module (NET-SNMP-AGENT-MIB): At line 1 in (none)
Apr 03 22:33:28 NAS-A upsdrvctl[3159]: Cannot find module (SNMP-MPD-MIB): At line 1 in (none)
Apr 03 22:33:28 NAS-A upsdrvctl[3159]: Cannot find module (SNMP-USER-BASED-SM-MIB): At line 1 in (none)
Apr 03 22:33:28 NAS-A upsdrvctl[3159]: Cannot find module (SNMP-FRAMEWORK-MIB): At line 1 in (none)
Apr 03 22:33:28 NAS-A upsdrvctl[3159]: Cannot find module (SNMP-VIEW-BASED-ACM-MIB): At line 1 in (none)
Apr 03 22:33:28 NAS-A upsdrvctl[3159]: Cannot find module (SNMP-COMMUNITY-MIB): At line 1 in (none)
Apr 03 22:33:28 NAS-A upsdrvctl[3159]: Cannot find module (IPV6-ICMP-MIB): At line 1 in (none)
Apr 03 22:33:28 NAS-A upsdrvctl[3159]: Cannot find module (IPV6-MIB): At line 1 in (none)
Apr 03 22:33:28 NAS-A upsdrvctl[3159]: Cannot find module (IPV6-TCP-MIB): At line 1 in (none)
Apr 03 22:33:28 NAS-A upsdrvctl[3159]: Cannot find module (IPV6-UDP-MIB): At line 1 in (none)
Apr 03 22:33:28 NAS-A upsdrvctl[3159]: Cannot find module (IP-FORWARD-MIB): At line 1 in (none)
Apr 03 22:33:28 NAS-A upsdrvctl[3159]: Cannot find module (NET-SNMP-PASS-MIB): At line 1 in (none)
Apr 03 22:33:28 NAS-A upsdrvctl[3159]: Cannot find module (NET-SNMP-EXTEND-MIB): At line 1 in (none)
Apr 03 22:33:28 NAS-A upsdrvctl[3159]: Cannot find module (SNMP-NOTIFICATION-MIB): At line 1 in (none)
Apr 03 22:33:28 NAS-A upsdrvctl[3159]: Cannot find module (SNMPv2-TM): At line 1 in (none)
Apr 03 22:33:28 NAS-A upsdrvctl[3159]: Cannot find module (NET-SNMP-VACM-MIB): At line 1 in (none)
Apr 03 22:33:28 NAS-A upsdrvctl[3159]: Detected Smart-UPS 750 RM on host 172.26.10.4 (mib: apcc 1.2)
Apr 03 22:33:28 NAS-A upsdrvctl[3159]: [UPS] Warning: excessive poll failures, limiting error reporting (OID = .1.3.6.1.4.1.318.1.1.1.9.2.3.1.5.1.1.3)
Apr 03 22:33:29 NAS-A upsdrvctl[3159]: [UPS] Warning: excessive poll failures, limiting error reporting (OID = .1.3.6.1.4.1.318.1.1.1.9.3.3.1.6.1.1.1)
Apr 03 22:33:29 NAS-A apache2[2647]: [error] [client 172.26.12.230] Connect rddclient failed, referer: http://nas-a/admin/
Apr 03 22:33:30 NAS-A upsdrvctl[3159]: Network UPS Tools - UPS driver controller 2.7.4
Apr 03 22:33:30 NAS-A systemd[1]: Started Network UPS Tools - power device driver controller.
Apr 03 22:33:30 NAS-A snmp-ups[3181]: Startup successful
Apr 03 22:33:30 NAS-A systemd[1]: Starting Network UPS Tools - power devices information server...
Apr 03 22:33:30 NAS-A upsd[3182]: listening on ::1 port 3493
Apr 03 22:33:30 NAS-A upsd[3182]: listening on 127.0.0.1 port 3493
Apr 03 22:33:30 NAS-A upsd[3182]: Connected to UPS [UPS]: snmp-ups-UPS
Apr 03 22:33:30 NAS-A systemd[1]: Started Network UPS Tools - power devices information server.
Apr 03 22:33:30 NAS-A upsd[3183]: Startup successful

[Alein]

Apr 03 22:33:30 NAS-A apache2[2649]: [error] [client 192.168.97.102] Connect rddclient failed, referer: https://172.26.10.10/admin/
Apr 03 22:33:31 NAS-A systemd[1]: Starting Network UPS Tools - power device monitor and shutdown controller...
Apr 03 22:33:31 NAS-A upsmon[3195]: UPS: UPS@localhost (master) (power value 1)
Apr 03 22:33:31 NAS-A systemd[1]: nut-monitor.service: PID file /var/run/nut/upsmon.pid not readable (yet?) after start: No such file or directory
Apr 03 22:33:31 NAS-A upsmon[3196]: Startup successful
Apr 03 22:33:31 NAS-A systemd[1]: nut-monitor.service: Supervising process 3197 which is not our child. We'll most likely not notice when it exits.
Apr 03 22:33:31 NAS-A systemd[1]: Started Network UPS Tools - power device monitor and shutdown controller.
Apr 03 22:33:31 NAS-A upsd[3183]: User monuser@::1 logged into UPS [UPS]
Apr 03 22:33:32 NAS-A nmbd[2509]: [2017/04/03 22:33:32.025874, 0] ../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2)
Apr 03 22:33:32 NAS-A nmbd[2509]: ***** Samba name server NAS-A is now a local master browser for workgroup DARK-FLOW on subnet 172.26.10.10 *****
Apr 03 22:33:32 NAS-A apache2[2648]: [error] [client 192.168.97.102] Connect rddclient failed, referer: https://172.26.10.10/admin/
Apr 03 22:33:33 NAS-A apache2[2647]: [error] [client 192.168.97.102] Connect rddclient failed, referer: https://172.26.10.10/admin/
Apr 03 22:33:33 NAS-A apache2[2909]: [error] [client 172.26.12.230] Connect rddclient failed, referer: http://nas-a/admin/
Apr 03 22:33:35 NAS-A apache2[2650]: [error] [client 192.168.97.102] Connect rddclient failed, referer: https://172.26.10.10/admin/
Apr 03 22:33:37 NAS-A apache2[2652]: [error] [client 192.168.97.102] Connect rddclient failed, referer: https://172.26.10.10/admin/
Apr 03 22:33:37 NAS-A apache2[2647]: [error] [client 172.26.12.230] Connect rddclient failed, referer: http://nas-a/admin/
Apr 03 22:33:38 NAS-A apache2[2649]: [error] [client 192.168.97.102] Connect rddclient failed, referer: https://172.26.10.10/admin/
Apr 03 22:33:39 NAS-A apache2[2648]: [error] [client 172.26.12.230] Connect rddclient failed, referer: http://nas-a/admin/
Apr 03 22:33:39 NAS-A apache2[2652]: [error] [client 192.168.97.102] Connect rddclient failed, referer: https://172.26.10.10/admin/
Apr 03 22:33:40 NAS-A apache2[2647]: [error] [client 172.26.12.230] Connect rddclient failed, referer: http://nas-a/admin/
Apr 03 22:33:42 NAS-A apache2[2648]: [error] [client 192.168.97.102] Connect rddclient failed, referer: https://172.26.10.10/admin/
Apr 03 22:33:42 NAS-A apache2[2650]: [error] [client 192.168.97.102] Connect rddclient failed, referer: https://172.26.10.10/admin/
Apr 03 22:33:43 NAS-A apache2[2647]: [error] [client 192.168.97.102] Connect rddclient failed, referer: https://172.26.10.10/admin/
Apr 03 22:33:44 NAS-A apache2[2649]: [error] [client 192.168.97.102] Connect rddclient failed, referer: https://172.26.10.10/admin/
Apr 03 22:33:44 NAS-A apache2[2650]: [error] [client 172.26.12.230] Connect rddclient failed, referer: http://nas-a/admin/
Apr 03 22:33:44 NAS-A apache2[2648]: [error] [client 192.168.97.102] Connect rddclient failed, referer: https://172.26.10.10/admin/
Apr 03 22:33:46 NAS-A apache2[2647]: [error] [client 192.168.97.102] Connect rddclient failed, referer: https://172.26.10.10/admin/
Apr 03 22:33:48 NAS-A apache2[3305]: [error] [client 172.26.12.230] Connect rddclient failed, referer: http://nas-a/admin/
Apr 03 22:33:49 NAS-A apache2[2909]: [error] [client 192.168.97.102] Connect rddclient failed, referer: https://172.26.10.10/admin/
Apr 03 22:33:49 NAS-A apache2[2648]: [error] [client 192.168.97.102] Connect rddclient failed, referer: https://172.26.10.10/admin/
Apr 03 22:33:51 NAS-A apache2[2647]: [error] [client 192.168.97.102] Connect rddclient failed, referer: https://172.26.10.10/admin/
Apr 03 22:33:52 NAS-A apache2[3305]: [error] [client 172.26.12.230] Connect rddclient failed, referer: http://nas-a/admin/
Apr 03 22:33:53 NAS-A apache2[2650]: [error] [client 192.168.97.102] Connect rddclient failed, referer: https://172.26.10.10/admin/
Apr 03 22:33:54 NAS-A apache2[2648]: [error] [client 192.168.97.102] Connect rddclient failed, referer: https://172.26.10.10/admin/
Apr 03 22:33:56 NAS-A apache2[2647]: [error] [client 192.168.97.102] Connect rddclient failed, referer: https://172.26.10.10/admin/
Apr 03 22:33:56 NAS-A apache2[3305]: [error] [client 172.26.12.230] Connect rddclient failed, referer: http://nas-a/admin/
Apr 03 22:33:56 NAS-A apache2[2649]: [error] [client 172.26.12.230] Connect rddclient failed, referer: http://nas-a/admin/
Apr 03 22:33:58 NAS-A apache2[2909]: [error] [client 192.168.97.102] Connect rddclient failed, referer: https://172.26.10.10/admin/
Apr 03 22:33:59 NAS-A apache2[2652]: [error] [client 192.168.97.102] Connect rddclient failed, referer: https://172.26.10.10/admin/
Apr 03 22:34:00 NAS-A apache2[3305]: [error] [client 192.168.97.102] Connect rddclient failed, referer: https://172.26.10.10/admin/
Apr 03 22:34:00 NAS-A apache2[2649]: [error] [client 172.26.12.230] Connect rddclient failed, referer: http://nas-a/admin/
Apr 03 22:34:01 NAS-A apache2[2650]: [error] [client 172.26.12.230] Connect rddclient failed, referer: http://nas-a/admin/
Apr 03 22:34:02 NAS-A apache2[2648]: [error] [client 192.168.97.102] Connect rddclient failed, referer: https://172.26.10.10/admin/
Apr 03 22:34:02 NAS-A apache2[2647]: [error] [client 192.168.97.102] Connect rddclient failed, referer: https://172.26.10.10/admin/
Apr 03 22:34:04 NAS-A apache2[3305]: [error] [client 172.26.12.230] Connect rddclient failed, referer: http://nas-a/admin/
Apr 03 22:34:04 NAS-A apache2[2650]: [error] [client 192.168.97.102] Connect rddclient failed, referer: https://172.26.10.10/admin/
Apr 03 22:34:05 NAS-A apache2[2648]: [error] [client 192.168.97.102] Connect rddclient failed, referer: https://172.26.10.10/admin/
Apr 03 22:34:07 NAS-A apache2[2647]: [error] [client 192.168.97.102] Connect rddclient failed, referer: https://172.26.10.10/admin/
Apr 03 22:34:07 NAS-A apache2[3305]: [error] [client 172.26.12.230] Connect rddclient failed, referer: http://nas-a/admin/
Apr 03 22:34:09 NAS-A apache2[2650]: [error] [client 192.168.97.102] Connect rddclient failed, referer: https://172.26.10.10/admin/
Apr 03 22:34:10 NAS-A apache2[2648]: [error] [client 192.168.97.102] Connect rddclient failed, referer: https://172.26.10.10/admin/
Apr 03 22:34:11 NAS-A apache2[2647]: [error] [client 172.26.12.230] Connect rddclient failed, referer: http://nas-a/admin/
Apr 03 22:34:12 NAS-A apache2[3305]: [error] [client 192.168.97.102] Connect rddclient failed, referer: https://172.26.10.10/admin/
Apr 03 22:34:14 NAS-A apache2[2650]: [error] [client 192.168.97.102] Connect rddclient failed, referer: https://172.26.10.10/admin/
Apr 03 22:34:15 NAS-A apache2[2648]: [error] [client 192.168.97.102] Connect rddclient failed, referer: https://172.26.10.10/admin/
Apr 03 22:34:15 NAS-A apache2[2652]: [error] [client 172.26.12.230] Connect rddclient failed, referer: http://nas-a/admin/
Apr 03 22:34:16 NAS-A apache2[3305]: [error] [client 192.168.97.102] Connect rddclient failed, referer: https://172.26.10.10/admin/
Apr 03 22:34:18 NAS-A apache2[2649]: [error] [client 172.26.12.230] Connect rddclient failed, referer: http://nas-a/admin/
Apr 03 22:34:18 NAS-A apache2[2909]: [error] [client 192.168.97.102] Connect rddclient failed, referer: https://172.26.10.10/admin/
Apr 03 22:34:20 NAS-A apache2[2652]: [error] [client 192.168.97.102] Connect rddclient failed, referer: https://172.26.10.10/admin/
Apr 03 22:34:21 NAS-A apache2[3305]: [error] [client 192.168.97.102] Connect rddclient failed, referer: https://172.26.10.10/admin/
Apr 03 22:34:22 NAS-A apache2[2650]: [error] [client 192.168.97.102] Connect rddclient failed, referer: https://172.26.10.10/admin/
Apr 03 22:34:22 NAS-A apache2[2648]: [error] [client 172.26.12.230] Connect rddclient failed, referer: http://nas-a/admin/
Apr 03 22:34:22 NAS-A apache2[2909]: [error] [client 172.26.12.230] Connect rddclient failed, referer: http://nas-a/admin/
Apr 03 22:34:23 NAS-A apache2[2647]: [error] [client 192.168.97.102] Connect rddclient failed, referer: https://172.26.10.10/admin/
Apr 03 22:34:25 NAS-A apache2[2649]: [error] [client 172.26.12.230] Connect rddclient failed, referer: http://nas-a/admin/
Apr 03 22:34:25 NAS-A apache2[2650]: [error] [client 192.168.97.102] Connect rddclient failed, referer: https://172.26.10.10/admin/
Apr 03 22:34:26 NAS-A apache2[2909]: [error] [client 192.168.97.102] Connect rddclient failed, referer: https://172.26.10.10/admin/
Apr 03 22:34:27 NAS-A apache2[2647]: [error] [client 192.168.97.102] Connect rddclient failed, referer: https://172.26.10.10/admin/
Apr 03 22:34:28 NAS-A apache2[3305]: [error] [client 172.26.12.230] Connect rddclient failed, referer: http://nas-a/admin/
Apr 03 22:34:30 NAS-A apache2[2650]: [error] [client 192.168.97.102] Connect rddclient failed, referer: https://172.26.10.10/admin/
Apr 03 22:34:31 NAS-A apache2[2909]: [error] [client 192.168.97.102] Connect rddclient failed, referer: https://172.26.10.10/admin/
Apr 03 22:34:32 NAS-A apache2[2647]: [error] [client 192.168.97.102] Connect rddclient failed, referer: https://172.26.10.10/admin/

[StephenB]

You likely will need support's help on this.

If you have a backup (or are willing to take the risk) you could try doing an OS reinstall.

You could also try booting the NAS as read-only (a long shot, but certainly will do no harm).

[Alein]

 I can not take the risk there is more than 8TB of data. 

Problem is , that I am 200km from NAS and even on site I have limited time. I was thinking about disconnect nas from AD, but I need some help with command lines, there is no realm. I think that something could happens with time change. One on my NAS freeze, but after reboot is working fine. 

[StephenB]

BTW, did you check for a full OS partition?

[mdgm-ntgr]

I can't see a support case for this. Have you sought help from support?

If the problem was say with/on the disks then moving the disks to another chassis is not going to resolve the problem.

[Alein]

There is still a lot of space

root@NAS-A:~# df -h
Filesystem Size Used Avail Use% Mounted on
udev 10M 4.0K 10M 1% /dev
/dev/md0 4.0G 659M 3.0G 18% /
tmpfs 1009M 0 1009M 0% /dev/shm
tmpfs 1009M 424K 1009M 1% /run
tmpfs 505M 716K 504M 1% /run/lock
tmpfs 1009M 0 1009M 0% /sys/fs/cgroup
/dev/md127 11T 8.9T 2.1T 81% /data
/dev/md127 11T 8.9T 2.1T 81% /apps
/dev/md127 11T 8.9T 2.1T 81% /home

[Alein]

I can only request hardware replace

Based on your serial number and purchase date, NETGEAR can offer you the following support options:

Complimentary

Ask our community

Search our knowledge base

Paid

Call us

Your complimentary 90 day technical support expired on Sep 18, 2016.
You can purchase a paid support subscription to extend your coverage.

Hardware Replacement

Your product is covered under hardware warranty until Jun 19, 2021.
To request warranty replacement, call us.

BACK

But I am not sure if this is hardware, more likely OS/firmware, or it is all hardware issue?

[mdgm-ntgr]

It doesn't look like hardware to me. It looks like some troubleshooting is needed to determine what the cause is.

Are you able to boot to volume read-only mode, download your logs and send those in (see the Sending Logs link in my sig)?

So you moved your disks from an old RN2120 to a new one or did you do something else?

[Alein]

HI,

I did not move any drives. I am 200km from NAS.  Today I am going to take two NAS 2120 and 2100(to make a copy of data if possible)

I have no idea if it will boot in RO. Will see.

[Alein]

 I was able to boot in RO mode. NAS is working, 

I send logs as you requested. Topic of the mail is this same like this one on the forum "ReadyNAS 2120 is working only for 4min"

It seems that something wrong is with write.

[mdgm-ntgr]

You could update to ReadyNAS OS 6.7.0 which is now available and if it still won't come up then try an OS Re-install.

An OS Re-install on 6.7.0 will disable quotas at the volume level. This may help.

[Alein]

Hi,

I made OS upgrade. No difference with 6.7

I send you new logs.

Please confirm that reinstallation of OS will not harm my data. I wil try to make a copy as much as possible(it will takes days), but I am not able to get 9TB of free space.

[StephenB]

---

@Alein wrote:

Please confirm that reinstallation of OS will not harm my data. 

---

An OS reinstall will reset the NAS admin password to password and reset the network interface configuration to use DHCP.  It also reinstalls selected OS files to the OS partition.  It shouldn't change any other settings or destroy data.

You might look into setting up a backup plan for the NAS after you get past this problem - though it seems expensive, data recovery is more expensive (and often won't recover everything).

[mdgm-ntgr]

The OS Re-install on 6.7.0 will disable quotas at the volume level. From looking at your logs I think this will help.

[Alein]

Good news. OS reinstall solve the problem but

by default there is no quota on data share, as a result I do not see size of snapshots etc. I turn it on, but my question is, is there a bug in quota configuration is it safe to use quota on OS 6.7 ?

[jak0lantash]

BTRFS quota accounting can be quite heavy. I wouldn't advise to enable quota at the volume level on an ARM unit (unless drastic optimization on 6.7.0).
Don't rely on df -h with BTRFS, I'd recommend using: btrfs filesystem usage <mount_point> ("btrfs fi us /data").

[Alein]

There is a bug in 6.7.0 turning on quota everytime I made a change in share.

I lost connection to two NAS because of this.

So please fix it.

The second problem is with UPS monitoring. I have scheduled runtime callibration , and NAS turned off on critical level. But it was calibration 😞

APC SNMP

So as for now, There  is qouta but I can not use it, there are LUNs , but I can not use them, UPS monitoring exist , but better do not use it,so what else I should not use ;/

[jak0lantash]

---

@Alein wrote:

There is a bug in 6.7.0 turning on quota everytime I made a change in share.

That wasn't introduced in 6.7.0, it was already the behavior before.

The issue really is that 6.7.0 introduces an option to disable the quotas, without changing that behavior. I  presume this will changed in 6.7.1.

[StephenB]

---

@jak0lantash wrote:

---

 I  presume this will changed in 6.7.1.

---

Per the release notes, it is fixed in 6.7.1 beta 1.

[Alein]

Can you send me 6.7 and 6.7.1 firmware ? Links are not working anymore, I have more NAS waiting for this firmware ASAP.

[StephenB]

---

@Alein wrote:

Can you send me 6.7 and 6.7.1 firmware ? Links are not working anymore, I have more NAS waiting for this firmware ASAP.

---

6.7.0 was withdrawn.

6.7.1 links work - see https://community.netgear.com/t5/ReadyNAS-Beta-Release/ReadyNASOS-6-7-1-T244-Beta-1/m-p/1266584#U126...