this issue has plagued me for a while on every version. is there a reason that everytime i have multiple writes i lose access unraid on my network and have to hard reset? everytime it does this i end up having to do a parity sync again.

this issue has plagued me for a while on every version. is there a reason that everytime i have multiple writes i lose access unraid on my network and have to hard reset? everytime it does this i end up having to do a parity sync again.

 

Without knowing what hardware you are running we cannot give much advice.

 

You have an issue somewhere but who knows were.  Do a memtest first for 8 hours to make sure it checks out.  You may have a marginal NIC in the machine so put in a PCI NIC card and see if that fixes the problem (diable the onboard NIC in the BIOS).

yea i kinda figured that much. ill have to post a hardware profile and syslog tomorrow. its just been a pain in the butt to troubleshoot. mainly wanted to know if there were any quick fixes/known issues/easy answers. ive just been avoiding doing multiple writes because if i troubleshoot and then test to see if it worked and it doesnt, i have to wait another 12 hours or a day or however long it is for the parity check to finish before i try something else that more than likely wont work.

also i dont think its the nic because i have had this issue on more than one mobo and more than one nic both onboard and pci, although now that i think about it it may be the same nic chipset.

Are you able to run parity checks successfully?  If so, then that would likely eliminate the possibility of a suspect PSU.

yes the parity checks complete fine.

I HAVE THIS EXACT SAME PROBLEM!!! I use to be able to write a few files without a problem but as of late I'm having very similar problem, but only when writing 1 file... I started a thread and don't want to hijack yours, but crazy as I'm having similar issues!

Waiting on the hardware profile...

I'm finally not alone! 

 

I have my own thread from a while back that I just bumped, with a little bit of info.

 

What OS are people how are having this problem running?

 

I'm on windows 7 64bit.

Win7-64 bit using teracopy to copy.... never had problems for years. I'm rebuilding parity now as I had to hard reboot and my parity came up blank. Parity rebuild is almost over and I'm going to run a tail on the system log to try and capture the issue....

I'm also using Win7 64 bit with TeraCopy...it all works fine for me.  Everything is pretty stock, too, I haven't tweaked any settings or anything (on either Windows or unRAID).

Waiting on the hardware profile...

 

lol, thanks for your help. got a little distracted

 

 

this is the motherboard i have:

 

GIGABYTE GA-MA790FXT-UD5P

http://www.newegg.com/Product/Product.aspx?Item=N82E16813128377

 

and my hard drives:

parity WDC_WD2002FYPS-0_WD-WCAVY0576318

disk1 WDC_WD4000KD-19N_WD-WMAMY1546033

disk2 Not installed

disk3 ST3750640AS_3QD03V1K

disk4 SAMSUNG_HD753LJ_S13UJDWQ728401

disk5 SAMSUNG_HD753LJ_S13UJ1KQ710938

disk6 WDC_WD10EADS-00L_WD-WCAU47281768

disk7 WDC_WD2002FYPS-0_WD-WCAVY0917427

disk8 WDC_WD2002FYPS-0_WD-WCAVY0239346

disk9 WDC_WD2002FYPS-0_WD-WCAVY0101205

disk10 WDC_WD20EADS-00R_WD-WCAVY122688

 

and my ram:

Crucial 1GB 240-Pin DDR3 SDRAM DDR3 1066 (PC3 8500) Desktop Memory Model CT12864BA1067

http://www.newegg.com/Product/Product.aspx?Item=N82E16820148147

 

i also have a supermicro sata card but i cant remember/find the model. but i have had different motherboards, processors, and ram. always had this issue. the hard drives more or less havent changed unless one fails or i add a new.

 

here is the system log. only shows from the time i just turned it on. i dont know how to get further back if i can.

syslog.txt

also i am using windows 7. ive used other oses before. same issue. if i have two file transfer windows open it does it. maybe the parity drive cant keep or something and crashes the system. i dunno.

maybe the parity drive cant keep or something and crashes the system.

 

I've been having similar issues, and this comment got me thinking about how unRaid could be crashed by the actions of another machine.  Perhaps Windows 7, unRaid, and/or our specific hardware has issues with Flow Control or PAUSE frames (I know very little about either, so these are a bit of a shot in the dark).  The result could be that Windows 7 is simply sending unRaid too much data (compared to how fast a particular unRaid system can write to disk), somehow overwhelming unRaid.  I set my Windows 7 NIC to 10 Mbps and was able to successfully transfer a file that had crashed unRaid on several previous attempts (when my NIC was set to 1 Gbps).  I then tried 100 Mbps with a couple more files from the same set, and that also worked.  For now, I'm going to leave my Windows 7 machine at 100 Mbps and transfer some more files that had been waiting because of this issue.

also i am using windows 7. ive used other oses before. same issue. if i have two file transfer windows open it does it. maybe the parity drive cant keep or something and crashes the system. i dunno.

 

also to clarify a little more, ive transfered large amounts of data before. hundreds of gbs at once. no issue. but if i copy some files to one directory on unraid and copy more files to unraid while the others are still copying, after a few minutes its screwed up. really inconvenient. i just avoid it because troubleshooting means waiting hours on end each time for parity check to finish.

also i am using windows 7. ive used other oses before. same issue. if i have two file transfer windows open it does it. maybe the parity drive cant keep or something and crashes the system. i dunno.

 

also to clarify a little more, ive transfered large amounts of data before. hundreds of gbs at once. no issue. but if i copy some files to one directory on unraid and copy more files to unraid while the others are still copying, after a few minutes its screwed up. really inconvenient. i just avoid it because troubleshooting means waiting hours on end each time for parity check to finish.

It sounds more like you are reaching a limit on the number of "open" files.  Perhaps Windows7 is not closing the files after copying them?

 

Once the system wide limit on open file descriptors is reached, nothing is predictable... (and the server will probably soon crash if a critical process cannot open a new file.)

 

There are two different limits... one for Linux itself, the other in SAMBA.

 

In smb-extra.conf, in a "[global]" section, you might try:

 

[global]

max open files=40000

 

At the linux command line level, to see the current limit type:

cat /proc/sys/fs/file-max

 

To see what is used, type:

cat /proc/sys/fs/file-nr

 

For more info (and how to interpert the resulting output from the above command, look here:

http://www.netadmintools.com/art295.html