Frank1940

Members
  • Content count

    4001
  • Joined

  • Last visited

  • Days Won

    2

Frank1940 last won the day on April 20

Frank1940 had the most liked content!

Community Reputation

96 Good

1 Follower

About Frank1940

  • Rank
    Advanced Member

Converted

  • Gender
    Male
  1. Thanks, I had another look at the diagnostics file and found this in the ifconfig.txt file: eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 10.99.1.12 netmask 255.255.255.0 broadcast 0.0.0.0 ether 0c:c4:7a:a8:64:6e txqueuelen 1000 (Ethernet) RX packets 94508238 bytes 12558573053 (11.6 GiB) RX errors 0 dropped 32445 overruns 0 frame 0 TX packets 741490782 bytes 1086558913298 (1011.9 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 Notice that you have sent out over 1000GB of data over the past four days that your server has been up. Can you explain what is happening as this would represent the playing of some 40 Blu-Ray movies? It seems rather high and could be a contributing factor to what you are experiencing.
  2. Below are the last few entries in your syslog file: Oct 18 16:25:10 FFAEJEANS01 root: error: plugins/preclear.disk/Preclear.php: wrong csrf_token Oct 18 16:26:02 FFAEJEANS01 sudo: root : TTY=pts/0 ; PWD=/root ; USER=root ; COMMAND=/bin/netstat -an Oct 18 16:27:55 FFAEJEANS01 sudo: root : TTY=pts/0 ; PWD=/root ; USER=root ; COMMAND=/bin/netstat --listen Oct 18 16:46:18 FFAEJEANS01 sudo: root : TTY=pts/0 ; PWD=/root ; USER=root ; COMMAND=/bin/netstat -nlp Oct 20 01:01:05 FFAEJEANS01 crond[1689]: exit status 1 from user root [ $(date +%d) -ge 22 -a $(date +%d) -le 28 ] && /usr/local/sbin/mdcmd check &> /dev/null Oct 21 14:57:53 FFAEJEANS01 sshd[980]: Accepted password for root from 10.99.7.39 port 58187 ssh2 Could you provide us with the Date and approximate time when this latest SMB problem occurred? If you look at the syslog file in the diagnostics file that you just uploaded, you will find a lot of lines about "wrong csrf-token". (I have included just one of those lines in this snippet of your syslog.) Here is a link to what that is all about: https://forums.lime-technology.com/topic/46802-faq-for-unraid-v6/?page=2&tab=comments#comment-545988
  3. This appears to a diagnostics file captured right after a reboot. You should try to get one after the problem has occurred. You can get it from the command line by typing diagnostics and the file will will be written to the logs folder/directory on your flash drive.
  4. Dynamix - V6 Plugins

    turn on the 'Help' when looking at the settings for disk caching, Notice what the Help says about " Scan user shares: ". If you are scanning the User Shares, you may be increasing the the amount of memory needed for storage by duplicating the the same info as was in the default disk caching.
  5. Server Hard Crash

    Since no one else has jumped after looking at your picture of the crash, I will propose that you see if you can get a bit more information to the Gurus to work with. Install the Fix Common Problems plugin and turn on the troubleshooting mode. That will write periodic log files to the logs folder/directory of your Flash Drive. After the next crash, up load those files in a new post.
  6. Make sure that your MB is setup to use ACHI mode for disk access and not one of the legacy IDE modes.
  7. Unraid Unresponsive

    Make sure you have turnoff any overclocking features that you may have activated when it was a gaming rig.
  8. Unraid Unresponsive

    IF you did a lot of work inside of the case when you made the conversion, make sure that the tabs on the memory are are in their locked position. (Another user had issues very recently that were traced to this very issue!) Also make sure that all of the fans are working properly and the CPU heatsink is clean. I doubt if either of these are the issue but let's get the easy stuff out of the way first before going into the more esoteric stuff...
  9. Unraid Unresponsive

    OK, if you push the power button on the server for about one second, it should initiate a clean shutdown. (Holding it down for more than three seconds will force an unclean shutdown.) Second, You seem to indicate that the server will come out of this 'coma' after a period of time. Is my assumption of what you wrote true? You should probably run the memtst program (which is on one the option on the unRAID boot menu) for at least 24 hours. Then install the Fix Common Problems plugin and turn on the troubleshooting feature. That will be writing log files to the logs folder/directory on your flash drive. After the problem occurs, post those up on a new post. You can find the plugin here: https://forums.lime-technology.com/topic/47266-plugin-ca-fix-common-problems/ Post up the current diagnostics file ('Tools' >>> 'Diagnostics' ) and perhaps there might be a clue in there about what is going on. Be sure to tell what plugins, Dockers, and VM you are running. Tell how you are using your system. Tell of any access that you allow to your server from the Internet.
  10. I appears that you are spinning your disk down when they are inactive. What is your Default spin down delay: set to? Since the problem seems to start about thirty minutes after you start watching, I would recommend you try 45 minutes or an hour. (I have sometimes observed if the playback application/device stops for 'lack of data', the condition you describe will occur.)
  11. Hopefully, you have 'locks' on the latches. I have always lock mine because I am worried that I (or someone) will inadvertently do exactly what your 15 month old is doing. They really do look inviting...
  12. What I suspect is happening (Completely a mental exercise on my part) is that contiguous blocks of memory are set aside as the OS boots up for the use of these two parameters. Now do a bit of math and you will see that with large amounts of installed RAM, this is a huge number. As you continue to use your server, the the available RAM becomes more and more fragmented over time. Eventually you get to the point where some process requires a block of RAM that is larger then any currently available. Now the OS throws out an OOM warning and selects a process to kill to get more RAM. As long as the process being killed is not necessary at that point and restartable at some later time, all is fine. (In the past, what would occasionally happen is that it would kill off the process that runs the GUI if the GUI hadn't been accessed for a long period of time. Unfortunately, the GUI process that unRAID uses is not restartable and that was a big problem! BTW, the function that these two parameters provide are largely unnecessary because of the way unRAID is generally used and the faster speed of modern hard drives. (In fact, I believe many modern HD's, with their on-board memory and controller, basically do the same function that the process that uses this memory does.)
  13. unRAID becomes unresponsive

    You might provide a list of plugins if it continues to run. Double check that all of your plugins are currently being actively supported.
  14. (SOLVED) LOST

    How much memory is on that server? (unRAID needs at least 2GB to run reliably And does much better with a minimum of 4BG.)
  15. Ethernet port LEDs went blank

    What happened to the lights on the router end of the CAT5 cable which connects to your server? You should also get a the diagnostics file and post it up with your next reply. Either ( 'Tools' >> 'Diagnostics' ) or type diagnostics on the command line and that will write the file to the logs folder/directory on your flash Drive.
Copyright © 2005-2017 Lime Technology, Inc. unRAIDĀ® is a registered trademark of Lime Technology, Inc.