ok..been trying to get this this new unraid box up and running consistently. The server seems to be dropping network connection while i'm copying files to it - It's inconsistent as far as timing goes (sometimes I can copy a 20-30 gigs before it kicks me off, other times just a few gigs) When it drops network I can't login via the web, can't telnet or ping it.  The server is still running however, I am able to login from the machine itself. To get it back online I need to reboot it.

 

This only appears to be a problem when i'm copying files, i've left it on for 24 hours with no problems, but not accessing it. I am copying files to Disks and not user shares.

 

things I have done

Assigned Static IP

Turned off disk Spin Down

Turned off all Power Management in the BIOS

Tried to copy to various Drives (happens on all the drives)

Enable active logging - there are no error messages when it goes offline

 

System Setup - all hardware is new except a few hard drives

ASUS P5LD2 R2.0 LGA 775 Intel 945P

Intel Celeron D 331 Prescott 2.66GHz LGA 775

CORSAIR ValueSelect 1GB (2 x 512MB)

5 Drives all IDE - 750 Gig parity / 2 250's and 2 500's

 

I'm starting to run out of ideas... I will post up a syslog when I get home later on today.

 

Any other ideas? or things I can do to narrow it down?

 

Thanks!

 

The next time you have the problem, log into the console and type "ifconfig -a" and post the results here.

