NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
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, one Western Digital as Volume1 and Volume2 respectively. Volume1 backs up to CrashPlan.
Recently, the performance of my ReadyNAS was terrible. My browser/ssh session/share folder would spin for hours, and sometimes would respond and sometimes would fail. I have done several hard reboots and after each one the response recovered, only to return days/weeks later.
After my most recent hard reboot, I no longer see Volume1. The share is gone, and from the admin page it does not show up either. I highly suspect the Seagate drive that housed Volume1 has failed, but I would like to do some diagnostics to confirm my suspicion. Is there a step by step for ReadyNAS, or do I need to physically pull the drive and diagnose it outside of the NAS unit?
Additionally (yes, i realize CrashPlan is not a supported piece of software on ReadyNAS) has anyone already gone through this process where you had CrashPlan and ReadyNAS and a drive/volume failed? If so, any gotchas/pointers based on your experience?
Thanks!
Phil
7 Replies
Replies have been turned off for this discussion
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.varsTARGETDIR=/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.tgzJAVACOMMON=/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
I am inclined to think that my HD in bay 1/HelmNAS1 is simply corrupted. Do you have any other suggestions?
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,
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
