Hello,I seem to be suffering from a problem that I don't see others mentioning when using 4.2.21. I own a recently RMAed Pioneer Pro 6 bay Readynas. My old Pioneer would lock up several times a day (I figured this was due to a bad CPU fan) but now my new one is doing the same thing!Problem:Several times a day, the NAS stops responding. The LED panel does not print the IP or other data when you press the button. Frontview does not respond to a web browser. My Mac Mini cannot connect to any of the folders.Environment:I am using all 6 bays of the Pioneer Pro. As mentioned above, I technically have two of them in my house right now and both suffer from the same problem. I did not have this problem when I was using 4.2.19. My only used Addon's are PLEX MEDIA SERVER (v0.9.6.3.143-4466fb5) , and DnsOMatic (Which I just disabled since I didn't notice it was on before).What I've tried:A new Pioneer Pro Readynas!Reinstalling 4.2.21 over the top of the current installRemoving all the addons except Plex (I really want to use Plex and their forums don't speak of this issue)Additional References:This guy had the same problem I have but on an earlier beta release: viewtopic.php?f=51&t=60222 :cry: :cry: :cry:

(1) Did you set the system to spin down the hard drives, or are they always on?(2) Have you checked the SMART+ stats for each disk?

I would open a new tech support ticket and refer it to the previous.

PapaBear,I've taken your advice and opened a ticket with NETGEAR (18988091). I've also updated the above posts to be a bit more accurate. Do you guys think of anything else?

Pioneer Pro stops responding (4.2.21) #18988091

23 Replies

Replies have been turned off for this discussion

StephenB
Guru - Experienced User
Jul 15, 2012
(1) Did you set the system to spin down the hard drives, or are they always on?

(2) Have you checked the SMART+ stats for each disk?

Pezman

Aspirant

Jul 15, 2012

Answers:
1) I don't utilize the disc spindown feature in the Frontpage Control Panel. Should I be?
2) The frontview page says they are all ok. Here is the more detailed version (look at drive 5):

Model:	WDC WD20EARX-00PASB0
Serial:	WD-WCAZA8361760
Firmware:	51.0AB51
SMART Attribute
Raw Read Error Rate	2
Spin Up Time	5500
Start Stop Count	89
Reallocated Sector Count	0
Seek Error Rate	0
Power On Hours	2830
Spin Retry Count	0
Calibration Retry Count	0
Power Cycle Count	87
Power-Off Retract Count	50
Load Cycle Count	191487
Temperature Celsius	38
Reallocated Event Count	0
Current Pending Sector	0
Offline Uncorrectable	0
UDMA CRC Error Count	0
Multi Zone Error Rate	0
ATA Error Count	0

Model:	WDC WD20EARX-00PASB0
Serial:	WD-WCAZA8418089
Firmware:	51.0AB51
SMART Attribute
Raw Read Error Rate	0
Spin Up Time	5300
Start Stop Count	79
Reallocated Sector Count	0
Seek Error Rate	0
Power On Hours	2789
Spin Retry Count	0
Calibration Retry Count	0
Power Cycle Count	78
Power-Off Retract Count	43
Load Cycle Count	197759
Temperature Celsius	39
Reallocated Event Count	0
Current Pending Sector	0
Offline Uncorrectable	0
UDMA CRC Error Count	0
Multi Zone Error Rate	0
ATA Error Count	0

Model:	WDC WD10EADS-65L5B1
Serial:	WD-WCAU4A865532
Firmware:	01.01A01
SMART Attribute
Raw Read Error Rate	0
Spin Up Time	5716
Start Stop Count	175
Reallocated Sector Count	0
Seek Error Rate	0
Power On Hours	24145
Spin Retry Count	0
Calibration Retry Count	0
Power Cycle Count	173
Power-Off Retract Count	12
Load Cycle Count	175
Temperature Celsius	40
Reallocated Event Count	0
Current Pending Sector	0
Offline Uncorrectable	0
UDMA CRC Error Count	0
Multi Zone Error Rate	0
ATA Error Count	0

Model:	WDC WD10EADS-65L5B1
Serial:	WD-WCAU4A877128
Firmware:	01.01A01
SMART Attribute
Raw Read Error Rate	0
Spin Up Time	5716
Start Stop Count	175
Reallocated Sector Count	0
Seek Error Rate	0
Power On Hours	24146
Spin Retry Count	0
Calibration Retry Count	0
Power Cycle Count	173
Power-Off Retract Count	12
Load Cycle Count	175
Temperature Celsius	40
Reallocated Event Count	0
Current Pending Sector	0
Offline Uncorrectable	0
UDMA CRC Error Count	0
Multi Zone Error Rate	0
ATA Error Count	0

This Hard Drive is complaining about stuff. Is there something I should do to resolve?


