Hi..I having an intermittently problem with my NAS 104 (sw 6.0.5) after a few days of operation the unit freezes , no response from the web or Power button. The only way to recover is to remove the power. Which then causes a rebuild of the drive array, which takes 24 hours ~Is they any logs in ssh i can look at that might indicate the cause of the problem ?Is anyone else have the same issue ??currently configured with 3* 3TB drives ThanksAndrew~

Could you send in your system logs?

I've seen the same on OS6, though on the #notsupported method of running it on an Ultra2. In my case, btrfs/kernel memory is doing something weird. Via SSH, the system says 'out of disk space', even though clearly has space, likely some memory leak. The GUI (readynasd) is unusable because it cannot write to its database (disk full), so it won't even load up. Only a reboot resolves it for ~12 hours.If you have SSH, are you able to even try 'touch ~/test', or does it report disk full in that state?$ ssh root@10.1.2.1root@10.1.2.1's password: Welcome to ReadyNASOS 6.0.5# touch testtouch: cannot touch `test': No space left on device# free total used free shared buffers cachedMem: 1009736 765592 244144 0 1272 563856-/+ buffers/cache: 200464 809272Swap: 523964 0 523964# df -hFilesystem Size Used Avail Use% Mounted onrootfs 4.0G 2.2G 1.4G 62% /tmpfs 10M 4.0K 10M 1% /dev/dev/md0 4.0G 2.2G 1.4G 62% /tmpfs 494M 4.0K 494M 1% /dev/shmtmpfs 494M 7.1M 486M 2% /runtmpfs 494M 0 494M 0% /sys/fs/cgrouptmpfs 494M 0 494M 0% /media/dev/md127 927G 215G 675G 25% /data/dev/md127 927G 215G 675G 25% /home/dev/md127 927G 215G 675G 25% /appsOut of curiosity, I went poking around, and found that if I disable the space_cache option on this mount point, the 'out of disk space' issue goes away, not requiring a reboot to get back to sane function.# mounttmpfs on /dev type tmpfs (rw,relatime,size=10240k,mode=755)devpts on /dev/pts type devpts (rw,relatime,mode=600)/dev/md0 on / type btrfs (rw,relatime,space_cache)proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755)tmpfs on /sys/fs/cgroup type tmpfs (rw,nosuid,nodev,noexec,mode=755)cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)cgroup on /sys/fs/cgroup/cpu type cgroup (rw,nosuid,nodev,noexec,relatime,cpu)cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=24,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)debugfs on /sys/kernel/debug type debugfs (rw,relatime)tmpfs on /media type tmpfs (rw,nosuid,nodev,noexec,relatime,mode=755)fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)configfs on /sys/kernel/config type configfs (rw,relatime)/dev/md127 on /data type btrfs (rw,relatime,space_cache)/dev/md127 on /home type btrfs (rw,relatime,space_cache)/dev/md127 on /apps type btrfs (rw,relatime,space_cache)# mount -o remount,nospace_cache /# mounttmpfs on /dev type tmpfs (rw,relatime,size=10240k,mode=755)devpts on /dev/pts type devpts (rw,relatime,mode=600)/dev/md0 on / type btrfs (rw,relatime,nospace_cache)proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755)tmpfs on /sys/fs/cgroup type tmpfs (rw,nosuid,nodev,noexec,mode=755)cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)cgroup on /sys/fs/cgroup/cpu type cgroup (rw,nosuid,nodev,noexec,relatime,cpu)cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=24,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)debugfs on /sys/kernel/debug type debugfs (rw,relatime)tmpfs on /media type tmpfs (rw,nosuid,nodev,noexec,relatime,mode=755)fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)configfs on /sys/kernel/config type configfs (rw,relatime)/dev/md127 on /data type btrfs (rw,relatime,space_cache)/dev/md127 on /home type btrfs (rw,relatime,space_cache)/dev/md127 on /apps type btrfs (rw,relatime,space_cache)# touch test# df -hFilesystem Size Used Avail Use% Mounted onrootfs 4.0G 2.1G 1.4G 62% /tmpfs 10M 4.0K 10M 1% /dev/dev/md0 4.0G 2.1G 1.4G 62% /tmpfs 494M 4.0K 494M 1% /dev/shmtmpfs 494M 7.1M 486M 2% /runtmpfs 494M 0 494M 0% /sys/fs/cgrouptmpfs 494M 0 494M 0% /media/dev/md127 927G 215G 675G 25% /data/dev/md127 927G 215G 675G 25% /home/dev/md127 927G 215G 675G 25% /apps

