Snorlax

Members
  • Posts

    4
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Snorlax's Achievements

Noob

Noob (1/14)

0

Reputation

  1. I think I found the source of my problem with FAH halting. It has to do with the number of cores being used. https://foldingforum.org/viewtopic.php?f=72&t=31091
  2. My Folding@Home container appears to keep halting. Not sure why, 07:12:54:WU00:FS00:Removing old file './work/00/logfile_01-20191013-064153.txt' 07:12:54:WU00:FS00:Running FahCore: /opt/fah/usr/bin/FAHCoreWrapper /config/cores/cores.foldingathome.org/Linux/AMD64/Core_a7.fah/FahCore_a7 -dir 00 -suffix 01 -version 704 -lifeline 30 -checkpoint 15 -np 23 07:12:54:WU00:FS00:Started FahCore on PID 101 07:12:54:WU00:FS00:Core PID:105 07:12:54:WU00:FS00:FahCore 0xa7 started 07:12:55:WU00:FS00:0xa7:*********************** Log Started 2019-10-13T07:12:54Z *********************** 07:12:55:WU00:FS00:0xa7:************************** Gromacs Folding@home Core *************************** 07:12:55:WU00:FS00:0xa7: Type: 0xa7 07:12:55:WU00:FS00:0xa7: Core: Gromacs 07:12:55:WU00:FS00:0xa7: Website: https://foldingathome.org/ 07:12:55:WU00:FS00:0xa7: Copyright: (c) 2009-2018 foldingathome.org 07:12:55:WU00:FS00:0xa7: Author: Joseph Coffland <[email protected]> 07:12:55:WU00:FS00:0xa7: Args: -dir 00 -suffix 01 -version 704 -lifeline 101 -checkpoint 15 -np 23 07:12:55:WU00:FS00:0xa7: Config: <none> 07:12:55:WU00:FS00:0xa7:************************************ Build ************************************* 07:12:55:WU00:FS00:0xa7: Version: 0.0.17 07:12:55:WU00:FS00:0xa7: Date: Apr 27 2018 07:12:55:WU00:FS00:0xa7: Time: 19:09:25 07:12:55:WU00:FS00:0xa7: Repository: Git 07:12:55:WU00:FS00:0xa7: Revision: 21359963583d09ec2063ef946399441c4df4ccd7 07:12:55:WU00:FS00:0xa7: Branch: master 07:12:55:WU00:FS00:0xa7: Compiler: GNU 6.3.0 20170516 07:12:55:WU00:FS00:0xa7: Options: -std=gnu++98 -O3 -funroll-loops 07:12:55:WU00:FS00:0xa7: Platform: linux2 4.14.0-3-amd64 07:12:55:WU00:FS00:0xa7: Bits: 64 07:12:55:WU00:FS00:0xa7: Mode: Release 07:12:55:WU00:FS00:0xa7: SIMD: sse2 07:12:55:WU00:FS00:0xa7:************************************ System ************************************ 07:12:55:WU00:FS00:0xa7: CPU: Intel(R) Xeon(R) CPU X5670 @ 2.93GHz 07:12:55:WU00:FS00:0xa7: CPU ID: GenuineIntel Family 6 Model 44 Stepping 2 07:12:55:WU00:FS00:0xa7: CPUs: 24 07:12:55:WU00:FS00:0xa7: Memory: 94.48GiB 07:12:55:WU00:FS00:0xa7:Free Memory: 68.20GiB 07:12:55:WU00:FS00:0xa7: Threads: POSIX_THREADS 07:12:55:WU00:FS00:0xa7: OS Version: 4.18 07:12:55:WU00:FS00:0xa7:Has Battery: false 07:12:55:WU00:FS00:0xa7: On Battery: false 07:12:55:WU00:FS00:0xa7: UTC Offset: 0 07:12:55:WU00:FS00:0xa7: PID: 105 07:12:55:WU00:FS00:0xa7: CWD: /config/work 07:12:55:WU00:FS00:0xa7: OS: Linux 4.18.20-unRAID x86_64 07:12:55:WU00:FS00:0xa7: OS Arch: AMD64 07:12:55:WU00:FS00:0xa7:******************************************************************************** 07:12:55:WU00:FS00:0xa7:Project: 14089 (Run 169, Clone 2, Gen 0) 07:12:55:WU00:FS00:0xa7:Unit: 0x000000000002894b5d9248759a580dbd 07:12:55:WU00:FS00:0xa7:Digital signatures verified 07:12:55:WU00:FS00:0xa7:Reducing thread count from 23 to 22 to avoid domain decomposition by a prime number > 3 07:12:55:WU00:FS00:0xa7:Reducing thread count from 22 to 21 to avoid domain decomposition with large prime factor 11 07:12:55:WU00:FS00:0xa7:Calling: mdrun -s frame0.tpr -o frame0.trr -cpt 15 -nt 21 07:12:55:WU00:FS00:0xa7:Steps: first=0 total=1250000 07:13:02:WU00:FS00:0xa7:ERROR: 07:13:02:WU00:FS00:0xa7:ERROR:------------------------------------------------------- 07:13:02:WU00:FS00:0xa7:ERROR:Program GROMACS, VERSION 5.0.4-20161122-4846b12ba-unknown 07:13:02:WU00:FS00:0xa7:ERROR:Source code file: /host/debian-stable-64bit-core-a7-sse-release/gromacs-core/build/gromacs/src/gromacs/mdlib/pme.c, line: 754 07:13:02:WU00:FS00:0xa7:ERROR: 07:13:02:WU00:FS00:0xa7:ERROR:Fatal error: 07:13:02:WU00:FS00:0xa7:ERROR:5 particles communicated to PME rank 4 are more than 2/3 times the cut-off out of the domain decomposition cell of their charge group in dimension y. 07:13:02:WU00:FS00:0xa7:ERROR:This usually means that your system is not well equilibrated. 07:13:02:WU00:FS00:0xa7:ERROR:For more information and tips for troubleshooting, please check the GROMACS 07:13:02:WU00:FS00:0xa7:ERROR:website at http://www.gromacs.org/Documentation/Errors 07:13:02:WU00:FS00:0xa7:ERROR:------------------------------------------------------- 07:13:02:WU00:FS00:0xa7:Completed 1 out of 1250000 steps (0%) 07:13:07:WU00:FS00:0xa7:ERROR: 07:13:07:WU00:FS00:0xa7:ERROR:------------------------------------------------------- 07:13:07:WU00:FS00:0xa7:ERROR:Program GROMACS, VERSION 5.0.4-20161122-4846b12ba-unknown 07:13:07:WU00:FS00:0xa7:ERROR:Source code file: /host/debian-stable-64bit-core-a7-sse-release/gromacs-core/build/gromacs/src/gromacs/mdlib/pme.c, line: 754 07:13:07:WU00:FS00:0xa7:ERROR: 07:13:07:WU00:FS00:0xa7:ERROR:Fatal error: 07:13:07:WU00:FS00:0xa7:ERROR:5 particles communicated to PME rank 5 are more than 2/3 times the cut-off out of the domain decomposition cell of their charge group in dimension x. 07:13:07:WU00:FS00:0xa7:ERROR:This usually means that your system is not well equilibrated. 07:13:07:WU00:FS00:0xa7:ERROR:For more information and tips for troubleshooting, please check the GROMACS 07:13:07:WU00:FS00:0xa7:ERROR:website at http://www.gromacs.org/Documentation/Errors 07:13:07:WU00:FS00:0xa7:ERROR:------------------------------------------------------- 07:13:12:WU00:FS00:0xa7:ERROR: 07:13:12:WU00:FS00:FahCore returned: INTERRUPTED (102 = 0x66)
  3. Did I get the wrong error log portion posted? It's should be there above the screenshot. I also replaced the sata cable with another and moved the hard drive power to another cable coming out of the power supply instead of the same cable run, so hopefully they are different rails now. Nothing changed on the network/switch/router setup from before the upgrades. The section of the network between my PC and the Unraid server shouldn't go to the router anyway. Should just be a couple of gigabit switches.
  4. I just recently upgraded from v5 rc12 or so to v5.0.5, installed some new v5 plugins, replaced my parity drive with a larger (4TB) drive, and put the old parity drive into use as a data drive. Now when I try to transfer a group of files to the server I get a network transfer error 0x8007003B. I think it is something to do with SMB restarting but otherwise I don't really know what is happening. I have tried to remove all the plugins except unmenu in case it was a memory issue but it hasn't helped. I saw another topic that had that error code but it didn't appear to offer a solution. Unraid_Error_Log.txt