Readynas 104 drops out when copying to it

The response will be please wait until the next firmware is released... in the meantime, congratulations on owning a boat anchor... and how many hours did you spend building the array (twice), copying the data on (twice), and then when the firmware is finally released... woohoo, you get to do it for a third time.

Agree with Perkij, many hours have been wasted.
Just my log of everything I’ve done/conversation with support is now 23 pages long (MS Word statistics says its 3264 words).

with EXT4 mine is very stable! :D

The biggest problem i have with it is that i own it for 9 months, paid good money for it and it is still in beta fase.
I've had gear before with beta status, but those where for free and i was beta tester, but i knew about the beta status all the time.
As reward they could sent a free 314 for all the beta testing whe have been doing :D

:thumbsup: :thumbsup: :thumbsup: :thumbsup:

Just got a Ready NAS 104 in October with 4 brand new Seagate 4TB NAS Drives. I'm just testing out the NAS for last few weeks and when I started to actually load some data onto it (1TB of data) I got the issue where it dropped out during last bit of the copy (as reported in this thread) resulting in me having to pull the power of the NAS to get it going again although I could ping it just fine.

Now the antivirus was on and I had a folder with 30GB worth of pictures videos that was set to take daily snapshots for 9 days. Turned off the antivirus, turned off the snapshots on all shares and deleted all the snapshot data.

Now I'm trying to get this NAS to above 70% capacity to see if I get this issue again but so far I have 4.34TB of data with 2.92TB (total capacity on NAS = 7.26TB) free and haven't had the drop out issue occur again or come back. What I am doing is copying the 1TB of data I originally tried copying to the NAS over and over again till I get to about 90% capacity to see if anything odd happens.

Some changes I made from my original attempt are that I went from using the standard Windows 7 explorer to transfer the file and instead use Teracopy.

I am Running Raid 10 using SMB.

Been doing these transfers for the last 2 days and am on the 5th copy of the 1TB of data and so far no issues. But I will wait till I get past 70% capacity ad see what happens from there.

When the 6.1.5 is released will the ready NAS automatically alert us or will this be an update we need to manually request it?

PS. I haven't contacted netgear support yet but will if the issue comes back.

satz404 wrote:
with EXT4 mine is very stable! :D

How did you migrate from BTRFS to EXT4? I've seen zero documentation and/or howto's on doing this. I'd love to give it a try though.

dishmagic66 wrote:
The biggest problem i have with it is that i own it for 9 months, paid good money for it and it is still in beta fase. I've had gear before with beta status, but those where for free and i was beta tester, but i knew about the beta status all the time. As reward they could sent a free 314 for all the beta testing whe have been doing :D

A free 314? Why, so you could have the same issues with a more expensive NAS? I have a 314 and experience the EXACT same issues that I have with my 2 104's.

As Rebby says and is my understanding from talking with 3rd level support, there is a fundamental flaw in BTRFS file system. There is no work around and every Netgear NAS that uses that file system will fail at some point.

So certainly swapping to EXT4 will solve the problem... satz404, maybe you can post how you did it... and then explain it to the Netgear developers and fix their problem for them!

Dishmagic66... 'reward' is not the right word to use... Compensation on the other hand is entirely appropriate given how much time we've all wasted on a failed product. They all seem to have their heads up their asses and can't see the damage this is doing to them.

perkij wrote:
So certainly swapping to EXT4 will solve the problem... satz404, maybe you can post how you did it... and then explain it to the Netgear developers and fix their problem for them!

http://www.readynas.com/forum/viewtopic.php?f=65&t=73537&start=30#p411217

With BTRFS you can fillup all of data without problem, but is the "write speed" the downside: if your speed is slow (2-3 MB/s) you can fillup, if your speed is bigger (like 35 MB/s) BTRFS become unstable (maybe the CPU is bottleneck).

Mine solutions is the more linear and simple (destroy and replace), but you can resize BTRFS partition (commands here: http://askubuntu.com/questions/75120/how-can-i-safely-resize-shrink-a-btrfs-partition) and make a new partition with EXT4. Xeltros have posted a procedure: http://www.readynas.com/forum/posting.php?mode=reply&f=65&t=73537#pr412402

Is not a simple work and can't be done if used space is > 49% but maybe it work!

Regards Satz404

If you can resize ext4 (with resize2fs ?), you can do it in several steps, resize, copy, delete original, resize, etc. All you need is a little more free space than your biggest file size, and a lot of patience...
That said the procedure was intended to replace BTRFS by BTRFS with better parameters, using another filesystem may not work as expected depending on how Netgear did all the interface/scripting.
That's no simple work (at least if you're not a linux adept, and you don't know what is partitioning and mounting), that's exactly why I didn't post any command, I want people to understand what they're doing, there is enough information for you to find the commands easily on the web, but you'll have do this willingly. This way I'm sure you won't be stuck because I just misspelled something (since I won't test on my NAS, can't be sure...).

Problem with EXT4 is that some features depend on BTRFS ; compression, defrag and snapshots at least. To keep that, Netgear would have to get LVM + EXT4 at least, maybe ZFS ? They just aimed the simplest way to do the job, it turned out that they were wrong. BTRFS has a somewhat special status. It's considered stable enough to be default in some linux distribution but is not recommended for professional use (I believe you found out why ;) ).
If you plan to correct the partition scheme manually, you may want to know that the web interface could just stop working entirely depending on how it's implemented. I believe they use BTRFS sub-volumes to create the shares, this way compress and snapshot should be easier to use (this explains why satz couldn't create the shares).