http://pastebin.com/UNa8BDKP

 

I don't understand what's wrong. But this is the result when trying to copy files to one of my unRAID servers.

The samba share will become inactive and I have to hard reset the machine.

You probably have a file-system on one of your disks that has some corruption.

 

/See this wiki link for how to check and repair.

http://lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems

As always, thanks for the fast reply!

So I guess I should go through them one by one (with reiserfsck --check /dev/mdx)?

 

As always, thanks for the fast reply!

So I guess I should go through them one by one (with reiserfsck --check /dev/mdx)?

 

exactly

 

Hmm.. Went through all 14 disks. Not a single problem. More ideas on what may be the cause. Occurs(at least a couple of times a month) without a given pattern (I can't recreate on will).

Hmm.. Went through all 14 disks. Not a single problem. More ideas on what may be the cause. Occurs(at least a couple of times a month) without a given pattern (I can't recreate on will).

Perform a memory test.  You may have problems there  with an occasionally finicky RAM strip. (or it is set with the wrong Voltage timing or clock-speed.

Memtest running for almost 17 hours. No errors so far.

This is a MD-1510/LI server from Lime Technology btw.

 

More tests that can be performed to find the cause?

Memtest running for almost 17 hours. No errors so far.

This is a MD-1510/LI server from Lime Technology btw.

 

More tests that can be performed to find the cause?

Does not sound like memory...  (but at least you know it is not the issue now)

This is becoming more and more common. I have the same problem where when I write to my server it will timeout. It seems that there are a few things that seem to be common:

1. Windows is the OS used for copying

2. 64 bit OS

3. You are using Green drives?

 

Someone stated in another thread that something happens with these Green drives when they get to a certain % of free space remaining. I guess the workaround is to copy over to a drive that has a lot of free space then rsync the files to the other drive.

 

Not sure if this is really the case or not, but I will have more information soon. I believe this is a HUGE problem as I continue to see more and more of these threads popping up complaining about the same issues.

 

I never had this problem until I upgraded to 4.5.6 and I believe it to be something with this release and these HD's. Still trying to prove that theory though...

 

 

1. Yes. Windows 7

2. Yes. 64-bit

3. Yes.

 

And just a couple of GB left on the drives.

 

I have 4.5.4 abut I've seen this on earlier (4.x.x) versions as well.

 

Are you using Teracopy to copy the data to the server?

No, I'm using Explorer.

Any advantage using TeraCopy?

There are tons of advantages to TeraCopy - CRC checks, allows you to pause and resume transfers, faster transfer speeds, etc.

 

For what it's worth, I'm using 64 Bit Win7, and green drives that are 99% full, and TeraCopy and I haven't run into this problem.