The motherboard is listed on the unRAID unofficial wiki (http://lime-technology.com/wiki/index.php?title=Hardware_Compatibility) as compatible.  You might try installing a spare NIC (if you have one) and seeing if the problem continues (don't forget to turn off your onboard NIC).

What version of unraid are you running?

 

 

Bill

FYI

 

I have had the same issue with "loosing network" during large copying or moving of files to the Unraid Server.

 

Using Unraid 4.1- Previously 3.x

 

AMD Athlon 2400

Asus A7N8X deluxe v2

1x512MB Ram or 1 GIG (2x 512)

9 drives -Parity 500 GIG /DATA  3x 500GIG + 5x300GIG

On board NIC _Nvidia only, 3com disabled in bios as serial and other ports.

 

Have tried with NIC 1 GIG from TrendNet and have noticed an improvement, but still having lost network issues.

 

Since I have not had a "reliable" unraid with this motherboard, I am building a replacement system with INTEL chipsets.

 

 

I have the EXACT same problem. And I bought the hardware brand new from Lime Technology. So this is nothing but a MAJOR SOFTWARE PROBLEM as I figure it. I can add, that I access the Unraid from a Mac OS X environment. When writing to a disk, it loses connection randomly. If no solution appears, Lime will have a returned box within shortly.

I've been struggling with this all week as well with my Asus P5LD2 on board Marvell NIC. I don't believe it's a hardware problem because I loaded XP on the machine and copied 1 tera of data into it no problem. Back to unRAID 4.1, same thing, 5 to 10 gig, and the network drops.

 

Yesterday I bought a cheap-o Trendnet 10/100/1000 for $10 and I'm at 250 gig so far without dropping.

Ooooo. This is sooooo bad. (and I'm soooooo annoyed...)

 

I get the "disk1" mounted on my desktop (OS X). I browse around. It disappears. Never to be found again until a reboot of Unraid.

 

PLEASE fix this problem. The software right now is a piece of crap and not even Beta with a problem like that...

 

I *shall* try not to lose my temper, but my expectations were high...and...you know.

Tom *does* read the posts, but I bet he reads his email more frequently.

 

One person could be an anomaly (i.e. bad hardware), but two is a trend.

 

 

Bill

Tom *does* read the posts, but I bet he reads his email more frequently.

 

One person could be an anomaly (i.e. bad hardware), but two is a trend.

 

 

Bill

 

In this thread alone - I count to four! I do not have Tom's email. Nor do I know his position. Übertech developer at Lime? Please forward him a link to this... :-)

Tom posts in almost every thread and identifies himself as the administrator.

 

Tom's email can be found by clicking on his handle, "limetech".

 

If you didn't know that Tom was the one to contact, you certainly could find the support link.

 

[email protected]

 

[email protected]

 

 

Bill

I just upgraded to 4.1 tonight and started to do some file copies, hasn't dropped network yet.

 

I did try copying 1 dvd at a time (4 gigs) and got about 8 or 10 dvd's until it dropped network.

 

the ifconfig -a showed everything working just fine. but am not sure how to export that output to file so I can post it.

 

another tidbit - after the server looses network, I am not able to ping out to any devices on the network..

 

it's like the cable has been pulled..nothing in or out...

 

I think I have an old NIC card lying around, will give that a shot tonight.

We are looking into this.

After upgrading to 4.1 and using the onboard NIC i'm still seeing the same problem..

 

hoping I can swap in a new NIC tonight.

I have the same issues.

 

 

I'm running Version 4.0, Intel GigEth NIC, 2.4 Ghz and 500MB of ram.

 

This issue didn't come up until recently, about two weeks ago.

 

At first I thought the NAS went down and rebooted then another repeat and discovered the NAS is running but I'm not able to find it using \\tower or //tower via browser however reachable via ip \\192.168.0.10 or //192.168.0.10 for web.

 

I've tried various things to figure out what fell asleep at the wheels and still not sure but if I click APPLY in the network Settings of the SETTINGS tab via web browser using IP, it all works again.

 

I've searched the forum and did find one user that ran out of ram and his unRaid started to shut down services on it's own, I've ordered 1GB of ram and plan on adding more just in case but I'm not sure if it's by design to have core apps shut down to free up memory.

 

Well, maybe this might help Tom a little if he hasn't discovered this already.

 

Until then, the work around i've found so far is to refresh the network settings by clicking apply after getting to it via IP.

 

 

-MOla

had this happen again, but didn't have time to reboot right away, so when I got home I checked the syslog before reboot and it looks like it logged something to do with the network. See attached log

Any Estimated Time of Arrival of a fix to this Major Problem yet? My NAS is totally useless in its current state.

tossed in a cheap network card I had lying around last night and so far so good.

Well, I got my 1500 "factory installed" from Tom The Man - and it still sucks. Hereby I therefore bump this thread.

 

Bump.

 

 

Same issue here.

 

My system is original spec, and after "upgrading" to 4.1, I could no longer copy to the UNRaid array from my Windows boxes. Each time I tried, it would lock up the array so hard that it wouldn't respond to shutdown, stop, or kill -9 for individual processes. I'd have to power down manually and wait for the 8+ hour parity check. I checked the rest of the network, and copying to and from other boxes was no problem.

 

After about four days of this, I saw that Corys8646 had success by swapping NICs, so I plugged an IntelPro into the UNRaid..... no luck there, either.

 

So finally, out of sheer frustration, I moved back to UNRaid 3.0 and it's copying like a champ right now from BOTH the onboard NIC and the IntelPro.

 

 

 

 

Hopefully this gets fixed soon. I have spoken to Tom about this problem, and I've had it since I started with unRAID many months ago. It has never really been usable for me I just want a stable NAS that I can read and write to.

 

I'm using An MSI K8NGM2-FID motherboard, with a S939 Opteron 144 and 1GB rab, 3x750GB Seagate 7200.10 SATA2 drives. using onboard NIC and SATA (nVidia 6150 chipset). I was considering building a new system, but not after this thread.

 

I have used 3.0-beta3 up to 4.1 now (and all vers in between), no changes ever, this problem has existed always for me.

Please try the following to see if it solves the 'dropped network' problem.

 

Edit the file 'syslinux.cfg' on the Flash device.  On the line that reads:

 

append initrd=bzroot rootdelay=10

change to

 

append initrd=bzroot rootdelay=10 nolapic

 

Then reboot your server.

 

 

Please try the following to see if it solves the 'dropped network' problem.

 

Edit the file 'syslinux.cfg' on the Flash device.  On the line that reads:

 

append initrd=bzroot rootdelay=10

change to

 

append initrd=bzroot rootdelay=10 nolapic

 

Then reboot your server.

 

 

 

Has anyone that tried this provide some feedback on the results?

 

I'm tempted to un bolt my NAS that's mounted in the garage for this however would be good to have some feedback from those who have had some sucess of improvement. 

 

Thanks,

Mola

 

...I have used 3.0-beta3 up to 4.1 now (and all vers in between), no changes ever, this problem has existed always for me.

 

Tom,  do you know yet whether this problem only affects a small number of users and/or is likely hardware/driver related (nic etc)?

 

I presume there are folks running v4.0 and v4.1 without this problem?

The only time I have been able to reproduce something like this problem, is when testing the s/w by introducing massive numbers of disk errors - there is a memory leak we've tracked down, but I don't think this is causing what most people are posting about in this thread.

 

If system becomes unreachable via network, the way to get the system log is:

1. log in via console (keyboard/monitor)

2. copy the system log to the flash:

  cp  /var/log/syslog  /boot/syslog.txt

3. reboot system

4. send the syslog.txt file to me (it will be in the Flash share).

 

Ultimately the source of this is probably hardware - but not necessarily the NIC, could be a side-effect of something else failing  :'(