Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

[SOLVED] unRAID network blowing up

Featured Replies

  • Author

Well, time to bring this topic back into play.  Soon after I last posted, my issue returned and so I plugged my unRAID server back into my D-link and things worked fine for a month.  Thats great except I want the unRaid plugged into the switch in my rack vs the one outside it as that requires an extra cable. 

 

I thought what the heck, maybe it will work, but no.  When my office machine is plugged to the dlink and the dlink to the trendnet to my unraid, things break.  Unraid locking up is the worst part, but it is the only way I can test.

 

----------------------------

news flash

----------------------------

 

no joke, as I was writing this I began another test, office pc and unraid both in the trendnet.  The transfer was running fine, way past the usual lockup point and suddenly I realized the transfer failed.  unRAID is now unaccessible, so maybe the issue is the trendnet as suspected all along...because others report great success with this unit given its price, the unit is going to be sent tuesday for RMA and I guess we will see what happens when the new unit arrives.  Man, if thats all it is I will be so relieved as my server has been a rock the last month when not connected to the trendnet and it sucks to break uptime over a network device...

 

Sorry for the sudden 180 mid-thought, but when I saw the failure occurred when the trendnet was the only device in play, I thought there was no reason to continue.

 

stay tuned

  • Replies 52
  • Views 13.6k
  • Created
  • Last Reply

This a long shot, a very long shot,  but it worked for me.

 

If any of the other PC's on your network use Win7, AND run on top of an 1155 motherboard, AND you are using the IGP, AND you are trying to drive a TV with it;  then try turning up the core GPU voltage by one notch in the BIOS on the Win 7 machine: in my case it was 0.05 volts.  My Win 7 motherboard is a Gigabyte H67N-USB3-B3.  I found a report stating that this motherboard could not always properly drive a large TV - mine is a 54" Panasonic plasma.  A consequence of the problem was the network collapsed. I don't call 2.5b kb/s a collapsed network, I called it something else (repeatedly).

 

I don't understand how such a problem can occur. But given that the total of my networking knowledge could be scribbled onto the back of my right thumbnail in crayon, I don't expect to.  I do however know that after upping the voltage by 0.05, my problems have disappeared: I have successfully test transferred over 10 terabytes of data. I struggled with this problem for over a week. I used 3 different NIC's, multiple cables, took the Switch (HP Procurve) out of the equation via direct PC to PC ethernet link, changed ethernet settings, etc. etc.

 

Transferring data to the Server via windows explorer now averages out at 35 mb/s with parity on, and 90 mb/s with parity off. I am at this moment 73% through a parity check on a 5 data plus parity drive system: no errors, 94 mb/s and slowing down ever so slightly.  When this completes, I will re-run, then add another 5 drives to the system and repeat.  After a week of frustration, I have regained my humour and am ready to re-join the world.

 

I am a new unRAID user and this is my first post. I am uncomfortable with the term "newbie" (even if it is appropriate), as it conjures up images of youths cavorting in green fields. I stopped cavorting in the 60's. Given my ignorance of protocol, or indeed what may be significant, I shall play safe and detail my server hardware:

 

Motherboard:         ASUS P8 H67-M EV (6 Sata Ports); NIC onboard is a Realtek 8111E           

CPU:               Intel Core i3 2100-T

Memory:             2 x 2 Gb Corsair Dominator

Power Supply:       Seasonic M12II-620 Bronze

Additional Sata:   Supermicro AOC-SASLP-MV8  and ADAPTEC 1430SA

Sata Cables:       Generic - including the  the 8087 breakout cables

Drive Cages:       3 x Norco SS-500

Case:             Zalman MS1000-HS

Drives:           A mixture of the 4 brands to a total of 12 drives

unRAID:             Server Pro 5.0-beta6a on Lexar 2 Gb

  • 4 months later...
  • Author

OK, I want to post back and report this as SOLVED.

 

Turns out that the culprit was my on-board NIC.

 

I installed an Intel NIC and ever since, I have been running clean.  I no longer see the random complete system lockups during transfers.  It has been a few months now that I have been running like this, so I believe it is safe to say it was the NIC in the end.

 

I couldn't be happier to be functioning and stable again.

 

I see my transfers in the 25-30MB/s range.  While not the much higher that others have reported in the past, this seems pretty good to me.  The only other thing I have given thought to is jumbo frames.

 

Any thoughts?

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.