EDIT BY MODERATOR: Please see the post at the end of the thread: http://www.readynas.com/forum/viewtopic.php?p=456217#p456217I guess i am not the only one this is happening to!everything worked fine for 6.1.9 (except for my root at 99% problem last month)once I updated, I transferred aprox 2 gigs of information it locks up every timeall apps are working fine.as a business owner i have come to the conclusion (with the amount of problems i have been having) ReadyNas is not meant for a reliable means of backing up seems majority of the fixes are "back everything up and factory reset!" I think that answer is as good as telling someone with computer problems to hit there computer a few times and see if it works.now i have gone to support many times yes they are quite helpful but only within 90 days of purchase of the unit! then they insist that i pay for a extension of that support.... i have 3 IBM servers and when there hardware fails (one little problem with a driver one year later) they back up the reseller in making sure my system is back up and running within 48 hours (no they are not leased or have a protection plan) If it wasent for the guys in the forums i would have beaten the system with a bat (please see Office space the movie)... sorry for the rant just truly frustrated with the system :evil:

Hello, I wanted to post the exact same issue... My RN104 worked fine in 6.1.9 and since 6.2.x, it become unreachable ramdomly (frequently) in all way, ping, ssh, raidar, window explorer, web interface..Like moegrease my "90days" is over. It's hallucinating that Netgear forces people to pay to solve issue of their fault... What this maj bring up to do this bug ?I tryed two time os reinstal, the bug is still here. I can't afford to transfer all my data to an other media to factory reset the readynas just as nas Netgear has updated it..Anybody have a way to solve this insupportable issue ?

My boss has instructed me to throw the RN104 in a dumpstersee ya wouldn't want to be ya

Split your post from http://www.readynas.com/forum/viewtopic.php?f=154&t=78534 to make it easier to follow.When your root volume was 99% full it is possible that some of your configuration may have been corrupted or a range of other problems. Only in rare cases would a root volume get full.Updating a system with a root volume that volume is very full is not advisable. Space needs to be freed up on the root volume before updating the firmware.The 104 is a device targeted at the home user. (we would recommend the 300 series and above for business use. The 314 comes with lifetime chat support). We provide a free basic diagnosis check to confirm a hardware issue with the chassis so we can authorise an RMA where that is needed. However all you have said would lead me to believe there is a software issue not a hardware one.When users don't want to purchase an support contract to diagnose software issues, backing up data and doing a factory reset and restoring from backup can be a good solution.

MDGM sorry for the confusing post! i should have clarified that the root situation was cleared up last month by a factory default, but now i have the problem of the ReadyNas now upgraded to 6.2.0 and locking up after a bit of information passes through it! and you are correct it may be a software issue or a issue with the NIC cards but i have no clue! I will keep in mind the 300 series when it is time to upgrade!

Removed your apps, deleted snapshots and disabled CoW on your shares. Doesn't affect existing files, but new files created won't have CoW.Would suggest turning off snapshots on shares you don't need them on. Also check to see that Bitrot protection and CoW are disabled in the UI.

ReadyNas 6.2 (NAS locks up entirely)

327 Replies

Replies have been turned off for this discussion

sparhawk765
Tutor
Feb 10, 2015
Ok, fair enough, I'll give a x-raid or raid-5 a shot and see if it makes any differens, or separate volumes for that matter.
Will report back once I tried them.
dickerj
Aspirant
Feb 10, 2015
The Beta 4 firmware is causing more lockups, I am noticing a few a day now. We really need a way to make these stable soon as I can't rely on this NAS now for my backups (I could all of last year running on the magical 6.1.5 firmware)
sparhawk765
Tutor
Feb 11, 2015
So quick update again, as per recommendation I threw out the raid-0 setup and went with whatever the NAS felt like giving me after a factory-reset.

After the setup-wizard the 104 put my 4 disks in a raid-5 configuration (x-raid2 mode) and started syncing the raid, 2.5% or about an hour in it locked up/froze. This morning before work I pulled the power and rebooted it after which it froze after about 5 min. Rebooted again, Went to work, connected to the NAS (via vnp to my home network) and was about to download the logs when it froze again, around 15 min uptime this time.

Next step seems to be pulling the disks and only using one of them, the non-wd-green one I guess and see what happends. I'm not feeling optimistic.
sauronek
Aspirant
Feb 11, 2015
I'm the "patient zero" first lock up on beta 6.2. Now my NAS working stable 12 hours on day (auto shut down and auto power up 6.2.2) but if i install latest beta 2, 3 lockups on a day. Becaus i have 2 NTFS disk connected on USB this make my disk r/o (dirty bit set) so i looking forward for i hope upcoming fix. (maybe new feature force r/w mount NTFS disk with dirty bit set?).
mdgm-ntgr
NETGEAR Employee Retired
Feb 11, 2015
The nature of these lockups appears to be quite specific to your environments. Otherwise we would have been able to reproduce them.