Model:	WDC WD20EARS-00MVWB0
Serial:	WD-WMAZ20047276
Firmware:	50.0AB50
SMART Attribute
Raw Read Error Rate	0
Spin Up Time	5475
Start Stop Count	154
Reallocated Sector Count	0
Seek Error Rate	0
Power On Hours	15043
Spin Retry Count	0
Calibration Retry Count	0
Power Cycle Count	152
Power-Off Retract Count	51
Load Cycle Count	1236411
Temperature Celsius	41
Reallocated Event Count	0
Current Pending Sector	7
Offline Uncorrectable	4
UDMA CRC Error Count	0
Multi Zone Error Rate	13
ATA Error Count	0


Model:	WDC WD20EARS-00MVWB0
Serial:	WD-WMAZ20444481
Firmware:	50.0AB50
SMART Attribute
Raw Read Error Rate	0
Spin Up Time	5575
Start Stop Count	154
Reallocated Sector Count	0
Seek Error Rate	0
Power On Hours	15038
Spin Retry Count	0
Calibration Retry Count	0
Power Cycle Count	152
Power-Off Retract Count	51
Load Cycle Count	1232261
Temperature Celsius	39
Reallocated Event Count	0
Current Pending Sector	0
Offline Uncorrectable	0
UDMA CRC Error Count	0
Multi Zone Error Rate	0
ATA Error Count	0

Pezman

Aspirant

Jul 15, 2012

I'm not sure what my next step should be. I keep browsing the forums for more details and in the meantime I downloaded all my logs (via frontview) and spent some time looking over system.log. I'm a total noob and have no idea what I'm looking for, other than I can copy and paste what looks like information right before it "dies" and when I reboot. Here are the two most recent examples:

