NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
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,
Tipster
26 Replies
Replies have been turned off for this discussion
Hi All,
So, and I dont want to jinx it, it would seem that 6.4.2 RC-1 and also the public release (which I manually upated to 5 days ago) have resolved the issue. I am on Day 21 with no hangs of my RN104.
I would strongly recommend upgrading if you haven't done so already. Thank you to all the Netgear staff and mod's for all your advice in the early stages of troubleshooting.
Cheers,
Nick
I thought I'd update people on this.
I'll get this out of the way firstly, we had an EXTREMELY poor L2/L3 support experience with this problem. We have sinced stopped purchasing Netgear ReadyNAS for our clients.
After the original problem happened for the THIRD time (we had tried 2x RN104s and 1x RN204) we realised the thing we had not changed was the drives themselves. Given they were expensive WD Red Pro 6Tb units, we were trying to avoid that.
By having the client note down everyday what was recorded on the front panel we discovered that different drives were dropping off the SATA bus.
We put jumpers on each drive's jumper block to force SATA 3Gbs mode and all has been fine since (touch wood).
Hi All,
So at the suggestion of Support I upgraded to 6.4.2 RC1 and (fingers crossed) I am now on Day 9 of perfect operation. I have now re-enabled Disk Spindown and Balance, Defrag and Scrub schedules on the volume, as these were initial activities that would cause a hang.
I am hopeful that this may be the soultion as RC-1's release notes specifically mention the following;
- [Beta 1] Fixed potential hang due to a race condition when using the CPU's RAID5 offload engine. (RN104)
So far so good, but if that changes I'll let you all know. I have found no other issues with 6.4.2 RC-1 apart from the Disk Temps not displaying under the performance tab on my RN104, which has been reported back to L3 Support.
Cheers,
Nick
So, after 6 days of perfect performance the system hung again yesterday. I contacted support and it is immediately goiing to L3. After pulling the plug on the system, and watching it report 60 hours of resyncing it again has hung today (around 21 hours into the resync). Awaiting L3 support to get in contact but really beginning to feel the RN104 was not the product to purchase.
Will continue to update.
Cheers,
Nick
Hi tipster71,
Thanks for the feedback. I suggest that you continue to work with the L3 Engineer who handles your support ticket. Just update this thread on what happens next.
Kind regards,
BrianL
NETGEAR Community Team
Hi All,
Just thought I would respond at what 'touch wood' has been a solution. I eventually had a few weeks of tooing and frooing with support, inbetween which 6.4.1 was released, which didn't resolve the issue.
Eventually it was escalated to L3 Support (although intitially they refused support as the old ticket had been closed and 90 days had passed since purchase - in their favour they did then provide support as it still was the same issue). After L3 dialled in to my system they then said it was a hardware fault and issued a full hardware replacement. I am now on Day 4 after migrating all disks (succesfully and with all data intact) to the new chassis.
Time will tell, but I will report back if this hasn't resolved the issue.
Cheers,
Nick
Installed 6.4.1. about nine hours ago. System didn't hang yet, but now it's slooooow.
I've gotta be a glutton for punishment.. Just installed 6.4.1 on my working RN102, which still has non important, flushable stuff on it because of the 6.4.0 craziness, and geeze, full lock up of the device. Now I'll have to get home to see if I can access the device and check the logs. Losing faith in ya, Netgear; good thing I didn't install it on my 104..
Tried the final release of 6.4.1 , exactly the same problem got to about 60% reync and poof, locked up again
Actually I wrote: "Actually I think 6.4.0 has never been in beta, so it can't get worse than that."
Since I only thought this, it wasn't really a statement, but an opinion. Therefore it can't be a mis-statement.
But then again: reading and interpreting what you've read is difficult when you have a certain prejudice.
I think you have to forgive customers making comments like that on this forum. We have all been sold a terrible product which isn't remotely fit for purpose or adequately supported. The software is full of glitches and the hardware is inadequate. Support is beyond a joke.
I for one am very surprised that 6.4.0 did indeed have a beta release. How many people actually tried the beta release? How many came back with each of the raised issues? Which issues were still outstanding at time of release? Which features were actually tested by the (brave) beta testers?
It should only take a moment to pull up those answers and post them on this forum. If nobody does that, I will not believe beta testing was actually carried out to any reasonable or acceptable degree. Show me the data. Its very hard to believe adequate testing was done and yet somebody thought it was acceptable to actually release despite the droves of issues beta testing should've raised.
Monkeynut wrote:
I think you have to forgive customers making comments like that on this forum...
I don't work for Netgear; I am a customer. I understand the frustration and I have experienced some problems first hand.
Though I think we are all better off if we can stay focused on the specific problems we're seeing, making sure that Netgear gets clear status back on what problems we've seen, and what we've tried (particularly what is resolved or still broken in 6.4.1-Txx). And making sure that as a community, we share whatever solutions/workarounds that we've found.
In my opinion just sniping at Netgear (though cathartic) doesn't accomplish anything useful, it justs adds noise to the forum.
Monkeynut wrote:
...I for one am very surprised that 6.4.0 did indeed have a beta release. How many people actually tried the beta release?
The public 6.4.0 beta was announced in this forum (https://community.netgear.com/t5/ReadyNAS-Beta-Release/bd-p/readynas-beta-releases?topic-zoom=Public%20ReadyNAS%20OS%206.x%20Beta&sort-by=&date-range=all#all-topics-top), and feedback was provided in this forum. Of course its up to all of us to try the beta releases - there's nothing Netgear can do to force us.
- Hi All,
Thanks JennC. Apologies for the radio silence but have been moving house.
I already have snapshots disabled, but I will try disabling disk spin down, although it would obviously be better if I didn't have to ;-)
I will report back with my findings. Is there any indication of a timeline for 6.4.1 from the engineering team?
I will also give support a shout in case they can shed some light from the logs.I'm not sure its worth phoning the support number, you can save yourself two days of fruststration and simply not bother.
The fact is this is a very common problem and all the well intentioned workarounds are simply not adequate.
Ultimately the 104 is under-powered for what the firmware demands, and the firmware is simply trying to live up to the claims NetGear have made about how great their product is. This situation is likely to only get worse, and us customers will encounter no end of troubles until the device is out of support or end of life and we chuck them in the bin.
Put simply, the device is not fit for purpose. The same issues do not occur with the 204 and 214 which confirms that the device is simply under-powered for the bloated firmware and infefficient feature implementation.
I expect Netgear to offer a replacement unit which is fit for purpose, such as the 204 or 214. Anything short of this is a joke. Its too long Netgear have taken the mickey out of their customers and made them run around an intentionally unworkable black-hole of "support" until customers give up. Too long have they been able to supply inadequate products supported by a raft of products, and relied on other customers to provide workaround solutions (almost always involving shutting off key advertised features), as if this is OK.
Enough is enough, Netgear. Recall this garbage product, re-release it with an entirely different reduced set of functionality claims, and provide existing customers with a product which is actually able to perform as this one was advertised.
I've the same trouble. 1 x RN102 w/2 WD 1TB Greens, and 1 x RN104 w/4 WD 3TB (2Green 2 Red). The 102 seems to be doing better after doing a full factory default reset (all that was on it were personal Time Machine backups), but haven't really tested it hard yet. The 104 tho.. Hoo boy. Locks up during boot, locks up when sitting still doing nothing, locks up when accessing from work, locks up when looked at by my cat, locks up when trying to copy data off the NAS to my external HD (hooked directly to the NAS), locks up when trying to access it thru my Xbox 1, etc. Basically, it just locks up whenever I try to do anything with it.
Right now, I'm having slight success while copying the 104 data to an external HD hooked up to my iMac (SMB seems to work much better than AFP), but it's touch and go. I tried reflashing the FW, as well as reinstalling the OS, but both to no avail. I deleted the snapshots (and managed to save close to a TB of space) as recommended, but that didn't do anything as well. As a side note, I turned off COW as well.. Now I shouldn't have creeping data on my free space after a defrag.
I tried downloading the logs, but it locks up :/
The unit was flawless until the 6.4.0 updates. When I performed the updates, both units locked up on rebooting (no activity on the drives). I had to reflash, etc..
I think I had to just vent a bit. They're not for business use, my NASes (NAE? What should be used for plurial? Lol..) are just home units, and while taking the time to copy everything off the units to reset/default is annoying/frustrating, it's not crucial.. Unless it eats my data, then it's not good.
I'm keeping an eye on the forums to see the progression of people's problems, and hopefully Netgear will have a solution for this quickly. If the reset to fac. defaults does not help in stability, well.. I hope they come out with a new FW quickly!
Thanks JennC,
Been following that thread as well. Not sure I want to try the downgrade just yet, but have followed through with the deletion of the snapshots, and other ideas. Still problematic. Waiting to do a full factory default to see if that will fix everything. Hopefully there'll be a 6.4.1 soon which fixes all these nagging problems.
I'm having the exact same issue. I also have a ReadyNAS 104. Mine has 4 x WD Red 3TB disks, and has been working fine until I took the latest upgrade to 6.4.0.
I first noticed the issue when a balance operation (which I had set on a weekly schedule) was still running 24 hours later, and my ReadyNAS was still on, but could not be accessed via ssh or http, and I could no longer access the files on it. The only option I had was to pull the plug, after which it came up again and tried to do a resync. I could then access the GUI for about 5 mins, before it hung again and I couldn't access any of the services. After I while, I figured out that if I cancelled the balance operation by sshing in quickly after booting, before it hung, I could cancel the balance using the btrfs command. This worked, and after rebooting I was able to get into the GUI without the NAS hanging. I immediately disabled the scheduled maintenance tasks and deleted a bunch of snapshots and all seemed OK. But now I still notice that it hangs every few days and I have to pull the plug to reset it, which results in a full volume resync which takes over 24 hours.
It's very frustrating - clearly something is broken with the 6.4.0 firmware (I've tried flashing a new version from a USB stick in case my image was corrupted, but it didn't make any difference), but as per the release notes, you cannot downgrade again from 6.4.0, so I guess I just have to wait for the next update :-(.
Any suggestions gratefully received!
Same here on a RN204 and RN102 devices so far after update.
The unit would appear in RAIDar initially, then drops off the network after boot, the management page is not available, but it still responds to pings.
In one instance we though the RN102 was faulty so we swapped it out.
Now we have an RN204 that is not accessible with 4 months of snapshots the client may need/want.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