We are continuing to look into it.

yajdam

Aspirant

Feb 11, 2015

mdgm wrote:
depasseg your issue looks like a different one. Your system has a huge amount of metadata. This could be related to your snapshots or simply related to CoW and fragmentation from using NFS with a high thread count.

mdgm wrote:
depasseg your issue looks like a different one. Your system has a huge amount of metadata. This could be related to your snapshots or simply related to CoW and fragmentation from using NFS with a high thread count.

That metadata was/is done by XBMC/Kodi when it exports it's database as a backup.
As for the snapshots, I've stopped using them since the lockups started.

Looks like you use the NAS as a NFS datastore for VMWare?

No. The NFS was only used to speed things up (a little) on a Raspberry Pi network access and since I replaced the Pi, I'll turn off NFS.

in 6.2.x we have some new configuration options which help with your use case.

Can you tell me what are those options? Maybe I should try them before replying to your PM.

There is no way back to 6.1.9 from 6.2.x. In 6.2.x we have one way upgrades e.g. to snapshots. We have a range of new features, enhancements, bug fixes and security fixes in 6.2.x.

Sorry, mdgm, but this is not for me. I'm one of the few that agrees with you, when you say that rolling back to 6.1.x is not the answer.

Thanks for everything!

mdgm-ntgr
NETGEAR Employee Retired
Feb 11, 2015
yajdam the post you quoted was for depasseg. I don't see an unusual amount of metadata in your logs.

This is what happens when a thread gets big like this. It becomes difficult to tell what is said for whom. Also users may believe they have the same problem as each other and in fact have quite different ones.

NFS should work well, but you do need to lower the thread count to 1 or 2 (under System > Settings > Services > NFS) and in some cases using async can be useful (but you do have to be careful about that: http://kb.netgear.com/app/answers/detail/a_id/14765/~/how-do-disable-nfs-sync-mode-in-readynas-os-6,-to-improve-nfs-performance)

For some use cases CoW and snapshots are not a good idea.

On the 100 series for new shares created on 6.2.x these are off by default.

Disabling them on existing shares will not have the same effect as once a file is created you can't change whether it has CoW or not.

CoW (Copy on Write) is one of the things that makes BTRFS a great filesystem however if you make a huge number of writes to modify existing files then you will get a lot of fragmentation. So you need to choose which shares you use it with and store your data accordingly.

On 6.2.x we link enabling/disabling CoW with enabling/disabling Bitrot protection.
abcd12341
Aspirant
Feb 11, 2015
Since Netgear keep saying they can not reproduce the lockup when there are quite a few people having lockup issues (including mine), why not just replace our units then you can use our faulty one to reproduce the lockup (which seems quite consistent to me).
The unit was fine using fw 6.1.x and I has been telling friends that the 104 was a good buy (how wrong was I - especially the 90 days support part). Now it cost me more to get extra HDD to get the data of it, then wasted a lot of time in testing the unit. As I cannot wait any longer that I have to buy another NAS (non Netgear of course). This means wasted money and time.
Is there anyone out there with good linux knowledge to trick the 6.1.x fw as an upgrade of 6.2.x so we can go back?
mdgm-ntgr
NETGEAR Employee Retired
Feb 11, 2015
If only it was so simple. Take your unit out of your network environment and we will likely find we can't reproduce it with your unit. If we could then we would have resolved the problem by now. Replacing the unit with another would not resolve the issue if it is related to your network environment. If it is a firmware problem a replacement unit will have the same problem in your environment, especially if you move the disks across as the firmware is installed on the disks.

Once we can establish what is causing the lockups we can plan a way forward.

Some user's lockups have been resolved by fixes in the 6.2.3 beta firmware which shows that there are different problems here.

Going back to 6.1.x if it were possible would expose you to bugs and security fixes since then. You would lose enhancements and new features. It's not a solution.
mdgm-ntgr
NETGEAR Employee Retired
Feb 11, 2015
Netgear are working with 2 people who posted in this thread in relation to 100 series and random lock ups. There is nothing apparent seen in the logs so we are collecting info via serial connector.

Netgear do see this as a concern and are investigating with all resources but in our labs we are not seeing the problem.

Forum Discussion

ReadyNas 6.2 (NAS locks up entirely)

327 Replies

Related Content

Entire Dropbox

ReadyNAS NV+ locking HDD

Downstream/Upstream Channel Locking

Weak Wireless Connection Crashes Entire Network

One upstream channel locked - amber light

NETGEAR Academy

ProSupport for Business