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.

Memory full? and network problems

Featured Replies

Hi

 

I have some problems with memory running v5.7b

Streaming blu-ray to a PCH-C200 and when I load a new movie it suddenly starts to stutter.

When I look at memory info.

Memory Info

 

(from /usr/bin/free)

 

                   total         used         free        shared    buffers     cached

Mem:       4146316    4018876     127440          0     101492    3723728

-/+ buffers/cache:     193656    3952660

Swap:            0              0             0

 

Attach the syslog

 

Rob

syslog-2011-07-14.txt

No, you're not having memory problems. Your memory is not full. It is being used as buffers/cache (3952660 bytes used as one big huge freaking cache), likely with what you're streaming. Unused memory is wasted memory.

 

Your stuttering issues lie elsewhere. Perhaps network latency or some PCH firmware bug, I read how some streaming devices have bad firmwares with gigabit networking and how putting a switch between it and the fileserver solved the issue.

I have some problems with memory running v5.7b

Streaming blu-ray to a PCH-C200 and when I load a new movie it suddenly starts to stutter.

 

I stream blu-ray to both a C200 and an A200 - I don't have problems with stuttering.  Visit the PCH forums for advice on network configurations for the C200.

Yeah I have no problems with the PCH and bluray. The one time I did it was faulty wiring in the wall.

 

If it is the C200, make sure it is set in 10/100. The GB doesn't always work.

 

Josh

  • Author

Hi Guys

 

I use the PCH-200 a long time with a nas no problem at all so the problem lies in the unraid server.

What is cached in the memory?

I got dropped packets how do I troubleshoot this?

 

Rob

NIC info (from ethtool)

 

Settings for eth0:

Supported ports: [ TP ]

Supported link modes:   10baseT/Half 10baseT/Full

                       100baseT/Half 100baseT/Full

                       1000baseT/Full

Supports auto-negotiation: Yes

Advertised link modes:  10baseT/Half 10baseT/Full

                       100baseT/Half 100baseT/Full

                       1000baseT/Full

Advertised pause frame use: No

Advertised auto-negotiation: Yes

Speed: 1000Mb/s

Duplex: Full

Port: Twisted Pair

PHYAD: 1

Transceiver: internal

Auto-negotiation: on

MDI-X: off

Supports Wake-on: pumbag

Wake-on: g

Current message level: 0x00000001 (1)

Link detected: yes

 

NIC driver info (from ethtool -i)

 

driver: e1000e

version: 1.2.7-k2

firmware-version: 1.9-0

bus-info: 0000:02:00.0

 

Ethernet config info (from ifconfig)

 

eth0      Link encap:Ethernet  HWaddr 00:25:90:32:2a:f4  

         inet addr:192.168.2.40  Bcast:192.168.2.255  Mask:255.255.255.0

         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

         RX packets:219177072 errors:0 dropped:2171 overruns:0 frame:0

         TX packets:129934295 errors:0 dropped:0 overruns:0 carrier:0

         collisions:0 txqueuelen:1000

         RX bytes:3289092643 (3.0 GiB)  TX bytes:3120498277 (2.9 GiB)

         Interrupt:16 Memory:feae0000-feb00000

  • Author

Hi

 

Did an upgrade to 5.09b and problems gone for now.

NIC info (from ethtool)

 

Settings for eth0:

Supported ports: [ TP ]

Supported link modes:  10baseT/Half 10baseT/Full

                        100baseT/Half 100baseT/Full

                        1000baseT/Full

Supports auto-negotiation: Yes

Advertised link modes:  10baseT/Half 10baseT/Full

                        100baseT/Half 100baseT/Full

                        1000baseT/Full

Advertised pause frame use: No

Advertised auto-negotiation: Yes

Speed: 1000Mb/s

Duplex: Full

Port: Twisted Pair

PHYAD: 1

Transceiver: internal

Auto-negotiation: on

MDI-X: on

Supports Wake-on: pumbag

Wake-on: g

Current message level: 0x00000001 (1)

Link detected: yes

 

NIC driver info (from ethtool -i)

 

driver: e1000e

version: 1.2.7-k2

firmware-version: 1.9-0

bus-info: 0000:02:00.0

 

Ethernet config info (from ifconfig)

 

eth0      Link encap:Ethernet  HWaddr 00:25:90:32:2a:f4 

          inet addr:192.168.2.40  Bcast:192.168.2.255  Mask:255.255.255.0

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:574673 errors:0 dropped:0 overruns:0 frame:0

          TX packets:287696 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:58578506 (55.8 MiB)  TX bytes:27873202 (26.5 MiB)

          Interrupt:16 Memory:feae0000-feb00000

 

Memory Info

 

(from /usr/bin/free)

 

                    total        used        free        shared    buffers    cached

Mem:      4146276    285688    3860588          0      4324    216488

-/+ buffers/cache:      64876    4081400

Swap:            0            0          0

 

Rob

What motherboard and nic?

 

