• Posts

  • Joined

  • Last visited


  • Gender

Recent Profile Visitors

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

lionceau's Achievements


Rookie (2/14)



  1. Ubuntu 18.04 LTS with all powertop settings on "good" idles at 16W on my Dell T20, Unraid with the exact same hardware idles at 31W for no good reason. CPUs were idle and disks were spun down in both tests. Even with this quite power efficient hardware and 0,28 cent per kWh that's ~37 euros per year or the price of a Tier 2 "Plus" license in two years. I'd rather pay Lime Technology than my power company, it would help save the environment too.
  2. It looks like somebody has recently reverse engineered throttlestop and figured out how to undervolt Haswell and newer CPUs in Linux. Is there any chance this can get ported to unraid, perhaps even as a plugin with a GUI?
  3. Wow LUKS support is a great idea, kudos for focusing on security! If I understand correctly a "xfs encrypted" volume will still be mountable from any Linux distribution that supports LUKS? How about the parity drive, does that also get encrypted or stay plaintext? (I can see arguments for both) Is a mixed mode with encrypted/unencrypted drives in the same array possible? If so am I correct in the assumption that all encrypted devices will have to be unlocked before the array can be started at all?
  4. Ok, I'm at the UPS now and did some research. You're right in that unRAID doesn't control the delay. This "Turn off UPS after shutdown" functionality doesn't work with Cyberpower UPS and should be set to "NO" or you will experience behaviour such as the scheduled hard shutdowns I experienced. There's also no way to change the default 1 hour shutdown delay/schedule, not even in the Windows software or unRAID's apctest. APC units default to 90 seconds. I'm going to do some more research on this considering the poster in the freeNAS forum seems to be able to control this via USB. There's a longer thread here:
  5. The UPS itself doesn't have an option to change this on its LCD, but perhaps there's a way to change this with the Windows software. I've never installed that software (and didn't plan to) but will try it via a VM. As I mentioned the UPS is no longer attached and I'm at the office right now, so I can't debug it any further right now. based on the command list here I do suspect that it's a linux daemon passing the command for the delayed shutdown via USB , perhaps with : Maybe something in the UPS firmware changed and it now expects minutes instead of seconds? Of course I could be wrong and it really is some EEPROM setting stored in the UPS, but then it'd be helpful if the "Turn off UPS after shutdown" setting came with a warning for these cases.
  6. Unfortunately I don't see an option to change anything regarding the "Turn off UPS after shutdown" option. (I'm no longer in the office and detached the UPS for now)
  7. Description: UPS plugin schedules 60 minute (one hour) poweroff after graceful shutdown/halt How to reproduce: execute a graceful UPS shutdown with the "Turn off UPS after shutdown" setting in unRAID enabled and the Cyberpower CP900EPFCLCD connected via USB Expected results: UPS shuts down seconds after computer halts gracefully, enabling the computer to power back on automatically after mains power is restored Actual results: UPS continues running and schedules a hard poweroff 60 minutes (one hour) after computer halts, even if the server is running with mounted filesystems at that point. This schedule also persists through resuming mains-power and — from what I can tell — cannot be canceled with any of the three buttons. A 59 min countdown is displayed on the UPS' LCD screen which automatically turns off after 5 seconds of inactivity. Other information: I have a new Cyberpower CP900EPFCLCD which is detected correctly by unRAID. There's one bug though, the "Power Off UPS" option in the unRAID UPS settings panel schedules a hard power-off n one hour (60 minutes) instead of the presumably intended 60 seconds after halting the computer. This schedule persists through mains-resume/power on and will be executed no matter what. You can probably guess the rest and how I found out about this bug. Can anybody reproduce this? One explanation would be that APC uses seconds and Cyberpower uses minutes as the default unit. I know the feature worked fine with my old APC and shut the UPS down after a minute.
  8. The linux kernel documentation mentions that intel_pstate parameters can indeed be tweaked. Maybe it would be possible to compare the settings and import those from Ubuntu to Unraid? Supposedly it should be possible to set intel_pstate=passive and use all generic governors while retaining intel functionality like turbo p-states, but I tried it in unraid and it only displays the two intel_pstate driver governors (powersave and performance).
  9. I just wanted to say that I'm seeing the same behavior with my Haswell (e3-1225v3) machine. intel_pstate seems to be too aggressive with clocking up compared to acpi-cpufreq. For example I always have a Windows VM idling. acpi-cpufreq with "ondemand" and the default up_threshold 95 (=raises clockspeed when core is above 95% load) throttles the CPU to 800 Mhz and usually to ~1700 Mhz when light load is applied or 3200 Mhz when full load is applied. This gives me very nice power consumption. On the other hand with intel_pstate and "powersave" my cores never drop below 3200 Mhz when the Win VM is idling and idle power consumption raises by 15W. I think it is too aggressive with clocking up, but I can't find the equivalent of up_threshold for the intel driver. this thread seems to describe the problem:
  10. That leaves Facebook, SuSe and Fujitsu as the major BTRFS contributors. This acquisition seems to be related: They intend to open source Permabit's technology. Perhaps XFS will get deduplication and compression in the near future? So far I do not regret my decision of using XFS for all my array and cache drives.
  11. I had problems with something "thrashing" my disk with reads causing one disk to always stay spun up. After some troubleshooting I found that it was cache_dirs plugin. It seems that one of my backup folders contains a large amount of directories, apparently too many to fit into RAM, so cache_dirs read the structure from disk every 10 seconds because the cached structure got evicted in the mean time. This resulted in endless directories reads from disk to memory. Not great. Excluding that folder worked for the most part but some reads were still not cached; now I doubled my RAM, included the folder again and had zero read/write from any disk in the past few hours. Is there any way to figure out how much memory the cached directory structure currently uses?
  12. It looks like somebody found a way to patch the Nvidia driver to remove the virtualization check that causes Error 43. Perhaps this is helpful for some edge cases where people can't dump their BIOS for whatever reason. I have not tried this, attempt at your own risk.
  13. I have updated the original posting. If people affected by the AMD/KVM/NPT bug could take a look at and perhaps comment on it then that'd be great because it would help raise awareness.
  14. Agreed but that's in the KVM developer's hands, there's really nothing the unRAID team can do about it.
  15. Gladly, there are many reports of this in the large Ryzen thread. Thank you for looking into it. There's also an ongoing issue with Nested Page Table performance with KVM and the Zen platform. Disabling it impacts CPU/memory performance negatively, enabling it degrades GPU performance. This does not happen in Xen so that ball is in the KVM maintainer's court. They've recently acknowledged that NPT with AMD needs work but don't have the time to fix it. More details can be found in this thread: Once both of these issues (unRAID-specific C-State crashing and KVM NPT bugfix) are resolved, Ryzen will a great alternative to Intel for unRAID.