Ric878

Hi, I've done some searching on this forum but can't seem to find an answer to my question. Is there a way to limit disk I/O in a given docker? Thanks, Ric

Hi, Not sure if anyone else is having this issue. I am using librenms, which is apparently a fork of observium. The plugin works to get snmp installed and all stats seem to be okay with the exception of ram usage. When looking at my ram usage it shows 99% used. From what I can tell, it is reporting the used ram + the cached ram, which in unRAID is essentially always maxed out. But the reality is that what I, and I assume most of us want to see is the used ram only. Is anyone else experiencing this? Does anyone have a work around? Thanks, Ric

I have removed the the two small ram modules. I will report back on results over the next couple of days. Typically, I have experience the issue within 2 - 4 days. I'm 19 hours in so I will provide an update over the weekend. Thanks

Any new troubleshooting steps or ideas?

Hi, I ran memtest overnight and it showed no errors. Here is a screen shot for reference. Thanks

Here are the results: root@sanserver:/# reiserfsck --check /dev/md1 reiserfsck 3.6.24 Will read-only check consistency of the filesystem on /dev/md1 Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes ########### reiserfsck --check started at Tue Oct 21 17:50:01 2014 ########### Replaying journal: Done. Reiserfs journal '/dev/md1' in blocks [18..8211]: 0 transactions replayed Checking internal tree.. finished Comparing bitmaps..finished Checking Semantic tree: finished No corruptions found There are on the filesystem: Leaves 81653 Internal nodes 496 Directories 82 Other files 139 Data block pointers 82593340 (6651 of them are zero) Safe links 0 ########### reiserfsck finished at Tue Oct 21 17:57:00 2014 ########### root@sanserver:/# reiserfsck --check /dev/md2 reiserfsck 3.6.24 Will read-only check consistency of the filesystem on /dev/md2 Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes ########### reiserfsck --check started at Tue Oct 21 17:58:27 2014 ########### Replaying journal: Done. Reiserfs journal '/dev/md2' in blocks [18..8211]: 0 transactions replayed Checking internal tree.. finished Comparing bitmaps..finished Checking Semantic tree: finished No corruptions found There are on the filesystem: Leaves 75019 Internal nodes 466 Directories 249 Other files 503 Data block pointers 75834063 (0 of them are zero) Safe links 0 ########### reiserfsck finished at Tue Oct 21 18:04:59 2014 ########### root@sanserver:/# reiserfsck --check /dev/md3 reiserfsck 3.6.24 Will read-only check consistency of the filesystem on /dev/md3 Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes ########### reiserfsck --check started at Tue Oct 21 18:10:08 2014 ########### Replaying journal: Done. Reiserfs journal '/dev/md3' in blocks [18..8211]: 0 transactions replayed Checking internal tree.. finished Comparing bitmaps..finished Checking Semantic tree: finished No corruptions found There are on the filesystem: Leaves 59571 Internal nodes 370 Directories 89 Other files 88 Data block pointers 60255795 (0 of them are zero) Safe links 0 ########### reiserfsck finished at Tue Oct 21 18:16:08 2014 ########### root@sanserver:/# reiserfsck --check /dev/md4 reiserfsck 3.6.24 Will read-only check consistency of the filesystem on /dev/md4 Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes ########### reiserfsck --check started at Tue Oct 21 18:18:19 2014 ########### Replaying journal: Done. Reiserfs journal '/dev/md4' in blocks [18..8211]: 0 transactions replayed Checking internal tree.. finished Comparing bitmaps..finished Checking Semantic tree: finished No corruptions found There are on the filesystem: Leaves 564374 Internal nodes 3459 Directories 7099 Other files 32380 Data block pointers 563834737 (0 of them are zero) Safe links 0 ########### reiserfsck finished at Tue Oct 21 19:25:18 2014 ########### root@sanserver:/# reiserfsck --check /dev/md5 reiserfsck 3.6.24 Will read-only check consistency of the filesystem on /dev/md5 Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes ########### reiserfsck --check started at Tue Oct 21 19:36:23 2014 ########### Replaying journal: Done. Reiserfs journal '/dev/md5' in blocks [18..8211]: 0 transactions replayed Checking internal tree.. finished Comparing bitmaps..finished Checking Semantic tree: finished No corruptions found There are on the filesystem: Leaves 71381 Internal nodes 433 Directories 82 Other files 469 Data block pointers 72144355 (0 of them are zero) Safe links 0 ########### reiserfsck finished at Tue Oct 21 19:46:00 2014 ###########

Upgrading now. Didn't realize there was a 10a

Here is the latest syslog. The issue occurred within 30 minutes of this syslog. syslog.7z.zip

Hi, I updated the BIOS to the latest version and still had the same issue. Any other hints?

Here you go. I had to use 7zip to get it small enough so change the extension from zip to .7z Thanks. syslog.7z.zip

Here you go

Hi, Over the last couple of weeks I have been experiencing some issues with my Unraid server which has been rock solid for some time now. I have tried to look at the syslog but am at a loss as to what the issue is. Here are the symptoms: Unraid server becomes partially unresponsive. I am able to ping the server but am not able to access any shares. The web gui is also not responsive. When I try to telnet in I am able to login in successfully but only able to run some commands with success. For example, I can run "ls" "cp" and other basic commands but I tried the shutdown script and it just hangs. Same thing with the basic reboot command. The command prompt indicates that the system is going down but just hangs. If I close the terminal window I can simply log back in. They system never actually reboots. Ultimately I have to perform a hard shutdown and go through the process of parity check. This seems to happen every two days or so at this point. I was able to grab my syslog and have attached it for reference. As the syslog was to large I attached the last few hours of data. Any help would be greatly appreciated. Thanks syslog.txt