Josh

...with 4GB of RAM, you do not have a memory problem in terms of resources.

The syslog looks OK to me, besides the fact that your second NIC does not show.

Did you disable it in the BIOS?

 

That motherboard is a real workhorse. I have two of them running with uptimes

for more than a year, each.

I doubt that your problems will permanently disappear with a simple upgrade of the unRAID SW.

Kernel and drivers have stayed the same. I've been testing v5.b7 with basically the same HW

and have copied over some full arrays, during my other tests, producing very high workloads for days.

 

...my bet is, that there is some glitch in your network wiring.

  • Author

Hi Ford Perfect

 

I try different cables and options but still got dropped packets.

I disabled the second nic with the jumper on board.

Don't understand what's going on it work like  hell and suddenly this stutter began.

Copied 5TB from my nas to the unraid server everything was OK.

As you can see after e fresh reboot I got no network error and after some time it begins.

How can I trouble shoot this?

 

Rob

So you're saying that the problem returned and 5.b9 did not solve it?

 

...can you test with a direct cable? no switch, static IPs between unRAID and media-client?

...swap NICs, disable the first and run the second on-board NIC only.

 

...can you test with a non-beta version (smaller array, max. 2TB drives) like v4.7 ??

  • Author

Hi

 

No it's not solved after upgrade.

First try to use the 2e NIC.

Don't think it's a cable switch problem nothing changed.

 

Rob

It is not very clear.... was it working for en extended period then stopped working?

  • Author

Hi NAS

 

Yes that's correct.

a few days ago I installed cache_dirs and then the trouble starts.

It runs for 1 week with no troubles.

 

Rob

 

 

 

  • Author

Hi

 

Used the second NIC on the MB and that didn't help

NIC info (from ethtool)

 

Settings for eth0:

Supported ports: [ TP ]

Supported link modes:  10baseT/Half 10baseT/Full

                        100baseT/Half 100baseT/Full

                        1000baseT/Full

Supports auto-negotiation: Yes

Advertised link modes:  10baseT/Half 10baseT/Full

                        100baseT/Half 100baseT/Full

                        1000baseT/Full

Advertised pause frame use: No

Advertised auto-negotiation: Yes

Speed: 1000Mb/s

Duplex: Full

Port: Twisted Pair

PHYAD: 1

Transceiver: internal

Auto-negotiation: on

MDI-X: off

Supports Wake-on: pumbag

Wake-on: g

Current message level: 0x00000001 (1)

Link detected: yes

 

NIC driver info (from ethtool -i)

 

driver: e1000e

version: 1.2.7-k2

firmware-version: 1.9-0

bus-info: 0000:02:00.0

 

Ethernet config info (from ifconfig)

 

eth0      Link encap:Ethernet  HWaddr 00:25:90:32:2a:f5 

          inet addr:192.168.2.40  Bcast:192.168.2.255  Mask:255.255.255.0

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:3724903 errors:0 dropped:2843270 overruns:0 frame:0

          TX packets:1670091 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:233267689 (222.4 MiB)  TX bytes:2514272739 (2.3 GiB)

          Interrupt:17 Memory:feae0000-feb00000

Also the memory is into cached alot.

Is that normal?

(from /usr/bin/free)

 

                    total        used          free      shared    buffers    cached

Mem:      4146276    4017188    129088          0    172128    3700664

-/+ buffers/cache:    144396    4001880

Swap:            0            0          0

 

Rob

Yes, Linux will cache as much as it can, this is by design.

Disable cache directories and see if the problem goes away then.

  • Author

Hi lionelhutz

 

Did that but that didn't help

I reboot everything and now it's running smooth but I stil have dropped packets.

 

Rob

First try to use the 2e NIC.

Don't think it's a cable switch problem nothing changed.

 

Your NIC is also part of the components that you did not change  ;)

If you accept a failure of the NIC - because you're going to test with a spare - I suggest

that you consider failure of cables/switch or other parts of your setup as well.

 

It makes sense that you rule out SW parts as well, so return to a config that previously

has proved to be stable.

 

Also the memory is into cached alot.

Is that normal?

(from /usr/bin/free)

 

                    total         used          free       shared    buffers     cached

Mem:       4146276    4017188     129088          0     172128    3700664

-/+ buffers/cache:     144396    4001880

Swap:            0            0           0

 

Yes, that is normal.

I have the same setup with X7SPA-HF mobo and RAM.

It looks like this:

root@unRaid1:~# free
             total       used       free     shared    buffers     cached
Mem:       4146028    4029408     116620          0     341420    3560484
-/+ buffers/cache:     127504    4018524
Swap:      4192956          0    4192956
root@unRaid1:~#

...looks like this since the last reboot, 8 months ago  ;)

 

Cut out the switch/nic if you can to test, even if it has all been working fine in the past.

 

I had a bad wire in the wall that worked fine to months and then started stuttering until I found out it was to do with the wiring in the wall.

 

Josh

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.