NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
6.4.0
11 Topics
rn104 updated to 6.4.0 and possible solution to random lock-ups
Hello everyone, I have updated my RN104 last week, and have been poised by the unit hanging up randomly since then. I have searched andread a lot of posts here, and after 5 hard reboot and re-syncing, I may have found a solution. At least, it's been 1 day the unit has not locked up, so I'm crossing my fingers. The culprit, I think, might by the snapshot creation. I had 3 share protected by snapshots. Documents, Caldav/Carddav hosting and my ebooks collection. All those share had a daily snapshooting policy. After reading the "FAQs on upgrading ReadyNAS firmware to 6.4.0" post linked in here, the last chapter caught my eye: btrfs-cleaner is commonly invoked after Smart Snapshot Management prunes older snapshots. ReadyNAS commonly prunes older snapshots based on its snapshot schedule. Now, my nas is almost 80% full, and the snapshots where taking around 4Gb of space (out of a 4 disks Raid5 array of 6To usable). As the unit completely locks up, no SSH-ing in to check how much CPU the btrfs-cleaner process takes, of course, and nothing in the syslog appart a bunch "@" at the time the hangs-up hapenned. Oct 13 21:48:05 nas kernel: [ 6591.520831] md: delaying resync of md126 until md127 has finished (they share one or more physical units) Oct 13 21:48:06 nas readydropd[4685]: DEBUG:readydropd.c:897 Shares.conf has been changed Oct 13 21:48:07 nas readydropd[4685]: DEBUG:readydropd.c:652 Reload Share configs Oct 13 21:48:08 nas kernel: [ 6593.661751] md: delaying resync of md126 until md127 has finished (they share one or more physical units) Oct 13 21:48:08 nas kernel: [ 6594.415415] md: delaying resync of md126 until md127 has finished (they share one or more physical units) Oct 13 21:48:09 nas kernel: [ 6594.927980] md: delaying resync of md126 until md127 has finished (they share one or more physical units) @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@Oct 13 21:53:01 nas kernel : imklog 5.8.11, log source = /proc/kmsg started. Oct 13 21:53:01 nas rsyslogd: [origin software="rsyslogd" swVersion="5.8.11" x-pid="2837" x-info="http://www.rsyslog.com"] start Oct 13 21:53:01 nas kernel: Booting Linux on physical CPU 0x0 Oct 13 21:53:01 nas kernel: Initializing cgroup subsys cpuset Oct 13 21:53:01 nas kernel: Initializing cgroup subsys cpu Oct 13 21:53:01 nas kernel: Initializing cgroup subsys cpuacct Reading the FAQ, I thought that I would try to remove the snapshots creation schedules of my shares, and remove all the existing snapshots. Since this moment, I had no more issues. By the way netgear, I'd really like to know another way than using the timeline to clean old snapshot. Removing 108 snapshots manually, one after the other was not fun... The "emergency" button in the shares/browse is nowhere to be found today in my web gui, so that only leaves the timeline afaik... It might not be relevant, but maybe the combination of low disk space, numerous snapshots and high CPU usage (because syncing back the array after the last hard reboot, my cpu load reported by "top" was around 12~15 at that time) might have been the issue. To be really torough, I even have deactivated DLNA, AFP and SMB services, leaving only the NFS, as I'm using linux boxes as client anyway. DLNA re-scanning the shares seems to be heavy, when resyncing the disks. Maybe it can help other people I've seen here having unresponsive units after bootup too. I'll come back comenting here if the unit locks-up again, but I am confident. Regards. Thierry.Solved13KViews0likes92Comments
RN316 randomly freezing shared folder on 6.4.0
Hi, I upgraded a client's RN316 to firmware 6.4.0 about 2 days ago. The firmware update reported successful and all seemed ok for about half a day. Now the primary share (2.7TB) of data, has become extremely unstable, randomly freezing up for about 10 minutes when PC's or Macs try to access it. Protocols enabled are SMB, AFP and NFS, and permissions are open - everyone can read/write. The unit has 2 x 4TB hard drives running (mirrored). Approx. 25-30 users may be accessing the share at any one time, and this was fine on 6.2.4. I had hourly snapshots running, but have reduced them to daily to try troubleshoot - the issue persists. I have tried using the 2nd NIC instead (Gb LAN), changed the device IP address, really just about exhausted all I can think of. Is there any way to rollback to 6.2.4? Will resetting permissions maybe help, or switching off and re-enabling protocols for the relevant share...? Thanks guys, I'm at a loss here. A great product being let down by these bugs right now :(Solved11KViews1like22Comments
ReadyNAS 104 system hanging frequently after 6.4.0 upgrade
Hi All, I have a pretty new ReadyNAS 104 system (August, 2015). Currently populated with 3 x 4TB WD RED drives, and a single Segate 3TB drive (to be upgraded once funds allow). Since upgrading to FW 6.4.0 I have found that the system will hang whenever a maintenance process is performed - Scub, Balance or Defrag, which I had scheduled previously. I have now disabled all the schedules and left the system alone, but overnight it has hung again, after approximately 72 hours of normal operation. It responds to pings, but the GUI will not load, it has dropped off the network via all protocols, fails to allow you to SSH into it and pressing the power button (Once, twice and three times) has absolutely no effect. The only option is to pull the plug. Also, after every hang, forcing a power pull, the system starts a complete resync of the volume, which always starts at 25.10% and takes about 4 days to complete over the 15TB of raw storage. Obviously this is putting undue strain on the disks everytime it is happening. Happy to provide logs to any friendly Netgear Admins, and any advice from any of you lovely people would be gratefully received. Cheers, Tipster10KViews2likes26CommentsReady NAS 6.4.0 rsync error copying data from Linux server
Hi there, may someone help me? I have a NAS (ReadyNas 102 6.4.0) and a Linux server on the same subnet. I scheduled a backup (rsync + ssh) on the NAS, the source is the Linux server and the destination is the NAS. The backup starts at 0:05:07 The backup ends at 1:15:53 The backup status is: ERROR DURING THE COPY Failed to run rsync, return rc 7680 (30) 'rsync' command returns rc=7680 This's the log I got (sorry for the Italian language settings): Nome processo di backup: zucchetti_full_151027 Tipo di processo di backup: Massima Protocollo: rsync+ssh Origine di backup: [remote:rsync+ssh]/192.168.37.205://home/e-smith/zucchetti Destinazione di backup: [BACKUP-ES]/ Ora di inizio backup: Mer Ott 28 2015 0:05:07 Ora di fine backup: Mer Ott 28 2015 1:15:53 Stato backup: Non riuscito: errore durante la copia. Failed to run rsync, return rc 7680 (30) 'rsync' command returns rc=7680 zucchetti/Acer (C) - collegamento.lnk zucchetti/DATA (D) - collegamento.lnk zucchetti/chromeinstall-7u45.exe zucchetti/dati (192.168.36.1dati) (K) - collegamento (2).lnk zucchetti/dati (192.168.36.1dati) (K) - collegamento.lnk zucchetti/dati (192.168.37.1dati) (K) - collegamento (2).lnk zucchetti/dati (192.168.37.1dati) (K) - collegamento.lnk zucchetti/jre-1_5_0_16-windows-i586-p.exe zucchetti/jre-6u18-windows-i586-s.exe zucchetti/jre-7u79-windows-i586-iftw.exe rsync error: timeout in data send/receive (code 30) at io.c(137) [sender=3.0.9] rsync: connection unexpectedly closed (62585 bytes received so far) [receiver] rsync error: error in rsync protocol data stream (code 12) at io.c(226) [receiver=3.1.1] rsync: [generator] write error: Broken pipe (32) rsync error: timeout in data send/receive (code 30) at io.c(820) [generator=3.1.1] --------------------------------------- Any help is wellcome Best regards Dario5.6KViews0likes7Comments
ReadyNas 312 Firmware Upgrade Failing
Hi, I have an issue with our ReadyNas 312. It's currently running firmware 6.1.6, and seems to have dropped off our domain. So when I logged in, I noticed a popup saying there is a firmware upgrade to 6.4.0. So I clicked on the 'Update' button. The update looked ike it downloaded OK, but then gave an error saying "Cannot write file". So I tried a manual update, downloaded Firmware 6.4.0 to my laptop from http://kb.netgear.com/app/answers/detail/a_id/29938 then unzipped it, and uploaded the .img file. The readynas said it would upgrade after a reboot, and asked if I wanted to reboot now. I said yes. I then waited 15 minutes, but the ReadyNas never comes back up. I've opened a cmd prompt, and ping the IP, but the network never comes back up. I have to perform a hard reboot, the ReadyNas then comes back, but on the same old firmware. I've tried again, running a constant ping test, I can see the ReadyNas reboots, as the ping stops, but then it never returns, until you do a hard reboot again. Anyone have any ideas? I'm unable to performt he firmware upgrade either automatically or manually! Thanks BenSolved3.9KViews0likes3Comments
Where to find maintenance utilities after update to 6.4.0?
Hello all, I updated my ReadyNAS104 to 6.4.0 today. Before I had 6.2.4 installed. Since the update to 6.4.0 I'm missing the maintenance utilities like - rebalance - disk test - data scrub ... I had schedules defined for them but now that menue seems to be is not available anymore with 6.4.0. As there is not manual for 6.4 I searched here, but did not find details so far. Can someone help me with this? Thanks and regards...HolgerSolved3.8KViews0likes9CommentsReplicate failes since firmware 6.4.0 (RN102)
Hi, since updating to firmware 6.4.0, Replicate over internet failes with exit code 10 (RN102). According to log files the detected connection before the update was relayed (method 5), afterwards LAN (mehod 2). The target NAS is not yet on firmware 6.4.0. Does someone have any suggestions? Thanks, KimSolved3.5KViews0likes3CommentsReadyNAS 204 OS 6.4.0 "Please remove inactive volumes", case #25950625
Hi, after some stability issues of my ReadyNAS 204 in the past with different OS 6 releases it now finally crashed some weeks after the installation of 6.4.0 with the above error message. I've opened the above case, response from tech support is i had a power failure and should order data recovery services. I do have a backup which is quite a bit outdated, however i do not understand why i should pay for data recovery services as (to me) it seems there are many bugs in 6.4.0 which might have caused this issue. At least I'd expect from Netgear to recover my data free of charge, in case that fails they could refer me to my backup responsibility. Anyone from Netgear able to help me on this ? Thx, MaxSolved3.3KViews0likes3Comments6.4.0 with RN104 - No Longer Shuts Down. Any Ideas?
Hey Guys, Ive been using My RN104 for a while, but since upgrading the firmware as per the login page the ReadyNas no longer shuts down. Ive tried the pressing the power button and follow the on display prompt to shut it down. It would appear that it does shut down as the HDD's turn off but the PSU fan keeps spinning with a Shutting message on the LCD display (Went a way for a few days and it was still shutting down). It was working fine with the previous FW and there have been no extra apps installed on this NAS as its basically a FTP/backup server Also with this issue is causing the auto on/off function not to work any more. Does any one else havethis issue or any idea on how to resolve this? Many thanks, Aaron2.9KViews0likes3Comments