Another quick update.  Rolled back to beta 12 which was the previous stable version I had.  The issue seems to have resolved by this roll back.  So there is something that changed in beta 14 from beta 12 that introduced this issue.  Unless you want me to gather some specific troubleshooting data, I'm going to leave it on 12.

Your drive which is connected to ATA13.00  (your syslog didn't go back far enough to tell which drive) has some issues. 

 

Thanks, the drive was corrupted, on its last legs I think. Will replace when the new one arrives.

 

Thanks for the help.

6 days later and no issues at all on beta 12

beta 15 is worse.  back to 12

beta 15 is worse.  back to 12

 

Thanks, was just going to ask about beta 15 before upgrading, you have saved me some time.  Does anyone know if this issue is even being worked on?  I'd hate to be stuck at beta 12 forever. 

Yeah, I think I am going to let Beta 15 cook for a while and see what happens.

That said it is acting just like 14 did, only now without any plugins, because everything is built in.

It would be perfect if br0 didn't go down every day.

 

Oh yes, I upgraded my Docker Containers and rebuilt the KVM VMs before br0 went down.

And I know the system was up, I was able to gracefull shutdown from the power button.

So, good news, I stayed up for more than 24 hrs.

Still testing....

That said, I have issues, but those may not be unRaid related.

 

My Build:

Mobo: Gigabyte Technology Co., Ltd. - H61N-USB3

CPU: Intel® Core™ i5-2500K CPU @ 3400

Cache: 64 kB, 6144 kB

Memory: 8192 MB (max. installable capacity 32 GB)

Network:  eth0: 1000Mb/s - Full Duplex

                eth1: 1000Mb/s - Full Duplex [Added after last reboot]

Kernel: Linux 3.19.4-unRAID x86_64 96.0-beta15]

Current Plugins: Only Built-In

 

HDDs: 10TB, currently using 7.23TB across 4 Drives + Parity and SSD Cache Drive

VMs:

Docker: gfjardim/btsync:latest and needo/plex:latest

VMs:

4 vCPU 2GB Ram Win7 VM w/ Media Center and Addons

1 vCPU 512MB Ram Turnkey Linux LAMP VM

 

Network: Fios Quantum Gateway (POS)

This thing stopped doing port forwarding and yesterday crashed.

Only we can screw up the last 10', Verizon

On Reboot the LAMP VM keeps loosing it's network config.

The Win7 VM often feels like it is being pushed to it's MAX CPU wise.

 

So it is possible that my Fears about Beta 15 were unfounded.

 

As always, I am a bad test case.

 

So,

 

I finally made the move to 15 to test.  I didn't even make it past 18 hours before the network puked out on me.  Looks like it's time to go back to 12 again.

 

Exact same symptoms as previous builds.  It appears to still be tied to the bridge interface.

 

 

-- Edit --

Just saw an RC version hit, gonna upgrade to that and see if the bug still exists

Well,

 

RC2 still has the same issues.  Back to Beta 12.  How is it a Release Candidate with a large bug like this?

what is this RC2 ?

this is the second person to do that i thought the latest release is RC1?

 

 

what is this RC2 ?

this is the second person to do that i thought the latest release is RC1?

No - if you go to the Plugins page in the GUI and do a check for updates there is an update to RC2 available.  What there is not is a separate announcement thread in the forum about RC2.

Well,

 

RC2 still has the same issues.  Back to Beta 12.  How is it a Release Candidate with a large bug like this?

 

Realtek NICs are known to have issues with certain hardware.  Using Intel-based NICs guarantee solid experiences.  Some folks have had no issues with Realtek, others have had problems.  Frank1940 recently had issues on a system with Realtek and switching to Intel solved his problem.  Intel NICs are fairly inexpensive.

Intel NICs are fairly inexpensive.

Extra motherboard slots to insert said NIC are not cheap, and may not be available without major case or motherboard changes. If you are taking the position that Realtek NICS are not going to be supported going forward, I suggest you need to be more assertive with specific motherboard recommendations, or at least warn people that if the onboard NIC is realtek, they are not going to be supported, use at their own risk.

 

2 out of my 3 personal PRO licenses are in use on systems with onboard realteks, currently both of those are running old versions of unraid that work fine, one 4.7, one 5.05. They haven't been upgraded because they are production machines, and I can't risk beta software. If it happens that 6 final doesn't support my particular Realtek NIC combination, so be it, but I'm not particularly happy to see the direction this is taking.

 

Is there any way you could offer multiple realtek driver support via some sort of extra download? i.e. If the stock realtek driver doesn't work, unzip this file in the root of your flash drive to try option 2?

Intel NICs are fairly inexpensive.