RN104 uses ext4 for the root filesystem, so this is likely something different.chirpa, can you try running:mount -o remount,clear_cache /I've also seen apps that would create large files on root, then unlink them while they're still in use -- thereby not actually freeing the space. So that would be another possibility.

I'll give that a try. Why does mtab list root as btrfs and not ext4? Backwards compatible, so no real hardm? Or is this a side affect of OS6 on old x86 models?I recall BackupExec RALUS had this issue once. Do you remember what proc tools were used to narrow down which process was 'eating' memory?Anyways, don't want to side-track AndrewT's thread if his issue turns out to be not related to this disk space eating issue.

All x86 boxes do btrfs on root; ARM does ext4. So your mtab should be accurate. You can look at the entries in /proc/*/fd/ to see open file descriptors.

NAS 104 locking up | NETGEAR Communities

39 Replies

Replies have been turned off for this discussion

mdgm-ntgr
NETGEAR Employee Retired
May 25, 2013
There are some 6.0.6 Release Notes: http://www.readynas.com/forum/viewtopic.php?f=1&t=71101
MarcusF
NETGEAR Employee
May 27, 2013
Release notes will be stored in netgear download centre going forward
http://downloadcenter.netgear.com/en/default.aspx

Enter model to find all info
In this case rn10400 Under each release there is a link to release notes.

6.0.6 is there now (with other releases). I am finding out why 6.0.5 is not there.

@AndrewT I have asked support to contact you and we will log a case
I had quick look through the logs and I see nothing obvious causing an issue.
we most likely will need ssh access to monitor the unit and confirm if we can see any building issue.
AndrewT1
Aspirant
May 31, 2013
Had a response from support to say I need to upgrade the firmware on my ST30000DM001 drives from cc24 to cc32 but cant find cc32 firmware on the Seagate Web site .. anyone know were I might find it ?

Anrew
chirpa
Luminary
May 31, 2013
NTGR Support (via Engineering) has the closest direct contact to Seagate Engineering. So I would follow up with the support response you got, and request the required update from them.
StephenB
Guru - Experienced User
May 31, 2013
In the meantime, try the Seagate Download Finder Tool (https://apps1.seagate.com/downloads/req ... kie=en_US_)
benny90
Aspirant
Jun 02, 2013
Hello,I have the same issues.
My NAS RN 104 keeps freezing, and when this happen Raidar cannot find it as it is disconnectiing and the NAS does not respond at all when I press the power button 1 or 2 times, the display remains black....
The only way to reboot is to unplug the power cable and then it works for few hours and crash again...
My configuration:
- Win 7
- Firmware 6.0.6
-4 x 2To WD Red RAID5
Network configuration: Router -> CPL-1 (devolo AVPlus200 -> Switch (GS105E or GS108Ev2) -> NAS
- Cable: Cat 5e or Cat 6 ( I tried both).
I have downloaded the Logs files from the Web Interface if you need.
I also tried to to fix the ip manually and not with DHCP without success...

Hope you can help me because I am stuck...
StephenB
Guru - Experienced User
Jun 02, 2013
Have you tried Netgear support? You have 90 days of free phone support, if you are somehow past that (not sure it is possible) you can do an online submission at support.netgear.com
benny90
Aspirant
Jun 03, 2013
Yes I've open a ticket:
They told me to do a OS-Reinstall but my NAS is still crashing after that.
I made a memory test as well and it was successfull.

What would you recommand ?
StephenB
Guru - Experienced User
Jun 03, 2013
Did they look at the logs?

You could escalate the support request to level 3.
Or perhaps do an RMA.

Another option is to test the disks in a PC (WDC's lifeguard program). Though you'd need to power down the NAS before you remove them.
AndrewT1
Aspirant
Jun 04, 2013
Benny90

NTG are replacing my NAS104 , Will let you know if it makes any difference ....

I can make mine crash just loading the unit e.g doing a backup to USB attached drive

Andrew

Forum Discussion

NAS 104 locking up

39 Replies

Related Content

READY NAS 104

RN-104 NAS

Ready NAS 104 Locks Up (6.4.1)

Unable to access NAS 104 connected to Orbi RBR850

Ready NAS 104 Slow Performance

NETGEAR Academy

ProSupport for Business