alright so i started this at the end of another thread i was having issues with but decided to create a new one since this is an entirely different issue and my initial problem was fixed.

 

so i've looked through the FAQs and such but can't find anything on this issue though i assume it's just some manner of networking problem.

 

i just built this array, precleared the drives, popped them in and put them all in an array. the drives have been formatted and a parity disk assigned. i enabled user shares and set up a single share so as to transfer my data in before organizing by media type and such.

 

now- here's the problem. i'm able to map the share to windows (see screenshots in attached PDF) and open it, but when i try to drop a file in, it hangs and then comes up with an error (says it can't connect), then the share no longer becomes accessible from 'my computer', i can no longer view the /tower page in a browser window, and the connected telnet session ceases to function. furthermore, it often will crash my network and render the wifi in the house and sometimes ethernet to my other pc useless until i power cycle the router. this has been repeated several times.

 

i ran ethtool and ifconfig commands before and after trying to add the file (and subsequently killing the internet) and got the syslog file from doing so if that is helpful (looks like gibberish to me). i've attached that along with screenshots and brief explanations along the way. please let me know if i can do anything else to evidence this issue! i have no idea.... it seems wild...

 

thank you!

 

EDIT: it won't let me attach the screenshots because they're too big, even when zipping... let me know if i need to upload them independently or something. if they are necessary.

syslog.txt

so... any thoughts?? thanks!

I experienced a similar issue long ago with one of my older server boards. The onboard Nic wasn't entirely compatible with unraid. The web GUI and telnet sessions let me manage my page but as soon as I started a file transfer everything froze. I didn't have a catastrophic network failure with other components like you did. If you have had a stable system for a while I would bet your Nic is failing. If its a new system then I would say your Nic might not be compatible.

Something else to check that happened to me a couple years back, had 2 servers going on the same network just like you do, and i had copied the contents of my flash drive onto the new one. changed the name, but.

What happened to me was, there was a txt config file in there that had the mac address in it, and so it forced the other pc to be using that mac address rather then the built in one on the nic, which then was causing me alot of problems. Just deleted the address out of the config file, and everything was fine, it updated it to the proper mac for that pc nic

Post detailed system specs and remove all add-ons.

If its a new system then I would say your Nic might not be compatible.

 

it's a new system, yeah, components posted below

 

Something else to check that happened to me a couple years back, had 2 servers going on the same network just like you do, and i had copied the contents of my flash drive onto the new one.

 

i don't exactly have two servers running; i just have a separate PC from the server now that used to run the drives as plain old network shares. so it shouldn't be an issue like that. although i formatted the drive on that computer so in theory that could have something to do with it i guess? but i set up unraid in the server box itself so i dont know. i'll have a look at this when i get home today.

 

Post detailed system specs and remove all add-ons.

 

ASUS C60M1-I AMD Fusion APU C-60 (1.0GHz, dual core) AMD Hudson M1 Mini ITX Motherboard/CPU Combo (http://www.newegg.com/Product/Product.aspx?Item=N82E16813131843)

2 x 4gb Gskill ares DDR3

5 x 2tb drives, 4 are samsung spinpoint f4's in array as storage, 1 is WD green as parity drive

XIGMATEK XCP-A400 400W ATX12V Ver2.3 Power Supply

 

brand new unraid build, I only have unmenu and screen installed as add-ons as those were part of the setup process i followed. can remove if it's relevant.

You have relatively new hardware - use the latest RC with the Samba fix instead of the older 4.7

i got the 4.7 since it was marked as "stable" but if the newer version is stable enough then i could upgrade... long as it isn't too much a pain and i dont have to preclear drives again and such i suppose

alright, son of a B.

 

on a whim last night after posting my bump i booted up the server and let it ride (did nothing to it) just to let the parity check finish, wondering if it would work after that. sure enough- it did! copied a file into the share just fine, ran files off of it -- working as i expected it to. so i guess, problem solved (until something goes wrong).

 

now my question is this; i thought i had read that you could use the array/share when it was doing a parity check- is that not the case? because that's the only variable; it seems to be working just fine now. or do you have to wait for the first parity check to go through before being able to copy things in the first time (this was a new build)... i guess what i'm asking is: what did i miss in the setup process?! (but thank you all so much for your help)

 

second question: is it worth upgrading to the newer RC's- i'm currently running the 4.7 release because it was listed as stable.. but is there something i get that i'm missing out on by upgrading? because i should probably do that before copying all my data back into the array i assume.

 

thank you!

I wouldn't say you would be missing out on something. There are some additional plugins you can run on v5RC's. it also offers support for 3TB+ Hard drive support. There is a small hard to find bug in 4.7 that can cause issues when your doing a parity check and writing data to the array. I don't understand the whole thing but I just didn't copy data while doing a parity check. If your data is important stay on 4.7 till 5 final comes out. It is unlikely that you would loose data on the RC's but it is possible.