NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Readynas 104 drops out when copying to it
I have a readynas 104 configured with four 4tb drives in raid 5. I've managed to copy about 6tb onto the device without issue but now whenever I go to copy something onto the box, lets say a single 4gb file, it starts out ok and will copy around 1gb of the file at 31MB/second but then the connection drops out completely and I get an error message saying:
There is a problem accessing Z:\....
Make sure you are connected to the network and try again.
Now I've obviously mapped drive Z: to the box and when I say it drops out, I can still ping it's IP address. I have tried both NIC's with different cables and in different ports on the router with exactly the same result every time. I am running two other buffalo NAS boxes off the same router and they are working fine.
I can view the files etc over readycloud and check it's performance without problem and in reasonable time, but then as soon as I copy a file over in explorer, readycloud all but freezes and wont let you navigate through the various screens. And once I try to copy a file across I can still view files and directories on the box in explorer, albeit it takes about 30 seconds or so to load each directory which is ridiculous, but before attempting to copy each directory will load almost instantly as you would expect.
Any ideas?
There is a problem accessing Z:\....
Make sure you are connected to the network and try again.
Now I've obviously mapped drive Z: to the box and when I say it drops out, I can still ping it's IP address. I have tried both NIC's with different cables and in different ports on the router with exactly the same result every time. I am running two other buffalo NAS boxes off the same router and they are working fine.
I can view the files etc over readycloud and check it's performance without problem and in reasonable time, but then as soon as I copy a file over in explorer, readycloud all but freezes and wont let you navigate through the various screens. And once I try to copy a file across I can still view files and directories on the box in explorer, albeit it takes about 30 seconds or so to load each directory which is ridiculous, but before attempting to copy each directory will load almost instantly as you would expect.
Any ideas?
153 Replies
Replies have been turned off for this discussion
- Yes i did contact support this morning.
Just came home and the 104 was free.
Copied another file (400MB) and stuck again...
no webif
no share
no ssh - Maybe something broken in the hardware? Let us know what support has to say.
- I don't think of a hardware defect, coz most of the time it frees it self after a very long period and there are allso a lot of other forum members reporting similar problems.
Whe will wait and see - I've tried to change filesystem...
- Moved all my data to another nas (a lot of time, but moved all at 60MB/s)
- deleted array
- recreated array and immediatilly substituted the file system (BRTFS) with EXT4
- waited a lot of time to done the reconstruction (29 H)
- moved back the data (a very lot of time...)
First, the bad news:
- the web gui doesn't support the creation of shares. Don't know why but it return an error with a function (if soneone is interested i can take a screenshot)
- the web gui discard all change made by hand if some service si restarted by gui
- Service like SAMBA, FTP, DLNA MUST be configured by hand
- ssh + systemd is the only way to manage the system
Good news:
- moved back all the data done without any problem by FTP (NAS 2 NAS with cat6 cross cable)
- moved other (2 file, 1 of 19GB and another of 3GB) data from my pc by samba without problem.
Write speed: ~36MB/s
System Load: ~2.5 (is high...)
Conclusions:
EXT4 > BRTFS for this NAS. Maybe on intel core i5 NAS it work like a charm...but on that it slowdown system to become unstable.
For me, no problem to use shell access to edit the system configuration, but for a normal users maybe a BIG TROUBLE.
Regards Satz404
ps: my NAS is a RN104 with 4x 3TB WD RED
ps2: sorry for my bad english!! :P - Something new... RN104 with 6.1.4
Last night i copied a 2.5GB ISO file to the NAS and it locked up after 5 seconds and it took about 6 minutes to free it self.
What's new? I have disabled snapshots on all shares, wich imoproves the behaviour a lot, but not 100% - I've given up and sent mine back... I don't see how Netgear can continue to sell a product that they know doesn't work and apparently can't fix... it's been two months since I opened the case. How long do they seriously expect people to hold onto a product that can't be used... "work with us" they say. For how f'n long I say, I bought it because I had a need for it two months ago, it straight up doesn't work and should be recalled.
Write as many bad reviews as you can. - The issue has been fixed on 6.1.5,
It will release soon,
I tested on RN104, system can fill 100% data.
root@nas-BF-0F-01:~# df /data
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/md127 11706500352 11626707888 77954896 100% /data - evan, this sounds like metadata block size issues, that btrfs added in more recent kernels than the ReadyNAS OS uses to date (3.0 versus 3.4). Is this what 6.1.5 will contain? And if so, like Sparc, that block size change would require a factory default/new volume creation to take advantage of?
Allow metadata blocks larger than the page size (4K). This allows metadata blocks up to 64KB in size. In practice 16K and 32K seem to work best. For workloads with lots of metadata, this cuts down the size of the extent allocation tree dramatically and fragments much less. Btrfs: Metadata blocks bigger than 4KB
Btrfs was designed from the start to support blocks of multiple sizes, but the code wasn't ready and was disabled, so the Btrfs filesystems used as block size the size of a memory page (4KB in x86). In this version, support for metadata blocks bigger than a page size has been re-enabled, so Btrfs can use metadata blocks of up to 64KB in size (16/32KB seem to work better and are recommended). Support is enabled at mkfs time (f.e. mkfs.btrfs -l 32K). These block sizes cut down the size of the extent allocation tree dramatically and fragments much less.
Can I change metadata block size without recreating the filesytem?
No, the value passed to mkfs.btrfs -n SIZE cannot be changed once the filesystem is created. A backup/restore is needed.
Note, that this will likely never be implemented because it would require major updates to the core functionality. - Hi Chirpa,
Yes, you are right. - Hi Evan,
Any idea when 6.1.5 when will be released ?
Also, will have again to have data wiped and copied back ?
In any case, if indeed 6.1.5 makes the RN104 stable, it is more than welcome.
Rgds
Alex
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
