ibasaw

thank you work again !

hi, after update the docker, i got this issue: 2018-09-14 10:34:45,159 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23076737844504 for <Subprocess at 23076737846160 with name sickrage in state STARTING> (stdout)> 2018-09-14 10:34:45,160 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23076738003816 for <Subprocess at 23076737846160 with name sickrage in state STARTING> (stderr)> 2018-09-14 10:34:45,160 INFO exited: sickrage (exit status 2; not expected) 2018-09-14 10:34:45,160 DEBG received SIGCLD indicating a child quit 2018-09-14 10:34:48,166 INFO spawned: 'sickrage' with pid 46 2018-09-14 10:34:48,185 DEBG 'sickrage' stderr output: /usr/sbin/python2: can't open file '/opt/sickrage/SickBeard.py': [Errno 2] No such file or directory 2018-09-14 10:34:48,186 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23076737844504 for <Subprocess at 23076737846160 with name sickrage in state STARTING> (stdout)> 2018-09-14 10:34:48,186 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23076735362040 for <Subprocess at 23076737846160 with name sickrage in state STARTING> (stderr)> 2018-09-14 10:34:48,186 INFO exited: sickrage (exit status 2; not expected) 2018-09-14 10:34:48,186 DEBG received SIGCLD indicating a child quit 2018-09-14 10:34:48,187 INFO gave up: sickrage entered FATAL state, too many start retries too quickly

some news...it happens when the mover is running

very nice, good job for the relooking of the website.

seem to be related to ipmi sensors

ideas ?

the-beast-diagnostics-20180822-1211.zip

hi unraid 6.5.3 pro since few days i got notifications that indicate my cache disk is full...this is totally wrong /dev/sde1 448G 152G 295G 35% /mnt/cache du -h -d 1 /mnt/cache 101G /mnt/cache/system 17G /mnt/cache/appdata 26G /mnt/cache/domains 144G /mnt/cache Why i got this error and notification ?

no overclock, power supply is 2 * 1200 W, but i live in Caraib and i got always 30 °Celsius all the year. I will check in the bios log

hi, i had installed ipmi plugins on my server and see these lines in the logs: 25410 2018-07-29 11:43:11 Sensor #70 OS Critical Stop Run-time Critical Stop ; OEM Event Data2 code = 61h ; OEM Event Data3 code = 74h 25409 2018-07-29 11:43:10 Sensor #0 Memory Correctable memory error ; OEM Event Data2 code = 4Ah ; OEM Event Data3 code = 81h 25408 2018-07-29 11:43:09 Sensor #0 Memory Correctable memory error ; OEM Event Data2 code = 4Ah ; OEM Event Data3 code = 81h 25407 2018-07-29 11:43:09 Sensor #0 Memory Correctable memory error ; OEM Event Data2 code = 4Ah ; OEM Event Data3 code = 81h 25406 2018-07-29 11:43:09 Sensor #0 Memory Correctable memory error ; OEM Event Data2 code = 4Ah ; OEM Event Data3 code = 81h 25405 2018-07-29 11:43:09 Sensor #0 Memory Correctable memory error ; OEM Event Data2 code = 4Ah ; OEM Event Data3 code = 81h 25404 2018-07-29 11:43:09 Sensor #0 Memory Correctable memory error ; OEM Event Data2 code = 4Ah ; OEM Event Data3 code = 81h What is that ? got an issue with a dimm ram ?

thanx

hello i got DUAL INTEL XEON PROCESSOR E5-2690 V2 TEN CORE 25M CACHE 3.0GHz i use a win10 VM and want to attribute only 4 threads for it but on the same physical cpu how to do it here my layer: Pair 1: cpu 0 / cpu 20 Pair 2: cpu 1 / cpu 21 Pair 3: cpu 2 / cpu 22 Pair 4: cpu 3 / cpu 23 Pair 5: cpu 4 / cpu 24 Pair 6: cpu 5 / cpu 25 Pair 7: cpu 6 / cpu 26 Pair 8: cpu 7 / cpu 27 Pair 9: cpu 8 / cpu 28 Pair 10: cpu 9 / cpu 29 Pair 11: cpu 10 / cpu 30 Pair 12: cpu 11 / cpu 31 Pair 13: cpu 12 / cpu 32 Pair 14: cpu 13 / cpu 33 Pair 15: cpu 14 / cpu 34 Pair 16: cpu 15 / cpu 35 Pair 17: cpu 16 / cpu 36 Pair 18: cpu 17 / cpu 37 Pair 19: cpu 18 / cpu 38 Pair 20: cpu 19 / cpu 39 i had configured this 2/22 3/23 is it correct ?

problem solved...

ok i saw it on the plugins Ca fix will try the Troubleshooting Mode

i used the old version, with this one is it safe to move file from /media/dir1 to /media/dir2 ? i used to move file form disk1/dir1 to disk/2/dir1 ++