Extra motherboard slots to insert said NIC are not cheap, and may not be available without major case or motherboard changes. If you are taking the position that Realtek NICS are not going to be supported going forward, I suggest you need to be more assertive with specific motherboard recommendations, or at least warn people that if the onboard NIC is realtek, they are not going to be supported, use at their own risk.

 

2 out of my 3 personal PRO licenses are in use on systems with onboard realteks, currently both of those are running old versions of unraid that work fine, one 4.7, one 5.05. They haven't been upgraded because they are production machines, and I can't risk beta software. If it happens that 6 final doesn't support my particular Realtek NIC combination, so be it, but I'm not particularly happy to see the direction this is taking.

 

Is there any way you could offer multiple realtek driver support via some sort of extra download? i.e. If the stock realtek driver doesn't work, unzip this file in the root of your flash drive to try option 2?

+1

 

even though this does not affect me currently as I already have an intel nic on board. But I don't have any spare slots so if my on board nic did not work I would be looking at major expense.

My username has been taken in vain (Just kidding, jonp) and I thought I ought to jump in.

 

Both of my systems (spec's below)  use about a low end processor as you can still purchase these days and the motherboard were quite inexpensive so they had Realtek NIC on them.  This combination results in playback problems (Video stuttering and audio dropouts) on high bitrate BluRAY ISO's.  It started in beta 15 and is still present in rc2.  ( Although rc2 is marginally better than the earlier releases.)

 

I installed the Intel Network card and all of the playback problems are gone.  HOWEVER, there is  still the remnants of the problems left over.  For example, I upgrade to rc2 about six hours ago, watched ONE 90 minute BluRay movie and now have about 3.5 MILLION drop errors showing up on the 'System Status' part of the Dashboard.  These drop errors only occur when watch a BluRay using my NTV media player.

 

What I think is happening is that the NTV550 is flooding the server with packet requests to assure that the highest possible  data rate is maintained.  This cause the NIC to issue interrupts that later versions of the unRAID OS are not configured to handle.  Since most of the Realtek NIC is software, it responses by not serving up packets is a steady stream.  Apparently, the Intel Network card has some onboard processing and recognizes what is happening to it and simply discards a lot of the duplicate requests.  (PS--- I may be all wet but my research into dropped packets revealed that they really cause no harm but are sometimes indicators of other problems.)

Intel NICs are fairly inexpensive.

Extra motherboard slots to insert said NIC are not cheap, and may not be available without major case or motherboard changes. If you are taking the position that Realtek NICS are not going to be supported going forward, I suggest you need to be more assertive with specific motherboard recommendations, or at least warn people that if the onboard NIC is realtek, they are not going to be supported, use at their own risk.

 

2 out of my 3 personal PRO licenses are in use on systems with onboard realteks, currently both of those are running old versions of unraid that work fine, one 4.7, one 5.05. They haven't been upgraded because they are production machines, and I can't risk beta software. If it happens that 6 final doesn't support my particular Realtek NIC combination, so be it, but I'm not particularly happy to see the direction this is taking.

 

Is there any way you could offer multiple realtek driver support via some sort of extra download? i.e. If the stock realtek driver doesn't work, unzip this file in the root of your flash drive to try option 2?

Both of my production systems are running 6.0RC2 using onboard RealTek NICs (both using driver r8169) without a problem.  (Actually, been running the 6.0B series since beta 7 on both the production servers without an issue)

 

I can't speak for LimeTech, but I would be rather surprised if they drop support for the Realtek NICs.  But, truth be told they do have more issues than the Intel NICs do (and even under Windows with far better driver support than Linux they can be troublesome)

Intel NICs are fairly inexpensive.

Extra motherboard slots to insert said NIC are not cheap, and may not be available without major case or motherboard changes. If you are taking the position that Realtek NICS are not going to be supported going forward, I suggest you need to be more assertive with specific motherboard recommendations, or at least warn people that if the onboard NIC is realtek, they are not going to be supported, use at their own risk.

 

2 out of my 3 personal PRO licenses are in use on systems with onboard realteks, currently both of those are running old versions of unraid that work fine, one 4.7, one 5.05. They haven't been upgraded because they are production machines, and I can't risk beta software. If it happens that 6 final doesn't support my particular Realtek NIC combination, so be it, but I'm not particularly happy to see the direction this is taking.

 

Is there any way you could offer multiple realtek driver support via some sort of extra download? i.e. If the stock realtek driver doesn't work, unzip this file in the root of your flash drive to try option 2?

Both of my production systems are running 6.0RC2 using onboard RealTek NICs (both using driver r8169) without a problem.  (Actually, been running the 6.0B series since beta 7 on both the production servers without an issue)

 

I can't speak for LimeTech, but I would be rather surprised if they drop support for the Realtek NICs.  But, truth be told they do have more issues than the Intel NICs do (and even under Windows with far better driver support than Linux they can be troublesome)

 

Dropping support isn't what we're doing.  That would mean removing the Realtek drivers from our build.  What I'm simply stating here is that MOST issues folks will have with networking and Realtek NICs can be resolved by switching to Intel.  We are not actively investigating Realtek-specific issues because they don't seem to affect a large amount of people (even you state that you have Realtek and have had no issues).

Intel NICs are fairly inexpensive.

Extra motherboard slots to insert said NIC are not cheap, and may not be available without major case or motherboard changes. If you are taking the position that Realtek NICS are not going to be supported going forward, I suggest you need to be more assertive with specific motherboard recommendations, or at least warn people that if the onboard NIC is realtek, they are not going to be supported, use at their own risk.

 

2 out of my 3 personal PRO licenses are in use on systems with onboard realteks, currently both of those are running old versions of unraid that work fine, one 4.7, one 5.05. They haven't been upgraded because they are production machines, and I can't risk beta software. If it happens that 6 final doesn't support my particular Realtek NIC combination, so be it, but I'm not particularly happy to see the direction this is taking.

 

Is there any way you could offer multiple realtek driver support via some sort of extra download? i.e. If the stock realtek driver doesn't work, unzip this file in the root of your flash drive to try option 2?

Both of my production systems are running 6.0RC2 using onboard RealTek NICs (both using driver r8169) without a problem.  (Actually, been running the 6.0B series since beta 7 on both the production servers without an issue)

 

I can't speak for LimeTech, but I would be rather surprised if they drop support for the Realtek NICs.  But, truth be told they do have more issues than the Intel NICs do (and even under Windows with far better driver support than Linux they can be troublesome)

 

Dropping support isn't what we're doing.  That would mean removing the Realtek drivers from our build.  What I'm simply stating here is that MOST issues folks will have with networking and Realtek NICs can be resolved by switching to Intel.  We are not actively investigating Realtek-specific issues because they don't seem to affect a large amount of people (even you state that you have Realtek and have had no issues).

...would be rather surprised if they drop support...

An FYI, we are actively investigating this issue and think it may be related to containers losing network config as well (another thread).  King fetty's feedback (as well as Sparkly in the other thread) has been much appreciated as it helped narrow down several factors for us.  No update to report yet, but we are attempting a few different things to resolve.

Should Realtek NIC's be listed as unsupported hardware given the various occurrences of 'realtek specific issues'. 

Should Realtek NIC's be listed as unsupported hardware given the various occurrences of 'realtek specific issues'.

 

I can't speak for LimeTech, but I think it might be better to qualify the support, something like "we support most Realtek chipsets".  There are quite a few, and most are working OK, if not great.  Naturally, you only hear from those that have a non-working Realtek NIC.

Should Realtek NIC's be listed as unsupported hardware given the various occurrences of 'realtek specific issues'.

 

It's not unsupported, they just don't always work very well.  We have test systems with Realtek that work just fine.  There are certain mobo/cpu/onboard NIC combos that have had problems, and when hardware-specific issues occur, regardless of whether it's a NIC, SATA, Ethernet, or other type of controller, there is little we can do to help fix the problem.  Something as simple as "upgrading the driver" could actually fix problems for some, but create new ones for others.

 

So in short, no, we shouldn't say Realtek is "unsupported" because that would mean (as I think I mentioned in this thread) that we were yanking the drivers for it out of the kernel altogether.

 

The simple truth with any bug, whether hardware or software, if we can't recreate it in our lab, there is a low probability of us fixing it.  We need something we can reproduce in order to track down the nature of the problem and resolve it.

All this fuss over Realtek vs Intel is pointless as the same issues occur on my Intel NIC as well.  I went out and purchased the Intel as requested at the beginning of this thread.  It did not alleviate the issues at all.  The only thing that corrects the issues is to disable bridging support.  Right now in order to get around this, I have purchased a physical NIC for each VM and I am passing through the NIC to each VM.  I tried going the tunneling route instead of physical NICs but it seems the tunnel support is not in the kernel.  The downside of the physical NIC being 2-fold.  1: Usage of all my PCI/USB slots. 2:  Access to the array now has to go through the physical network.

Well, the Realtek vs Intel NIC discussion comes from honestly a large number of other issues that have nothing to do with bridging, but in your situation, this particular issue is unlikely to be hardware specific thanks to the rigorous testing and feedback you've provided. We are actively looking into this still.

Looks like it's fixed in the latest RC.  I've been running solid for a week with bridging enabled.