• Posts

  • Joined

  • Last visited


  • Member Title


  • Gender
  • Location
    Huntingdon, UK

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

S80_UK's Achievements


Collaborator (7/14)




Community Answers

  1. Same for me (I use Brave as my browser mostly). Mostly I was thrown by the unexpected need to use email address instead of user name and only fully realised that after doing a password reset anyway. Had me scratching my head for a few minutes. I don't use MyServers, so I was unaffected by that side (not sure whether I would have been or not...)
  2. The Feb 14th update is working for me. I did have to wait a few seconds for Real-Time stats to appear, and a minute of so for the Last Day option to start showing data, but that seems reasonable. No reboot was needed. No reboot was required. Thank you for your attention on this issue.
  3. I was reading the above and wondered about the power factor too. Is this using the same power supply as the Threadripper build? If it's not, then it might just be that the power factor is different in the new build and the Tasmota device (not sure what that is btw) is reading VA rather than true power in Watts. Some power supplies only manage decent power factor at reasonable loads, and at light loads the readings might be quite misleading. Using a kill-a-watt kind of device that can read both Watts and VA might help clarify what's going on.
  4. Updated two servers, no issues at present. Thank you.
  5. Updated both main and backup servers from 6.11.1 to 6.11.2 without issue. Thank you.
  6. @Johnyb62 - Replying here since I just saw your post on the Parity Check Tuning thread. Providing your system's diagnostics could help, as requested above. But possible causes include... not enough RAM faulty memory (try several passes of Memtest86) possibly overclocked CPU or RAM (easily done if it's a Ryzen CPU since DOCP/XMP defaults are often a CPU memory controller overclock) possibly a power supply issue. A reliable system should not have problems running parity checks without interruption.
  7. This is simple (or confusing, depending on relevant knowledge and experience). (so not how much this will help...) APC and CyberPower use VA ratings for their UPS product naming, not real power in Watts. VA is a measure of the voltage and current capability multiplied together without any regard for the phase relationship between the voltage and current as consumed by the attached load. Depending on the power factor of the load, the current and voltage may be significantly out of phase, and this will mean a lower "real" power is available to the load under such conditions. The "real" power is measured as the product of the voltage and its in-phase current at each point where the voltage is measured. This will always be a lower number than the VA rating (since power factor cannot be greater than 1). (The VA number is sometimes known as the "apparent power".) The UPS has to be designed around the VA rating, since the electronics within need to be able to support both the voltage and current requirements of the load whether they are in phase or not. So for a UPS rated 1500 VA, the maximum load in watts is a lower figure, and the manufacturers are working with a power factor of 0.6 to quote a supported load of 1000 watts for the nominal power figure. In modern PC power supplies, the power factor approaches 1 as the load increases above 20% or so of the power supply's rating. In standby conditions (below 10 watts or so), it is not unusual for the power factor to drop massively, to maybe 0.2 or even 0.1. Note that some plug in power meters (Kill-a-watt style and similar) can read VA and Watts and sometimes Power Factor as separate readings. For domestic users, the electricity meters are normally reading only the real power consumed (the lower figure), not the VA figure and so you will generally only pay for the actual power usage. I found this which is not maths heavy (compared to the Wikipedia articles on the same)... https://www.arrow.com/en/research-and-events/articles/real-vs-reactive-power
  8. I started, also on 4.7, a couple of months before you (my post in your thread - ) Happy Birthday, LimeTech and Unraid. Long may it continue.
  9. OK - that's good news. Thanks for the feedback. But I would still recommend an increase as and when you're able to. Linux uses any unused RAM for caching disk accesses, so you'll most likely find things will run more smoothly with 4GB or 8GB.
  10. I edited my post after your reply - please also see the bit at the end about disabling unneeded Nerdpack modules.
  11. You're trying to run a load of plugins - they are reported as corrupt .tar files - perhaps due to lack of RAM when trying to unpack them. You are running and trying to install just about every option from the Nerdpack - that will be taking a chunk of space. They idea of Nerdpack is to only enable the features actually required. After that is installed just about everything else has problems. If you look through the text file yourself you can see this. I still think this is primarily a lack of RAM. Certainly I would not expect to run any plugins reliably when you have only half the recommended minimum RAM available. First thing I would try is to borrow a bit more RAM from somewhere just to see if that helps - and uninstall Nerdpack, or at least limit the modules that you are enabling.
  12. Like I said, it was a guess based on very little information. If you cannot run diagnostics, you could still post your syslog file for example which might reveal something going wrong.
  13. My guess is that 2GB is the issue. It's very little even without plugins. Things might work, but it would not take much to cause some processes to be killed due to a lack of available memory.
  14. I use Rufus which is also very capable for this kind of task - https://rufus.ie/en/
  15. That looks very suspect. I suspect that the web page may have been hijacked.