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

yajdam
Aspirant
Feb 10, 2015
mdgm. I hope the ReadyNAS Devs aren't taking the easy road and blame the hard drives for a problem that is clearly firmware related.
I have these WD hard drives since day one of my rn104 which came with ReadyNAS... (let me check the box...) 6.0.4 and until 6.2.0 everything worked
without any type of problem, and I thought "This rn104 was a great buy!".

I already tested the hard drives using the ReadyNAS test disks and WD diagnostics tool (one of the first things I did, after starting to have this lock ups) and all tests reported no errors.

Maybe the right road to take is what ReadyNAS devs have done with x86 systems. Forget this kernel and find out if this still happens with the new kernel present in 6.3.3.
So, when will there be a version of 6.3.3 for arm systems?

Thanks for everything, mdgm.
mdgm-ntgr
NETGEAR Employee Retired
Feb 10, 2015
I am not a ReadyNAS dev. I want to rule out disk issues where possible. Not all users may have the same problem even if they think they have.

Disks can and do fail over time.

We do have a hard drive compatibility list to provide direction as to which drives to use. With drives on the compatibility list for current models we don't need to worry about things like Green features of Green disks and potential implications of that for things such as disk spin-down.

There is work on bringing the new kernel to ARM systems. As to when that will be complete I cannot provide an ETA at this time.

We have not abandoned 6.2.x for x86 systems. 6.3.x is early access for x86. It is 6.2.x that will remain the stable line of firmware for x86 for the present.

From 6.0.0 through to the latest 6.2.x release we have been using the same longterm kernel series. I don't think the lockups are a problem with the kernel. If they were then I don't think it would be claimed that the issues only started on 6.2.x.
mdgm-ntgr
NETGEAR Employee Retired
Feb 10, 2015
sparhawk765 I cannot recommend using RAID-0 spanned across mutliple disks. If a disk fails all data is lost.

I would recommend you backup your data and test using X-RAID or RAID-5.

I notice that you too have WD Green disks with a very high load cycle count.

yajdam

Aspirant

Feb 10, 2015

mdgm wrote:

Disks can and do fail over time.

mdgm wrote:
Disks can and do fail over time.

Unfortunately, yes they do and this is one of the reasons why I bought the rn104. The use of RAID5.

We do have a hard drive compatibility list to provide direction as to which drives to use. With drives on the compatibility list for current models we don't need to worry about things like Green features of Green disks and potential implications of that for things such as disk spin-down.

If the model/firmware is that picky with hard drives, then Netgear should place a big sticker on every model, saying something like this: "Before buy, check the hard drives compatibility list.", because the main reason for me to buy a NAS, was to put to some use the 3 wd green 2tb I already had. Had I been warned, I would bought another thing or build my own NAS.
I never used the "disk spin-down" feature.

There is work on bringing the new kernel to ARM systems. As to when that will be complete I cannot provide an ETA at this time.

Glad to hear it. Thanks for the information.

As for the ReadyNAS 6.2.3-T1696 beta 4 in my rn104, don't know why but is worse than T1652. 6 lockups just today... wait... make that 7! Final count for February 10th... 10 lock ups!

Thank you for everything. (As before, I'm not being ironic.)

Rify
Tutor
Feb 10, 2015
I am in exact same situation that yajdam. "My seagate is the issue..." . The problem appears with the 6.2.0 update and Netgear ask me to pay to have a support...
I really don't understand why they do not rollback to 6.1.19 stable code of the firmware ?! Seriously, why don't you provide us a version of old stable code pending you find a solution ? My NAS is off for about 4weeks...
depasseg
Aspirant
Feb 10, 2015
I've got a 516 with 6 Seagate Constellation ES.3's (that came from NETGEAR) and it experiences the recent hanging issue.
mdgm-ntgr
NETGEAR Employee Retired
Feb 10, 2015
yajdam I have sent you a PM.

You can use just about any disk, but disks don't have equal suitability for different uses. Some disks are quite unreliable in RAID arrays and yet great for other use cases.

Anyway clearly for at least many of you it is not the disks that are the problem.

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.
mdgm-ntgr
NETGEAR Employee Retired
Feb 10, 2015
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.

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

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

sparhawk765

Tutor

Feb 10, 2015

mdgm wrote:
sparhawk765 I cannot recommend using RAID-0 spanned across mutliple disks. If a disk fails all data is lost.

I would recommend you backup your data and test using X-RAID or RAID-5.

I notice that you too have WD Green disks with a very high load cycle count.

mdgm wrote:
sparhawk765 I cannot recommend using RAID-0 spanned across mutliple disks. If a disk fails all data is lost. I would recommend you backup your data and test using X-RAID or RAID-5. I notice that you too have WD Green disks with a very high load cycle count.

Ok, once again. I am fully aware of the risks of running a raid-0 and like I have said before unless that itself makes the 104 freeze I don't care. The data is not that important, and in the current state I wouldnt put anything critical on it anyway.

As for the WD Greens, do they make the 104 freeze or could? Or does it just indicate that the disks might be short lives, if the second case, don't care much about that either.

mdgm-ntgr
NETGEAR Employee Retired
Feb 10, 2015
If you don't care about the data a separate volume for each disk would be much better. You are less likely to see lockups with any RAID configuration other than a spanned RAID-0 volume.

The Load Cycle Count issue would affect things like disk spin-down.

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