joji

Thankyou very much. The scripts are working now. If I may, is there a way to copy over the other files from the source folder. I have collected trialers, subtitles etc. I would like all the files to copy over to the new directory. Thanks in advance.

Hello. I couldn't see any entries on the syslog just before the system crashed everytime. exported it via flash. I just ended up buying a Ryzen 3600 + Asrock B450M and replacing my old Supermicro board. The system has been running stable for close to 4 days now. Once I get a little more time I will try to stress test the old system to see if something was worng with board capcitors may be.

Hello. I am sorry for a question which probably is very noob. I have been running filebot on windows for a while and now have installed the docker on unraid. I don't want to use the AMC script but just want to run some command line scripts. But when I go into the docker console I can't find a way to execut the filebot command. Can someone point me in the right direction please.

Hello. So I just got back home after a 6 months work stint and my unraid server has been having problems during the last 2-3 months. I am going to start toubleshooting but I don't really have many replacement parts, so I thought I will document it here and request support from the pros here. I have been running this for close to a year without any issues. Case: Node 804 Processor / Board / Ram: E3-1220 V2 / X9SCL / 2 x 8GB ECC Drives: 2 x WD120EMFZ (parity) + 8 x 8TB WD Whitelabels Unraid version: 6.8.3 Powersupply: Seasonic focus gold 750 Watt HBA card: LSI SAS2008 Issue # 1. The server restarts randomly. I have tried to disable all my dockers to remove any cpu stress but it doesn't help. I have also tried to leave the array in stopped mode, but it still crashes or restarts. Is it RAM, board? or may be even power supply? I am not sure where to start? Issue # 2. Unraid parity checks throw a lot of errors. Is it because of several crashes that has happened? parity history I am trying to get hold of the server logs and have enabled "Mirror syslog to flash". But I am not sure if upon a random restart, it will append the old syslog file or will start over-writing it? Any suggestions please? Thanks very much for any help in advance. After I reached home 2AM in the morning, the first thing I looked into was my unraid server. I thought I was using an old power supply that might be the culprit. But its not. And I am not really sure how to go about fixing it?