NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
ReadyNASPro2 data loss after freeze and reboot?
Hi all, i got a big problem with my readyNasPro2. After my return from vacation my nas totaly got freezed. After the reastart without changing the configuration it claimed "A new disk was added to the ReadyNAS. If multiple disks have been added, they will be processed one at a time. Please do not remove any added disk(s) during this time." Now it looks like all my data is not accessible or even gone. When i reeboot the message "The paths for the shares listed below could not be found. Typically, this occurs when the ReadyNAS is unable to access the data volume. RNXconfig documents media DVBLink Dropbox backup MemeoBackup" appers. (where the mentioned names, starting with documents, are my shares) I removed the drives to check whether this is only affecting one drive. The error occors with each single disk. When i connect via SFTP there is only 1 file showing up under the c/. Do you have any ideas to get access or recover my data? Thank you very much in advance! best regards, Martin --- When i boot the ReadyNAS i get the following messages: 1) ***** File system check performed at Mon May 29 10:13:03 CEST 2017 ***** fsck 1.42.12 (29-Aug-2014) fsck.ext4: No such file or directory while trying to open /dev/c/c Possibly non-existent device? --- 2) The paths for the shares listed below could not be found. Typically, this occurs when the ReadyNAS is unable to access the data volume. RNXconfig documents media DVBLink Dropbox backup MemeoBackup [Mon May 29 10:13:27 CEST 2017] ----
RN104 freezing during copy. How to troubleshoot?
When I try to copy files from one share to another (on the same NAS device), Windows Explorer hangs and ReadyNAS becomes unresponsive. Copying seems to work for most shares, but always causes issues for others. When the copy attempt fails, I cannot open the Admin Page (it prompts me to log in, but after logging in, I only see the screen with the firmware version). If I manage to access the Admin Page, and try to reboot or shut down, the sutdown never completes. I can't shut down using the power button either; it just displays the "Good-bye" message on the LCD panel, so I need to unplug the cord. Once rebooted (via unplugged cord), the system comes back to life, and I can access the Admin Page, reboot normally, etc, but if I try to attempt another copy, the story repeats. I am wondering how I can troubleshoot the problem. Could it be an issue with disks? Is there any way to verify that the disks are okay? Could it be the device itself? Firmware? Somehting else? I am using two 3 TB Toshiba drives configured as RAID 1 (I think I'm using Netgear's propriatary RAID configuration which automatically increaes space when you add drives). The latest firmware (v6.4.2) was installed around the time when the problem started happening a few weeks ago (before that, it had been running problem free for over a year). I do not get alerts about drive failures. The Admin Page shows that everything is fine. Did not find anything suspicious in the logs. Space info shows 973 GB free of 2.7 TB. I'm not running any apps or anti-virus on the device. All shares are configured for access from Windows (typical settings, no FTP, etc). I turned COW off, but it did not make a difference. I'm not saving snapshots. On the client side, I use Windows 10 (x64) on wired and wireless-N home network (tried different laptops, same problem). Any ideas how to troubleshoot it? If this is not obvious, I'd like to first make sure the drives are good. Is there a recommended procedure to test RAID 1 drives without the risk of breaking something? Or is there something else I'd need to check first? Thanks in advance.
ReadyNAS NV+ syslogd taking 100% CPU
Hi - I've got a Sparc-based ReadyNAS NV+ that I've had for years. Currently running RAIDiator 4.1.14; 4 x 2TB drives in Raid-X configuration, with about 300G/5.5T free. Lately, the NAS box will become non-responsive during transfers and I have to pull the power, and re-install the OS in order to make it happy. Unfortunately, it's not happy for more than a few hours at a time lately, and I've had to do this once a day or so. By non-responsive, I mean that I can ping it, but not telnet/ssh/frontview, and the front-panel power-button seems to do nothing with a brief press. I've bought its replacement, and am transferring ~ 6TB off it via CIFS, and it is still locking up. This last time, I left top running in a terminal window, which was still updating, though slowly. top - 18:24:58 up 1 day, 1:18, 1 user, load average: 9.04, 9.07, 9.02 Tasks: 67 total, 5 running, 62 sleeping, 0 stopped, 0 zombie Cpu(s): 1.6% us, 98.4% sy, 0.0% ni, 0.0% id, 0.0% wa, 0.0% hi, 0.0% si Mem: 226352k total, 221632k used, 4720k free, 8976k buffers Swap: 767904k total, 1856k used, 766048k free, 188352k cached PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 1571 root 25 0 2128 960 800 R 97.7 0.4 1000:39 syslogd 1066 root 16 0 2992 1168 896 R 2.3 0.5 33:38.83 top 1 root 15 0 2000 592 496 S 0.0 0.3 0:05.09 init 2 root 34 19 0 0 0 S 0.0 0.0 0:00.03 ksoftirqd/0 3 root 10 -5 0 0 0 S 0.0 0.0 0:00.04 events/0 4 root 10 -5 0 0 0 D 0.0 0.0 0:00.03 khelper 5 root 10 -5 0 0 0 S 0.0 0.0 0:00.01 kthread 10 root 10 -5 0 0 0 S 0.0 0.0 0:09.36 kblockd/0 13 root 10 -5 0 0 0 S 0.0 0.0 0:00.01 khubd Syslogd with 1000 minutes of runtime, and 98.4% sys CPU seems very likely to be the cause of my problem. The rootfs wasn't full just prior to the CIFS transfer. nasgul:~# df / -i Filesystem Inodes IUsed IFree IUse% Mounted on /dev/hdi1 128000 11330 116670 9% / nasgul:~# df / -h Filesystem Size Used Avail Use% Mounted on /dev/hdi1 1.9G 642M 1.3G 33% / So, what's my next step here? A factory reset would be more palatable after I'm convinced that my data has been successfully backed up to the new NAS box. What can I do to keep the box up while I do my transfers and verifications? Thanks.