Jul 15 00:18:51 Readynas kernel: EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: acl,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv1
Jul 15 00:18:52 Readynas exportfs[2411]: /etc/exports [1]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/backup".   Assuming default behaviour ('no_subtree_check').   NOTE: this default has changed since nfs-utils version 1.0.x 
Jul 15 00:18:52 Readynas exportfs[2411]: /proc/fs/nfs/exports:1: unknown keyword "test-client-(rw" 
Jul 15 00:18:52 Readynas rpc.statd[2416]: Version 1.1.2 Starting
Jul 15 00:18:52 Readynas sm-notify[2435]: sm-notify running as root. chown /var/lib/nfs/sm to choose different user 
Jul 15 00:18:52 Readynas Backgrounding to notify hosts... 
Jul 15 00:18:52 Readynas rpc.statd[2416]: statd running as root. chown /var/lib/nfs/sm to choose different user 
Jul 15 00:18:52 Readynas kernel: svc: failed to register lockdv1 RPC service (errno 97).
Jul 15 00:18:52 Readynas kernel: NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
Jul 15 00:18:52 Readynas kernel: NFSD: starting 90-second grace period
Jul 15 00:18:53 Readynas kernel: warning: `proftpd' uses 32-bit capabilities (legacy support in use)
Jul 15 00:18:54 Readynas kernel: bonding: bond0: setting mode to balance-rr (0).
Jul 15 00:18:54 Readynas kernel: bonding: bond0: Setting MII monitoring interval to 100.
Jul 15 00:18:54 Readynas kernel: ADDRCONF(NETDEV_UP): bond0: link is not ready
Jul 15 00:18:54 Readynas kernel: 8021q: adding VLAN 0 to HW filter on device bond0
Jul 15 00:18:56 Readynas ifplugd(bond0)[2722]: ifplugd 0.28 initializing.
Jul 15 00:18:56 Readynas ifplugd(bond0)[2722]: Using interface bond0/00:00:00:00:00:00 with driver <bonding> (version: 3.7.0)
Jul 15 00:18:56 Readynas ifplugd(bond0)[2722]: Using detection mode: SIOCETHTOOL
Jul 15 00:18:56 Readynas ifplugd(bond0)[2722]: Initialization complete, link beat not detected.
Jul 15 00:18:59 Readynas ifplugd(eth0)[2909]: ifplugd 0.28 initializing.
Jul 15 00:18:59 Readynas ifplugd(eth0)[2909]: Using interface eth0/00:1F:33:EA:62:73 with driver <sk98lin> (version: 10.70.1.3 (01))
Jul 15 00:18:59 Readynas ifplugd(eth0)[2909]: Using detection mode: SIOCETHTOOL
Jul 15 00:18:59 Readynas ifplugd(eth0)[2909]: Initialization complete, link beat detected.
Jul 15 00:19:00 Readynas ifplugd(eth0)[2909]: Executing '/etc/ifplugd/ifplugd.action eth0 up'.
Jul 15 00:19:00 Readynas ifplugd(eth0)[2909]: client: 2917: old priority 0, new priority 0
Jul 15 00:19:00 Readynas ifplugd(eth0)[2909]: client: SIOCADDRT: File exists
Jul 15 00:19:22 Readynas syslogd 1.4.1#18: restart.
Jul 15 00:19:39 Readynas ifplugd(eth0)[2909]: client: Starting plexserver
Jul 15 00:19:45 Readynas ifplugd(eth0)[2909]: Program executed successfully.
Jul 15 00:19:46 Readynas ifplugd(eth1)[3279]: ifplugd 0.28 initializing.
Jul 15 00:19:46 Readynas ifplugd(eth1)[3279]: Using interface eth1/00:1F:33:EA:62:72 with driver <sk98lin> (version: 10.70.1.3 (01))
Jul 15 00:19:46 Readynas ifplugd(eth1)[3279]: Using detection mode: SIOCETHTOOL
Jul 15 00:19:46 Readynas ifplugd(eth1)[3279]: Initialization complete, link beat not detected.
Jul 15 00:20:24 Readynas chronyd[2993]: Invalid host/IP address at line 1
Jul 15 00:20:25 Readynas RAIDiator: System is up.
Jul 15 00:20:31 Readynas kernel: sk98lin 0000:01:00.0: PME# enabled
Jul 15 00:20:31 Readynas kernel: sk98lin 0000:02:00.0: PME# enabled
Jul 15 00:20:34 Readynas avahi-daemon[3958]: Found user 'avahi' (UID 20) and group 'avahi' (GID 20).
Jul 15 00:20:34 Readynas avahi-daemon[3958]: Successfully dropped root privileges.
Jul 15 00:20:34 Readynas avahi-daemon[3958]: avahi-daemon 0.6.23 starting up.
Jul 15 00:20:34 Readynas avahi-daemon[3958]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
Jul 15 00:20:34 Readynas avahi-daemon[3958]: Loading service file /etc/avahi/services/afp.service.
Jul 15 00:20:34 Readynas avahi-daemon[3958]: Loading service file /etc/avahi/services/cifs.service.
Jul 15 00:20:34 Readynas avahi-daemon[3958]: Loading service file /etc/avahi/services/frontview.service.
Jul 15 00:20:34 Readynas avahi-daemon[3958]: Loading service file /etc/avahi/services/mt-daapd.service.
Jul 15 00:20:34 Readynas avahi-daemon[3958]: Loading service file /etc/avahi/services/readynas.service.
Jul 15 00:20:34 Readynas avahi-daemon[3958]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::21f:33ff:feea:6273.
Jul 15 00:20:34 Readynas avahi-daemon[3958]: New relevant interface eth0.IPv6 for mDNS.
Jul 15 00:20:34 Readynas avahi-daemon[3958]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.2.120.
Jul 15 00:20:34 Readynas avahi-daemon[3958]: New relevant interface eth0.IPv4 for mDNS.
Jul 15 00:20:34 Readynas avahi-daemon[3958]: Network interface enumeration completed.
Jul 15 00:20:34 Readynas avahi-daemon[3958]: Registering new address record for fe80::21f:33ff:feea:6273 on eth0.*.
Jul 15 00:20:34 Readynas avahi-daemon[3958]: Registering new address record for 192.168.2.120 on eth0.IPv4.
Jul 15 00:20:34 Readynas avahi-daemon[3958]: Registering HINFO record with values 'X86_64'/'LINUX'.
Jul 15 00:20:35 Readynas avahi-daemon[3958]: Server startup complete. Host name is Readynas.local. Local service cookie is 3825488552.
Jul 15 00:20:36 Readynas avahi-daemon[3958]: Service "ReadyNAS Discovery [Readynas]" (/etc/avahi/services/readynas.service) successfully established.
Jul 15 00:20:36 Readynas avahi-daemon[3958]: Service "ReadyNAS Server on Readynas" (/etc/avahi/services/mt-daapd.service) successfully established.
Jul 15 00:20:36 Readynas avahi-daemon[3958]: Service "FrontView on Readynas" (/etc/avahi/services/frontview.service) successfully established.
Jul 15 00:20:36 Readynas avahi-daemon[3958]: Service "Readynas (CIFS)" (/etc/avahi/services/cifs.service) successfully established.
Jul 15 00:20:36 Readynas avahi-daemon[3958]: Service "Readynas (AFP)" (/etc/avahi/services/afp.service) successfully established.
Jul 15 00:21:45 Readynas chronyd[2993]: Invalid host/IP address at line 2
Jul 15 00:24:26 Readynas chronyd[2993]: No usable initstepslew servers at line 3 
Jul 15 00:24:26 Readynas chronyd[2993]: Initial txc.tick=10000 txc.freq=0 (0.00000000) txc.offset=0 => hz=100 shift_hz=7
Jul 15 00:24:26 Readynas chronyd[2993]: set_config_hz=0 hz=100 shift_hz=7 basic_freq_scale=1.28000000 nominal_tick=10000 slew_delta_tick=833 max_tick_bias=1000
Jul 15 00:24:26 Readynas chronyd[2993]: Linux kernel major=2 minor=6 patch=37
Jul 15 00:24:26 Readynas chronyd[2993]: calculated_freq_scale=1.00000000 freq_scale=1.00000000
Jul 15 00:56:06 Readynas kernel: usb 2-3: new high speed USB device using ehci_hcd and address 3
Jul 15 00:56:06 Readynas kernel: usblp0: USB Bidirectional printer dev 3 if 1 alt 0 proto 2 vid 0x04B8 pid 0x083C
Jul 15 00:56:06 Readynas kernel: scsi7 : usb-storage 2-3:1.2
Jul 15 00:56:07 Readynas kernel: scsi 7:0:0:0: Direct-Access     EPSON    Stylus Storage   1.00 PQ: 0 ANSI: 2
Jul 15 00:56:07 Readynas kernel: scsi: killing requests for dead queue
Jul 15 00:56:07 Readynas last message repeated 7 times
Jul 15 00:56:07 Readynas kernel: sd 7:0:0:0: Attached scsi generic sg6 type 0
Jul 15 00:56:07 Readynas kernel: sd 7:0:0:0: [sdg] Attached SCSI removable disk
Jul 15 00:56:09 Readynas avahi-daemon[3958]: Files changed, reloading.
Jul 15 00:56:09 Readynas avahi-daemon[3958]: Loading service file /etc/avahi/services/PRINTER-Stylus_Photo.service.
Jul 15 00:56:09 Readynas avahi-daemon[3958]: Got SIGHUP, reloading.
Jul 15 00:56:10 Readynas avahi-daemon[3958]: Service "EPSON Stylus Photo RX595 on Readynas" (/etc/avahi/services/PRINTER-Stylus_Photo.service) successfully established.
Jul 15 00:56:18 Readynas RAIDiator: USB device sdg has zero size, skipping.
Jul 15 02:21:59 Readynas kernel: plexserver invoked oom-killer: gfp_mask=0x201da, order=0, oom_adj=0, oom_score_adj=0
Jul 15 02:21:59 Readynas kernel: Pid: 3556, comm: plexserver Tainted: P            2.6.37.6.RNx86_64.2.4 #1
Jul 15 02:21:59 Readynas kernel: Call Trace:
Jul 15 02:21:59 Readynas kernel:  [<ffffffff8807eeaf>] dump_header+0x6f/0x190
Jul 15 02:21:59 Readynas kernel:  [<ffffffff8808ee2a>] ? wait_iff_congested+0xba/0x120
Jul 15 02:21:59 Readynas kernel:  [<ffffffff8804d500>] ? autoremove_wake_function+0x0/0x40
Jul 15 02:21:59 Readynas kernel:  [<ffffffff8807f3be>] oom_kill_process+0x27e/0x290
Jul 15 02:21:59 Readynas kernel:  [<ffffffff8807f61e>] out_of_memory+0x24e/0x300
Jul 15 02:21:59 Readynas kernel:  [<ffffffff880825a3>] __alloc_pages_nodemask+0x5f3/0x610
Jul 15 02:21:59 Readynas kernel:  [<ffffffff88084c47>] __do_page_cache_readahead+0xe7/0x220
Jul 15 02:21:59 Readynas kernel:  [<ffffffff88084d9c>] ra_submit+0x1c/0x20
Jul 15 02:21:59 Readynas kernel:  [<ffffffff8807e319>] filemap_fault+0x3b9/0x3c0
Jul 15 02:21:59 Readynas kernel:  [<ffffffff88092da0>] __do_fault+0x50/0x490
Jul 15 02:21:59 Readynas kernel:  [<ffffffff880bfdb6>] ? dput+0x26/0x130
Jul 15 02:21:59 Readynas kernel:  [<ffffffff88094f8c>] handle_mm_fault+0x1ac/0x840
Jul 15 02:21:59 Readynas kernel:  [<ffffffff88020139>] do_page_fault+0x139/0x420
Jul 15 02:21:59 Readynas kernel:  [<ffffffff880b7bfc>] ? path_put+0x2c/0x40
Jul 15 02:21:59 Readynas kernel:  [<ffffffff880b23dc>] ? vfs_fstatat+0x6c/0x70
Jul 15 02:21:59 Readynas kernel:  [<ffffffff8805e000>] ? compat_sys_futex+0x90/0x140
Jul 15 02:21:59 Readynas kernel:  [<ffffffff8804c1b0>] ? sys_clock_gettime+0x90/0xe0
Jul 15 02:21:59 Readynas kernel:  [<ffffffff885b479f>] page_fault+0x1f/0x30
Jul 15 02:21:59 Readynas kernel: Mem-Info:
Jul 15 02:21:59 Readynas kernel: DMA per-cpu:
Jul 15 02:21:59 Readynas kernel: CPU    0: hi:    0, btch:   1 usd:   0
Jul 15 02:21:59 Readynas kernel: CPU    1: hi:    0, btch:   1 usd:   0
Jul 15 02:21:59 Readynas kernel: DMA32 per-cpu:
Jul 15 02:21:59 Readynas kernel: CPU    0: hi:  186, btch:  31 usd:   0
Jul 15 02:21:59 Readynas kernel: CPU    1: hi:  186, btch:  31 usd:   0
Jul 15 02:21:59 Readynas kernel: active_anon:90561 inactive_anon:90683 isolated_anon:0
Jul 15 02:21:59 Readynas kernel:  active_file:238 inactive_file:191 isolated_file:32
Jul 15 02:21:59 Readynas kernel:  unevictable:381 dirty:0 writeback:0 unstable:0
Jul 15 02:21:59 Readynas kernel:  free:5090 slab_reclaimable:5696 slab_unreclaimable:5140
Jul 15 02:21:59 Readynas kernel:  mapped:93 shmem:2 pagetables:1795 bounce:0
Jul 15 02:21:59 Readynas kernel: DMA free:4220kB min:248kB low:308kB high:372kB active_anon:5644kB inactive_anon:5880kB active_file:0kB inactive_file:0kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15688kB mlocked:0kB dirty:0kB writeback:0kB mapped:0kB shmem:0kB slab_reclaimable:32kB slab_unreclaimable:0kB kernel_stack:16kB pagetables:88kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? yes
Jul 15 02:21:59 Readynas kernel: lowmem_reserve[]: 0 992 992 992
Jul 15 02:21:59 Readynas kernel: DMA32 free:16140kB min:16132kB low:20164kB high:24196kB active_anon:356600kB inactive_anon:356852kB active_file:952kB inactive_file:764kB unevictable:1524kB isolated(anon):0kB isolated(file):128kB present:1016752kB mlocked:4kB dirty:0kB writeback:0kB mapped:372kB shmem:8kB slab_reclaimable:22752kB slab_unreclaimable:20560kB kernel_stack:1504kB pagetables:7092kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:2942 all_unreclaimable? yes
Jul 15 02:21:59 Readynas kernel: lowmem_reserve[]: 0 0 0 0
Jul 15 02:21:59 Readynas kernel: DMA: 33*4kB 1*8kB 1*16kB 1*32kB 1*64kB 1*128kB 1*256kB 1*512kB 1*1024kB 1*2048kB 0*4096kB = 4220kB
Jul 15 02:21:59 Readynas kernel: DMA32: 1987*4kB 10*8kB 5*16kB 3*32kB 4*64kB 4*128kB 2*256kB 1*512kB 0*1024kB 1*2048kB 1*4096kB = 16140kB
Jul 15 02:21:59 Readynas kernel: 4235 total pagecache pages
Jul 15 02:21:59 Readynas kernel: 3372 pages in swap cache
Jul 15 02:21:59 Readynas kernel: Swap cache stats: add 545169, delete 541797, find 5631/7962
Jul 15 02:21:59 Readynas kernel: Free swap  = 0kB
Jul 15 02:21:59 Readynas kernel: Total swap = 2097084kB
Jul 15 02:21:59 Readynas kernel: 261792 pages RAM
Jul 15 02:21:59 Readynas kernel: 6514 pages reserved
Jul 15 02:21:59 Readynas kernel: 1222 pages shared
Jul 15 02:21:59 Readynas kernel: 248631 pages non-shared
Jul 15 02:21:59 Readynas kernel: [ pid ]   uid  tgid total_vm      rss cpu oom_adj oom_score_adj name
Jul 15 02:21:59 Readynas kernel: [  829]     0   829      450       58   1       0             0 ifplugd
Jul 15 02:21:59 Readynas kernel: [  940]     0   940      611        2   0     -17         -1000 udevd
Jul 15 02:21:59 Readynas kernel: [ 2096]     0  2096      424        0   1       0             0 acpid
Jul 15 02:21:59 Readynas kernel: [ 2102]     0  2102      422        0   0       0             0 raidard
Jul 15 02:21:59 Readynas kernel: [ 2264]     0  2264      633        1   1       0             0 quota_nld
Jul 15 02:21:59 Readynas kernel: [ 2269]     1  2269      453        0   0       0             0 portmap
Jul 15 02:21:59 Readynas kernel: [ 2304]     0  2304      437        9   0       0             0 syslogd
Jul 15 02:21:59 Readynas kernel: [ 2325]     0  2325      489        1   1       0             0 atd
Jul 15 02:21:59 Readynas kernel: [ 2332]     0  2332      425        0   1       0             0 klogd
Jul 15 02:21:59 Readynas kernel: [ 2344]     0  2344      940        7   0       0             0 cupsd
Jul 15 02:21:59 Readynas kernel: [ 2350]    21  2350      688        1   0       0             0 dbus-daemon
Jul 15 02:21:59 Readynas kernel: [ 2353]     0  2353      494       10   0       0             0 cron
Jul 15 02:21:59 Readynas kernel: [ 2397]     0  2397     3722        0   1       0             0 smbd
Jul 15 02:21:59 Readynas kernel: [ 2410]     0  2410      483        0   1       0             0 rpc.rquotad
Jul 15 02:21:59 Readynas kernel: [ 2416]     0  2416      470        0   1       0             0 rpc.statd
Jul 15 02:21:59 Readynas kernel: [ 2418]     0  2418     3722        1   1       0             0 smbd
Jul 15 02:21:59 Readynas kernel: [ 2456]     0  2456      483        1   0       0             0 rpc.mountd
Jul 15 02:21:59 Readynas kernel: [ 2722]     0  2722      431        6   1       0             0 ifplugd
Jul 15 02:21:59 Readynas kernel: [ 2909]     0  2909      431        6   1       0             0 ifplugd
Jul 15 02:21:59 Readynas kernel: [ 2976]     0  2976    11226       23   1       0             0 minidlna
Jul 15 02:21:59 Readynas kernel: [ 2987]     0  2987      534        1   0       0             0 cnid_metad
Jul 15 02:21:59 Readynas kernel: [ 2993]     0  2993     2704        1   0       0             0 chronyd
Jul 15 02:21:59 Readynas kernel: [ 3001]     0  3001      444        0   0       0             0 lld2d
Jul 15 02:21:59 Readynas kernel: [ 3002]     0  3002      424       12   0       0             0 upnpd
Jul 15 02:21:59 Readynas kernel: [ 3007]     0  3007     1779        1   0       0             0 afpd
Jul 15 02:21:59 Readynas kernel: [ 3011]    98  3011    22011        0   1       0             0 mysqld
Jul 15 02:21:59 Readynas kernel: [ 3069]     0  3069     3747       44   1       0             0 smbd
Jul 15 02:21:59 Readynas kernel: [ 3077]     0  3077     3788       69   0       0             0 smbd
Jul 15 02:21:59 Readynas kernel: [ 3079]     0  3079     2829       49   1       0             0 proftpd
Jul 15 02:21:59 Readynas kernel: [ 3085]     0  3085    10517       17   0       0             0 apache-ssl
Jul 15 02:21:59 Readynas kernel: [ 3185]     0  3185    48126       43   1       0             0 plexserver
Jul 15 02:21:59 Readynas kernel: [ 3260]     0  3260     4270        7   1       0             0 mt-daapd
Jul 15 02:21:59 Readynas kernel: [ 3266]     0  3266      454        0   1       0             0 dhcp6c
Jul 15 02:21:59 Readynas kernel: [ 3279]     0  3279      431        6   0       0             0 ifplugd
Jul 15 02:21:59 Readynas kernel: [ 3312]     0  3312     2211       20   0       0             0 nmbd
Jul 15 02:21:59 Readynas kernel: [ 3515]     0  3515    29094      110   1       0             0 Plex DLNA Serve
Jul 15 02:21:59 Readynas kernel: [ 3641]     0  3641      543       29   1       0             0 monitor_enclosu
Jul 15 02:21:59 Readynas kernel: [ 3958]    20  3958      711       39   0       0             0 avahi-daemon
Jul 15 02:21:59 Readynas kernel: [ 3972]     0  3972      425        2   0       0             0 getty
Jul 15 02:21:59 Readynas kernel: [ 5039]    98  5039    11036     1307   0       0             0 apache-ssl
Jul 15 02:21:59 Readynas kernel: [ 5259]    98  5259    13605      314   1       0             0 apache-ssl
Jul 15 02:21:59 Readynas kernel: [ 6679]     0  6679     3782       64   0       0             0 smbd
Jul 15 02:21:59 Readynas kernel: [23521]     0 23521   684512   176035   1       0             0 Plex Media Scan
Jul 15 02:21:59 Readynas kernel: [23653]    98 23653    10517       28   0       0             0 apache-ssl
Jul 15 02:21:59 Readynas kernel: Out of memory: Kill process 23521 (Plex Media Scan) score 832 or sacrifice child
Jul 15 02:21:59 Readynas kernel: Killed process 23521 (Plex Media Scan) total-vm:2738048kB, anon-rss:704140kB, file-rss:0kB
Jul 15 09:36:54 Readynas syslogd 1.4.1#18: restart.
Jul 15 09:36:54 Readynas kernel: klogd 1.4.1#18, log source = /proc/kmsg started.
Jul 15 09:36:54 Readynas kernel: Initializing cgroup subsys cpu
Jul 15 09:36:54 Readynas kernel: Linux version 2.6.37.6.RNx86_64.2.4 (jmaggard@calzone) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 SMP Mon May 21 16:00:40 PDT 2012
Jul 15 09:36:54 Readynas kernel: Command line: initrd=initrd.gz reason=normal BOOT_IMAGE=kernel 
Jul 15 09:36:54 Readynas kernel: BIOS-provided physical RAM map:

Here is the second time it happened today:


Jul 15 09:37:25 Readynas syslogd 1.4.1#18: restart.
Jul 15 09:38:11 Readynas avahi-daemon[3897]: Found user 'avahi' (UID 20) and group 'avahi' (GID 20).
Jul 15 09:38:11 Readynas avahi-daemon[3897]: Successfully dropped root privileges.
Jul 15 09:38:11 Readynas avahi-daemon[3897]: avahi-daemon 0.6.23 starting up.
Jul 15 09:38:11 Readynas avahi-daemon[3897]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
Jul 15 09:38:11 Readynas avahi-daemon[3897]: Loading service file /etc/avahi/services/PRINTER-Stylus_Photo.service.
Jul 15 09:38:11 Readynas avahi-daemon[3897]: Loading service file /etc/avahi/services/afp.service.
Jul 15 09:38:11 Readynas avahi-daemon[3897]: Loading service file /etc/avahi/services/cifs.service.
Jul 15 09:38:11 Readynas avahi-daemon[3897]: Loading service file /etc/avahi/services/frontview.service.
Jul 15 09:38:11 Readynas avahi-daemon[3897]: Loading service file /etc/avahi/services/mt-daapd.service.
Jul 15 09:38:11 Readynas avahi-daemon[3897]: Loading service file /etc/avahi/services/readynas.service.
Jul 15 09:38:11 Readynas avahi-daemon[3897]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::21f:33ff:feea:6273.
Jul 15 09:38:11 Readynas avahi-daemon[3897]: New relevant interface eth0.IPv6 for mDNS.
Jul 15 09:38:11 Readynas avahi-daemon[3897]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.2.120.
Jul 15 09:38:11 Readynas avahi-daemon[3897]: New relevant interface eth0.IPv4 for mDNS.
Jul 15 09:38:11 Readynas avahi-daemon[3897]: Network interface enumeration completed.
Jul 15 09:38:11 Readynas avahi-daemon[3897]: Registering new address record for fe80::21f:33ff:feea:6273 on eth0.*.
Jul 15 09:38:11 Readynas avahi-daemon[3897]: Registering new address record for 192.168.2.120 on eth0.IPv4.
Jul 15 09:38:11 Readynas avahi-daemon[3897]: Registering HINFO record with values 'X86_64'/'LINUX'.
Jul 15 09:38:12 Readynas avahi-daemon[3897]: Server startup complete. Host name is Readynas.local. Local service cookie is 780553564.
Jul 15 09:38:13 Readynas avahi-daemon[3897]: Service "ReadyNAS Discovery [Readynas]" (/etc/avahi/services/readynas.service) successfully established.
Jul 15 09:38:13 Readynas avahi-daemon[3897]: Service "ReadyNAS Server on Readynas" (/etc/avahi/services/mt-daapd.service) successfully established.
Jul 15 09:38:13 Readynas avahi-daemon[3897]: Service "FrontView on Readynas" (/etc/avahi/services/frontview.service) successfully established.
Jul 15 09:38:13 Readynas avahi-daemon[3897]: Service "Readynas (CIFS)" (/etc/avahi/services/cifs.service) successfully established.
Jul 15 09:38:13 Readynas avahi-daemon[3897]: Service "Readynas (AFP)" (/etc/avahi/services/afp.service) successfully established.
Jul 15 09:38:13 Readynas avahi-daemon[3897]: Service "EPSON Stylus Photo RX595 on Readynas" (/etc/avahi/services/PRINTER-Stylus_Photo.service) successfully established.
Jul 15 09:38:27 Readynas chronyd[3040]: Invalid host/IP address at line 1
Jul 15 09:39:48 Readynas chronyd[3040]: Invalid host/IP address at line 2
Jul 15 09:42:29 Readynas chronyd[3040]: No usable initstepslew servers at line 3 
Jul 15 09:42:29 Readynas chronyd[3040]: Initial txc.tick=10000 txc.freq=0 (0.00000000) txc.offset=0 => hz=100 shift_hz=7
Jul 15 09:42:29 Readynas chronyd[3040]: set_config_hz=0 hz=100 shift_hz=7 basic_freq_scale=1.28000000 nominal_tick=10000 slew_delta_tick=833 max_tick_bias=1000
Jul 15 09:42:29 Readynas chronyd[3040]: Linux kernel major=2 minor=6 patch=37
Jul 15 09:42:29 Readynas chronyd[3040]: calculated_freq_scale=1.00000000 freq_scale=1.00000000
Jul 15 12:18:04 Readynas syslogd 1.4.1#18: restart.
Jul 15 12:18:05 Readynas kernel: klogd 1.4.1#18, log source = /proc/kmsg started.
Jul 15 12:18:05 Readynas kernel: Initializing cgroup subsys cpu
Jul 15 12:18:05 Readynas kernel: Linux version 2.6.37.6.RNx86_64.2.4 (jmaggard@calzone) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 SMP Mon May 21 16:00:40 PDT 2012
Jul 15 12:18:05 Readynas kernel: Command line: initrd=initrd.gz reason=normal BOOT_IMAGE=kernel 
Jul 15 12:18:05 Readynas kernel: BIOS-provided physical RAM map:
Jul 15 12:18:05 Readynas kernel:  BIOS-e820: 0000000000000000 - 000000000009cc00 (usable)
Jul 15 12:18:05 Readynas kernel:  BIOS-e820: 000000000009cc00 - 00000000000a0000 (reserved)
Jul 15 12:18:05 Readynas kernel:  BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
Jul 15 12:18:05 Readynas kernel:  BIOS-e820: 0000000000100000 - 000000003feb0000 (usable)
Jul 15 12:18:05 Readynas kernel:  BIOS-e820: 000000003feb0000 - 000000003febe000 (ACPI data)
Jul 15 12:18:05 Readynas kernel:  BIOS-e820: 000000003febe000 - 000000003fef0000 (ACPI NVS)
Jul 15 12:18:05 Readynas kernel:  BIOS-e820: 000000003fef0000 - 000000003ff00000 (reserved)
Jul 15 12:18:05 Readynas kernel:  BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
Jul 15 12:18:05 Readynas kernel:  BIOS-e820: 00000000ffb00000 - 0000000100000000 (reserved)
Jul 15 12:18:05 Readynas kernel: NX (Execute Disable) protection: active

What is killing the NAS? I can't see a consistant action that does this. What I DO know is that if you look at the logs inside frontview it doesn't even acknowledge that it went offline. It just acknowledges that I manually rebooted the device. I'd love any help you guys can offer.

PapaBear1
Apprentice
Jul 15, 2012
I would open a new tech support ticket and refer it to the previous.
Pezman
Aspirant
Jul 15, 2012
PapaBear,

I've taken your advice and opened a ticket with NETGEAR (18988091). I've also updated the above posts to be a bit more accurate. Do you guys think of anything else?
Bigbearf
Aspirant
Jul 15, 2012
It appears that your Load Cycle Counts are high. Did you run the WDIDLE /D and TLER ON on your WD Drives. I think the one with over a million LCCs may be a problem. See my prior posts for tips on running the WDIDLE and TLER dos programs on your WD green drives to halt LLC escalations. I have started replacing my WD20EADS drives with WD2003FYYS enterprise drives and they work great. They are about $225 on Amazon Prime.
Hope this helps.
bigbearf

StephenB

Guru - Experienced User

Jul 16, 2012

Based on your response, it seems unlikely to me that this is disk-drive related. Let us know what support concludes.

Pezman wrote:
1) I don't utilize the disc spindown feature in the Frontpage Control Panel. Should I be?...

Pezman wrote:
1) I don't utilize the disc spindown feature in the Frontpage Control Panel. Should I be?...

Some people like the power savings (though they are relatively small), but there are some drawbacks. The NAS will take several seconds to spin them up when you access it, and if the spin down is too frequent, it probably increases drive wear. I do have spindown configured, but with a long threshold. I don't make a recommendation either way though.

The reason I was asking was that I was wondering if the issue might be related to disk spin up. That doesn't seem to be the case.

Pezman wrote:
2) The frontview page says they are all ok. Here is the more detailed version (look at drive 5)...This Hard Drive is complaining about stuff. Is there something I should do to resolve?...

Pezman wrote:
2) The frontview page says they are all ok. Here is the more detailed version (look at drive 5)...This Hard Drive is complaining about stuff. Is there something I should do to resolve?...

The reallocated sectors (and related pending sector counts) are concerning. Netgear support usually suggests replacement when those counts reach 50 (I would sum them, since the only difference is the pending sector error was detected on a read, while the reallocated sector is detected on a write). If you see these counts begin to rise, then I would immediately replace it. After you get the case resolved, you could schedule a disk scrub, which would perhaps find more errors (letting you know they are there).

As BigBearf says, the load cycle counts are high, particularly on drives 5 and 6. Running Wdidle and tler is often suggested, though it is something that Western Digital doesn't recommend, so it is "at your own risk". I haven't run them myself, I am planning to simply replace the drives when they fail. In any case, I don't see any point in running them on drives that already have load counts over a million.

BigBearf wrote:
I have started replacing my WD20EADS drives with WD2003FYYS enterprise drives and they work great. They are about $225 on Amazon Prime.

BigBearf wrote:
I have started replacing my WD20EADS drives with WD2003FYYS enterprise drives and they work great. They are about $225 on Amazon Prime.

The new Western Digitial RED line is another option (though since they just came out, no one has experience with them yet).

Pezman
Aspirant
Jul 19, 2012
FYI, for those interested, I'm still awaiting feedback from support on my ticket. I have sent them all of my logs to a level 2 tech and they are reviewing it. I'll keep you posted once I hear more.
cficik
Aspirant
Jul 26, 2012
Having the exact same issue since upgrading to this version on my ready as pro. Was running fine until the afternoon after it was upgraded. Please post any info you get from support.
Dakurt71
Aspirant
Aug 03, 2012
I have the same problem , but i think it has something to do with plex, although i removed it and reinstalled. Has anybody solved this?