Forum Discussion

Aspirant

Oct 11, 2015

How to diagnose ReadyNAS

Hi all, brand new to the forum, so i apologize in advance for dumb or repeated questions. I have a ReadyNAS 102 with firmware 6.4.0. Non-RAID JBOD configuration. Each are 2TB drives one Seagate,...

Other Discussions

dendron8

Aspirant

Oct 24, 2015

Thanks for the response StephenB. I read through some of that thread you recommended and I am not entirely convinced that is related to my problem. That thread talks about Crashplan requiring Java 1.7 or 1.8, and I already have 1.7 installed and configured:

root@helm-home-nas:~# java -version
java version "1.7.0_65"
OpenJDK Runtime Environment (IcedTea 2.5.3) (7u71-2.5.3-2~deb7u1)
OpenJDK Zero VM (build 24.65-b04, mixed mode)
root@helm-home-nas:~# cat /usr/local/crashplan/install.vars

TARGETDIR=/usr/local/crashplan
BINSDIR=/usr/local/bin
MANIFESTDIR=/usr/local/var/crashplan
INITDIR=/etc/init.d
RUNLVLDIR=/etc/rc5.d
INSTALLDATE=20141219
APP_BASENAME=CrashPlan
DIR_BASENAME=crashplan
JRE_X64_DOWNLOAD_URL=http://download.code42.com/installs/proserver/jre/jre-7u45-linux-x64.tgz
JRE_I586_DOWNLOAD_URL=http://download.code42.com/installs/proserver/jre/jre-7u45-linux-i586.tgz

JAVACOMMON=/usr/bin/java
root@helm-home-nas:~# which java
/usr/bin/java
root@helm-home-nas:~#

Additionally, some of the posts in that thread imply that the symptom is that NONE of the shares appear. In my case, I have 2 volumes, and only 1 of them is not working. On my ReadyNAS, I see this

root@helm-home-nas:/# cd HelmVolume1
root@helm-home-nas:/HelmVolume1# ls
root@helm-home-nas:/HelmVolume1# ls -al
total 8
drwxr-xr-x 2 root root 4096 Dec 18 2014 .
drwxr-xr-x 26 root root 4096 Oct 11 09:03 ..
root@helm-home-nas:/HelmVolume1# cd ../HelmVolume2
root@helm-home-nas:/HelmVolume2# ls -al
total 8
drwxr-xr-x 1 root root 54 Dec 18 2014 .
drwxr-xr-x 26 root root 4096 Oct 11 09:03 ..
drwxrwxrwx+ 1 guest guest 20 Dec 18 2014 HelmNAS2
drwx------ 1 root root 0 Dec 18 2014 .purge
drwxr-xr-x 1 root root 16 Dec 31 1969 ._share
drwx------ 1 root root 0 Dec 18 2014 .vault
root@helm-home-nas:/HelmVolume2#

in the admin panels i see this

2015-10-24 09_36_30-Clipboard.png

I am inclined to think that my HD in bay 1/HelmNAS1 is simply corrupted. Do you have any other suggestions?

JennC

NETGEAR Employee Retired

Oct 24, 2015

Hello dendron8,

Welcome to the community!

The NAS should still see the disk 1.

Since this is non-RAID, can you try reinserting the disk 1? If same problem, power off NAS, remove disk 1 and check it with diagnostic tools.

Regards,

StephenB
Guru - Experienced User
Oct 24, 2015
When the OS partition fills, the NAS will eventually become completely non-responsive. Along the way, the admin UI starts to misbehave, SMB shares then begin to misbehave, and eventually SSH stops responding. In the earlier stages, you won't see all of these.

Did you check for OS partition fullness? That is log in via ssh and then enter

df . -h

df . -i
- dendron8
  Aspirant
  Nov 07, 2015
  Thanks StephenB. The output from the command looks like this:
  
  root@helm-home-nas:~# df . -h
  Filesystem Size Used Avail Use% Mounted on
  /dev/md0 4.0G 3.0G 801M 79% /
  root@helm-home-nas:~# df . -i
  Filesystem Inodes IUsed IFree IUse% Mounted on
  /dev/md0 65536 30393 35143 47% /
  root@helm-home-nas:~#
  
  I am guessing that is telling me the partition is not full?
  - StephenB
    Guru - Experienced User
    Nov 08, 2015
    dendron8 wrote:
    
    Thanks StephenB. The output from the command looks like this:
    
    root@helm-home-nas:~# df . -h
    Filesystem Size Used Avail Use% Mounted on
    /dev/md0 4.0G 3.0G 801M 79% /
    root@helm-home-nas:~# df . -i
    Filesystem Inodes IUsed IFree IUse% Mounted on
    /dev/md0 65536 30393 35143 47% /
    root@helm-home-nas:~#
    
    I am guessing that is telling me the partition is not full?
    
    Actually it is quite full. Normally it is around 20-30%, not 79%.
    
    Have you moved the crashplan cache to the data volume?
dendron8
Aspirant
Nov 07, 2015
Thanks for the response Jen. I have a Seagate Barracuda 2TB DOM 1/13 - almost 3 years old but should be good i think. Unfortunately the link you provided takes me to the Seagate site, and I only see ways to diagnose an internal or USB external drive. To diagnose this drive I am going to have to purchase an adapter and a power supply to connect it to my desktop.

Are there ways to diagnose the drive when its docked in the ReadyNAS ?