Jump to content

KidCastro

Members
  • Content Count

    149
  • Joined

  • Last visited

Community Reputation

0 Neutral

About KidCastro

  • Rank
    Advanced Member

Converted

  • Gender
    Male
  • Location
    Sydney Oz
  1. What is one thing that makes you proud and one thing that you look forward to for Unraid?
  2. Thank you @John_M fixed both my issues in one post...
  3. @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?
  4. 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
  5. Thanks for figuring that out, hope someone has an idea, I need to fix this... the errors are happening every 15mins.
  6. 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
  7. 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.
  8. 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
  9. Should I just go to the trusted Intel platform for this upgrade. Intel i5 8400 Asus Prime B365M-A
  10. 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.
  11. 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.
  12. Re-installing stats and no longer getting those errors, how did you know it was stats plugin?
  13. 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