I just purchased a Ready Nas. I am currerntly doing 4 drives Raid 1 for both. For some reason the transfer rate from windows 10 via SMB to Raid2 fluxuates from 800mbps to 10mbps more towards then 10mbps while copying big files. When copying to Raid 1 speeds are normal. When copying same files to another SMB share transfer rate stays at 900mbps.
Running latest FW and all Gig ethernet. Once in a while it will say not enough storage space when I have lots of space avalable. Any Ideas?
Load the latest Beta Firmware (6.5.0-T2) and tell us if it fixes the issue that you've experienced. I also suggest that you read the ff. articles before upgrading the device Firmware.
It seems like with the FW it has imporoved but still fluxuates between 300mbps to 500mbps when other nas goes about 900mbps solid. Where are the FF notes located? I also noticed that when mapping to the drive it only shows public folders, windows 10 never promps for login unless mapped directly to the permissions only folder. If not logging in and copying to public folder it says not enough space but after logging in everything works. Public folder is open to everyone to read and write.
Can you give us more information of your network topology and the machine you are using to do the test?
Also, can you do a series of random writes(Smaller than 10MB files) vs sync writes (larger than 1GB files) this will give us a bit more data about your network and probably look to trouble shoot a little better.
Also any direct connection to the NAS is a good test with the same series of random writes and sync writes.
Can you help with this?
Thank you very much for your patience while we try to help you resolve this issue.
Are jumbo frames configured on your network? Are you using only one NIC in the NAS or both? What model is the switch? Do you know if 802.3x flow control is enabled on it?
The data sheet includes 802.3x flow control (though it is odd that there isn't a configuration setting to enable/disable it). I'd leave jumbo frames off for now.
It might not be the network at all, but of course we didn't have much information to work with. The fact that the performance is specific to some shares (and not others) suggests that it is not a network problem.
Are the two shares on the same volume? Also, have you checked the SMART stats for the disk? Are snapshot settings the same? Is the fluctuation on reading or writing (or both)?
Running a 4000MB file write on \\192.168.1.164\ ----------------------------- Average (W): 106.59 MB/sec ----------------------------- Running a 4000MB file read on \\192.168.1.164\ ----------------------------- Average (R): 113.23 MB/sec -----------------------------
Raid 2
Running warmup... Running a 4000MB file write on \\192.168.1.164\ ----------------------------- Average (W): 24.59 MB/sec ----------------------------- Running a 4000MB file read on \\192.168.1.164\ ----------------------------- Average (R): 72.46 MB/sec -----------------------------
The health on the hard drives are both fine. Anyway to allow to copy to RAM first then to drive ?
I agree you've ruled out the network. Disk I/O is already cached in ram. Though of course you do want the data moved to the disk promptly, otherwise data corruption occurs on power fail/unexpected shutdown.
Does "healthy" drives mean no reallocated/pending sectors and no ATA errors?
How full is the under-performing RAID array? What drive models are you using?
I am using wd red drives 4tb each WD40EFRX. The drives are pretty much empty, I just purchased the NAS and was trying to dump files on when noticing the speed differences. Pretty much the status just says healthy.
Do you think it will make a difference if switching to Black Drives? I know the reds are only 5400rpms. but then again that doesnt solve the reason why only one raid is slower then the other. I reformated the raid again and still same issue.
I wonder if its due to SMB share, I havent tested AFP or anything else yet. I did notice my Windows 10 machine doesnt prompt for login when mapping to the drive. It only displays public folders unless I map directly to a privialaged folder then it promps for login. I also noticed that if I dont force it to login the puclic read/write folders will not allow me to dump big files it says the disk is full, when more then 3TBs are left. Small text files work fine and creating folders.
I did notice my Windows 10 machine doesnt prompt for login when mapping to the drive. It only displays public folders unless I map directly to a privialaged folder then it promps for login.
What happens is that the Windows machine presents you windows logon/password to the NAS when you connect. If that login is accepted by the NAS, then you get whatever permissions are assiociated with the logon. If the username doesn't exist on the NAS, then if guest access is enabled, you'll get that,
If you want full access, then go into the Windows Credential manager, and create a windows credential for the NAS (using the username and the password you want). You'll need to remove (or edit) whatever credentials already stored for the NAS. Note also that the PC treats the NASNAME and the NASIPADDRESS as two different machines. If you access both ways, you'll want to set up both credentials. They can use either different user/passwords if you want.
if I dont force it to login the puclic read/write folders will not allow me to dump big files it says the disk is full, when more then 3TBs are left. Small text files work fine and creating folders.
What firmware are you running? Do you have quotas enabled?
