Jump to content

KidCastro

Members
  • Content Count

    152
  • Joined

  • Last visited

Everything posted by KidCastro

  1. Thanks Rick, I also found Xteve but as per the post under that docker page. I can't pass the channels into plex because I cant map them to the correct channel name... do you know what I need to do here?
  2. I cant add the channel mappings? none of them match...? confused... configuration went through fine until trying to add channels to plex.
  3. Hi Rick, I have multiple IPTV entries but none start... also no options to put in M3U file port etc as per the original setup?
  4. What is one thing that makes you proud and one thing that you look forward to for Unraid?
  5. Thank you @John_M fixed both my issues in one post...
  6. @John_M You are a legend I installed Tips and Tweaks and as you said it was set to... CPU Frequency Scaling Driver: Intel Pstate Governor: Performance I set it to Governor: Power Save and now the CPU is scaling down to 800mhz when I'm not doing anything. Every 1.0s: cat /proc/cpuinfo | grep -i mhz HORIZONLAB: Tue May 28 21:48:08 2019 cpu MHz : 800.107 cpu MHz : 800.228 cpu MHz : 800.026 cpu MHz : 800.041 cpu MHz : 800.067 cpu MHz : 800.000 I just want to know why this was set to performance by default and also will this affect performance at all?
  7. Thanks @John_M I reset the Fixed Schedules and my output of crontab -l is below. Is this correct now? I'm not seeing these failed parsing crontab for user root logs as frequent. root@HORIZONLAB:~# crontab -l # If you don't want the output of a cron job mailed to you, you have to direct # any output to /dev/null. We'll do this here since these jobs should run # properly on a newly installed system. If a script fails, run-parts will # mail a notice to root. # # Run the hourly, daily, weekly, and monthly cron jobs. # Jobs that need different timing may be entered into the crontab as before, # but most really don't need greater granularity than this. If the exact # times of the hourly, daily, weekly, and monthly cron jobs do not suit your # needs, feel free to adjust them. # # Run hourly cron jobs at 47 minutes after the hour: 47 * * * * /usr/bin/run-parts /etc/cron.hourly 1> /dev/null # # Run daily cron jobs at 4:40 every day: 40 4 * * * /usr/bin/run-parts /etc/cron.daily 1> /dev/null # # Run weekly cron jobs at 4:30 on the first day of the week: 30 4 * * 0 /usr/bin/run-parts /etc/cron.weekly 1> /dev/null # # Run monthly cron jobs at 4:20 on the first day of the month: 20 4 1 * * /usr/bin/run-parts /etc/cron.monthly 1> /dev/null The only issue I have left is my CPU clock speed is always high even though load is low. Is the command watch -n 1.0 "cat /proc/cpuinfo | grep -i mhz" accurate? Every 1.0s: cat /proc/cpuinfo | grep -i mhz HORIZONLAB: Mon May 27 15:06:03 2019 cpu MHz : 3850.181 cpu MHz : 3806.042 cpu MHz : 3893.782 cpu MHz : 3887.109 cpu MHz : 3454.613 cpu MHz : 3889.451
  8. Thanks for figuring that out, hope someone has an idea, I need to fix this... the errors are happening every 15mins.
  9. root@HORIZONLAB:~# crontab -l # If you don't want the output of a cron job mailed to you, you have to direct # any output to /dev/null. We'll do this here since these jobs should run # properly on a newly installed system. If a script fails, run-parts will # mail a notice to root. # # Run the hourly, daily, weekly, and monthly cron jobs. # Jobs that need different timing may be entered into the crontab as before, # but most really don't need greater granularity than this. If the exact # times of the hourly, daily, weekly, and monthly cron jobs do not suit your # needs, feel free to adjust them. # # Run hourly cron jobs at 47 minutes after the hour: * * * * /usr/bin/run-parts /etc/cron.hourly 1> /dev/null # # Run daily cron jobs at 4:40 every day: * * * /usr/bin/run-parts /etc/cron.daily 1> /dev/null # # Run weekly cron jobs at 4:30 on the first day of the week: * * /usr/bin/run-parts /etc/cron.weekly 1> /dev/null # # Run monthly cron jobs at 4:20 on the first day of the month: * * /usr/bin/run-parts /etc/cron.monthly 1> /dev/null
  10. How can I check this, I haven't played around with scripts before. I have run Unraid for a very long time so maybe I did something a long time ago.
  11. Hi guys I've had this error for over a year, constantly in my logbook... can someone please assist with working out why these keep populating my log. May 25 20:18:01 HORIZONLAB crond[1894]: failed parsing crontab for user root: /usr/bin/run-parts /etc/cron.hourly 1> /dev/null May 25 20:18:01 HORIZONLAB crond[1894]: failed parsing crontab for user root: /usr/bin/run-parts /etc/cron.daily 1> /dev/null May 25 20:18:01 HORIZONLAB crond[1894]: failed parsing crontab for user root: /usr/bin/run-parts /etc/cron.weekly 1> /dev/null May 25 20:18:01 HORIZONLAB crond[1894]: failed parsing crontab for user root: /usr/bin/run-parts /etc/cron.monthly 1> /dev/null May 25 20:33:01 HORIZONLAB crond[1894]: failed parsing crontab for user root: /usr/bin/run-parts /etc/cron.hourly 1> /dev/null May 25 20:33:01 HORIZONLAB crond[1894]: failed parsing crontab for user root: /usr/bin/run-parts /etc/cron.daily 1> /dev/null May 25 20:33:01 HORIZONLAB crond[1894]: failed parsing crontab for user root: /usr/bin/run-parts /etc/cron.weekly 1> /dev/null May 25 20:33:01 HORIZONLAB crond[1894]: failed parsing crontab for user root: /usr/bin/run-parts /etc/cron.monthly 1> /dev/null May 25 20:48:02 HORIZONLAB crond[1894]: failed parsing crontab for user root: /usr/bin/run-parts /etc/cron.hourly 1> /dev/null May 25 20:48:02 HORIZONLAB crond[1894]: failed parsing crontab for user root: /usr/bin/run-parts /etc/cron.daily 1> /dev/null May 25 20:48:02 HORIZONLAB crond[1894]: failed parsing crontab for user root: /usr/bin/run-parts /etc/cron.weekly 1> /dev/null May 25 20:48:02 HORIZONLAB crond[1894]: failed parsing crontab for user root: /usr/bin/run-parts /etc/cron.monthly 1> /dev/null May 25 21:03:02 HORIZONLAB crond[1894]: failed parsing crontab for user root: /usr/bin/run-parts /etc/cron.hourly 1> Also I recently upgraded my motherboard, cpu and ram to i5 8400, Asus B365M-A and 16GB Corsair DDR. My CPU clock is constantly showing high clock speed even though my load doesn't warrant it. Command: watch -n 1.0 "cat /proc/cpuinfo | grep -i mhz" Every 1.0s: cat /proc/cpuinfo | grep -i mhz HORIZONLAB: Sat May 25 22:01:08 2019 cpu MHz : 3838.821 cpu MHz : 3830.289 cpu MHz : 3893.794 cpu MHz : 3869.166 cpu MHz : 3886.809 cpu MHz : 3888.813
  12. Should I just go to the trusted Intel platform for this upgrade. Intel i5 8400 Asus Prime B365M-A
  13. Hi Guys This CPU seems like good value with built in APU, I only want a solid confirmation that it works with Unraid. What is the current state of Ryzen compatibility with Unraid as of May 2019. Are C States still an issue? Will I be able to passthrough graphics card for VM's? I really want an answer before I take the plunge. CPU: Amd Ryzen 5 2400G MB: Asus Prime B450M-A Thanks guys.
  14. Hi Guys I have a very unusual issue with sleep mode, I can wake my unraid sever through power button and WOL magic packet (even remotely). This works really well but the issue I have is after the 2nd or 3rd wake I lose full control of my unraid... its no longer detected on my home network. The only way I can bring it back is by holding the power button and rebooting. I can't even SSH obviously and I dont have any logs because they get deleted once I boot up again. Can you please help me troubleshoot this fault? Screenshot of my settings.
  15. Re-installing stats and no longer getting those errors, how did you know it was stats plugin?
  16. Removing stats plug has stopped the error, that worked but i realy like using stats. i'll have to ask in the right thread. Thank you
  17. I'll try that now Squid, ive attached my syslog as well. server-syslog-20160523-1026.zip
  18. Hi trurl, I searched the forum and didn't find anything related to my issue.. This is worrying. crond[1512]: exit status 127 from user root /usr/lib/sa/sa1 1 1 &> /dev/null
  19. I just updated them now and restarted my machine... No difference
  20. Hi Guys This log statement has been worrying me, every minute on the dot i get the following. Can someone please help me with it? I don't know what it is and what it means. May 22 03:26:01 SERVER crond[1512]: exit status 127 from user root /usr/lib/sa/sa1 1 1 &> /dev/null May 22 03:27:01 SERVER crond[1512]: exit status 127 from user root /usr/lib/sa/sa1 1 1 &> /dev/null May 22 03:28:01 SERVER crond[1512]: exit status 127 from user root /usr/lib/sa/sa1 1 1 &> /dev/null May 22 03:29:01 SERVER crond[1512]: exit status 127 from user root /usr/lib/sa/sa1 1 1 &> /dev/null May 22 03:30:01 SERVER crond[1512]: exit status 127 from user root /usr/lib/sa/sa1 1 1 &> /dev/null May 22 03:31:01 SERVER crond[1512]: exit status 127 from user root /usr/lib/sa/sa1 1 1 &> /dev/null May 22 03:32:01 SERVER crond[1512]: exit status 127 from user root /usr/lib/sa/sa1 1 1 &> /dev/null May 22 03:33:01 SERVER crond[1512]: exit status 127 from user root /usr/lib/sa/sa1 1 1 &> /dev/null May 22 03:34:01 SERVER crond[1512]: exit status 127 from user root /usr/lib/sa/sa1 1 1 &> /dev/null May 22 03:35:01 SERVER crond[1512]: exit status 127 from user root /usr/lib/sa/sa1 1 1 &> /dev/null May 22 03:36:01 SERVER crond[1512]: exit status 127 from user root /usr/lib/sa/sa1 1 1 &> /dev/null Any help is appreciated
  21. Thanks trurl! Will the recreate process use the same file system as the old drive and is there a problem using a mix of xfs and reiserfs in an array?
  22. Replace a Single Disk with a Bigger One 1. Stop the array. 2. Power down the unit. 3. Replace smaller disk with new bigger disk. 4. Power up the unit. 5. Start the array. When you start the array, the system will reconstruct the contents of the original smaller disk onto the new disk. Upon completion, the disk's file system will be expanded to reflect the new size. You can only expand one disk at a time. IS this method redundant now? Stop the array Unassign the old drive, if it's still assigned Power down [ Optional ] Pull the old drive (you may want to leave it installed for Preclearing or testing) Install the new drive Power on Assign the new drive in the slot of the old drive Go to the Main -> Array Operation section Put a check in the Yes, I'm sure checkbox (next to the information indicating the drive will be rebuilt), and click the Start button The rebuild will begin, with hefty disk activity on all drives, lots of writes on the new drive and lots of reads on all other drives All of the contents of the old drive will be copied onto the new drive, making it an exact replacement, except possibly with more capacity than the old drive.