Did all the hard drives pass at least 1 preclear cycle with clean smart reports?

When I did the first preclear it came back with an issue with a drive but it was just a seating issue. I fixed that and did another and it came back all fine.

 

 

Paste a SMART report for the disk into a post.

Renewing a DHCP should not be disruptive so unless something is very broken I don't think that is relevant.

 

Actually, in the 5.x candidate releases I found that it was.  When the IP renew occurred, it would reset SAMBA, even if it kept the same IP.  My solution was to hard code the IP, no more problems.

Okay little update and this should probably be moved to the os version 6

 

I got all my drives finally pre-cleared and formatted.

I am starting to move my files over and I am still having the same issue. Funny part is it don't matter if it is a file or a folder. If I move a large folder with large files one of them will will make me skip it.

I am starting to wonder if it is a Ethernet switch problem.

 

The switch I have is the TP-SG1016D

I am on average getting on full good transfer 95 MB/second

The most I have seen is 104 MB/second

Forgetting the red ball issue, which is another problem entirely.

 

The problem you are describing is a well known bug in the implementation of the Reiser file system on some platforms, not just unRAID (but it fails "safe" so it's never been fixed).

 

You are probably finding

It occurs on a nearly full disk?

Once it times out and you restart it, it is ok some of the time?

If you have another copy (read or write) running from the same client, that fails also?

 

It will go away in unRAID 6 if you move away from the Reiser file system.

 

 

Forgetting the red ball issue, which is another problem entirely.

 

The problem you are describing is a well known bug in the implementation of the Reiser file system on some platforms, not just unRAID (but it fails "safe" so it's never been fixed).

 

You are probably finding

It occurs on a nearly full disk?

Once it times out and you restart it, it is ok some of the time?

If you have another copy (read or write) running from the same client, that fails also?

 

It will go away in unRAID 6 if you move away from the Reiser file system.

I did a pre-clear so no reball.

I am using unRAID 6.0beta7 now.

The drive is currently 56GB out of 4TB used.

I just hit skip and write the file name down and transfer the file separate and it will work.

I am only doing a transfer from one computer to the server. No other activity is being transfered or read from the server.

 

I would try a different file system.  I suspect your problem might disappear.

I would try a different file system.  I suspect your problem might disappear.

 

This is what the FS is "reiserfs"

There is a problem like you describe in Reiserfs, the work around is you just copy the file again.

 

 

There is a problem like you describe in Reiserfs, the work around is you just copy the file again.

 

But that will become a bigger issue when I start transferring bigger file folders

Come on people. It made me skip a 6kb txt file....

There is a problem like you describe in Reiserfs, the work around is you just copy the file again.

 

But that will become a bigger issue when I start transferring bigger file folders

I have seen the issue you describe if the network plays up for any reason.

 

I have had no problems copying very large amounts of files (~3TB) if I do it internally within the server.  I have found that I can get issues when copying over the network.  If at that point I reset the network hardware (not unRAID) and then tell the copy process to retry it normally proceeds OK.  If I try the same without resetting the network then on a retry the error repeats.  This suggests that in my case at least the issue is in the network and not unRAID.

so switch?

or router?

There is a problem like you describe in Reiserfs, the work around is you just copy the file again.

 

But that will become a bigger issue when I start transferring bigger file folders

 

I have seen this on 3 unRAID servers now.  Yes, it's a pain.  But it fails "safe", you never see it on read, only on write.  I have just got used to going back and recopying all the failures.  I mostly see it when the disk is nearly full.

 

I have read posts on other Linux forums that say this disappears when you change your file system from Reiser to XFS or EXT4.  I should imagine BTRFS is OK too.  I am looking forward to testing it when stable 6 is released.

so should i just change the file systems?

I would replace the switch if its a Trendnet switch. They're known to have some troublesome models. See this posting here:  http://wdtz.org/mysterious-lag-spikes-and-faulty-switches.html

 

After I found that post, I switched my switch and my issues went away. My two coworkers did the same and their similar issues went away too.

The switch I have is the TP-SG1016D

I am on average getting on full good transfer 95 MB/second

The most I have seen is 104 MB/second

Well tested it on a cheapo Netgear FS605 switch and it transfered the file fine. (Granted at a slower speed).

Also tested it on a TP-Link TL-SG1008 switch and it transfered the file fine as well.

 

Connected everything back up to the TP-Link TP-SG1016D and again issue with connectivity.

I am still having an issue on transferring a large file folder. 

 

I just got a Cisco SG200-26 and still having issues transferring large file folders.

 

I know this is in the wrong area now becaues I am using  6.0Beta7.

 

Should i update to beta 8?

 

Also what do I have to do to make this STOP.

Since the symptoms seem to change when you mess with the network, perhaps you have a dodgy piece elsewhere in the chain. Does the symptom stay the same from multiple clients? What happens if you try large transfers from 2 clients at once? Do they both fail, or only 1?

Since the symptoms seem to change when you mess with the network, perhaps you have a dodgy piece elsewhere in the chain. Does the symptom stay the same from multiple clients? What happens if you try large transfers from 2 clients at once? Do they both fail, or only 1?

 

Well the large transfer is coming right from my computer to the server. I could possibility understand if it was going from one server1 to computer to server2. I haven't had any issues like this before in my network. This is why I am so confused.

 

Let me see on transferring the Large file folder to a different server and see what happens.

the files transferred fine to my other server. So now what?

I keep getting redballs on different hard drives and grrrr

what the hell do I have to do to make this thing work other than buy a different mobo.

I have the same issue transferring large files. Did you get this resolved?