lionceau
-
Posts
70 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by lionceau
-
-
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?
-
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?
-
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:
http://lime-technology.com/forum/index.php?topic=13411.0
-
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 load.off.delay :
https://forums.freenas.org/index.php?threads/cyber-power-systems-cp850pfclcd-working.18673/
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.
-
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)
-
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.
-
The linux kernel documentation mentions that intel_pstate parameters can indeed be tweaked.
https://www.kernel.org/doc/html/latest/admin-guide/pm/intel_pstate.html
Maybe it would be possible to compare the settings and import those from Ubuntu to Unraid?
QuoteTuning Interface in
debugfsThe
powersavealgorithm provided byintel_pstatefor the Core line of processors in the active mode is based on a PID controller whose parameters were chosen to address a number of different use cases at the same time. However, it still is possible to fine-tune it to a specific workload and thedebugfsinterface under/sys/kernel/debug/pstate_snb/is provided for this purpose. [Note that thepstate_snbdirectory will be present only if the specific P-state selection algorithm matching the interface in it actually is in use.]The following files present in that directory can be used to modify the PID controller parameters at run time:
deadbandd_gain_pcti_gain_pctp_gain_pctsample_rate_mssetpointNote, however, that achieving desirable results this way generally requires expert-level understanding of the power vs performance tradeoff, so extra care is recommended when attempting to do that.
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).
-
1
-
-
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:
-
That leaves Facebook, SuSe and Fujitsu as the major BTRFS contributors.
QuoteThe
Btrfsfile system has been in Technology Preview state since the initial release of Red Hat Enterprise Linux 6. Red Hat will not be movingBtrfsto a fully supported feature and it will be removed in a future major release of Red Hat Enterprise Linux.The
Btrfsfile system did receive numerous updates from the upstream in Red Hat Enterprise Linux 7.4 and will remain available in the Red Hat Enterprise Linux 7 series. However, this is the last planned update to this feature.Red Hat will continue to invest in future technologies to address the use cases of our customers, specifically those related to snapshots, compression, NVRAM, and ease of use. We encourage feedback through your Red Hat representative on features and requirements you have for file systems and storage technology.
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.
-
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?
-
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.
https://github.com/sk1080/nvidia-kvm-patcher
I have not tried this, attempt at your own risk.
-
I have updated the original posting.
If people affected by the AMD/KVM/NPT bug could take a look at https://bugzilla.kernel.org/show_bug.cgi?id=196409 and perhaps comment on it then that'd be great because it would help raise awareness.
-
1 hour ago, Josecitox said:
Now we need a fix for the GPU performance and goodbye intel for me
Agreed but that's in the KVM developer's hands, there's really nothing the unRAID team can do about it.
-
7 hours ago, limetech said:
Please add link to this issue.
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: http://www.spinics.net/lists/kvm/msg152343.html
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.
-
On 7/4/2017 at 5:27 PM, Dephcon said:
Ryzen support was added in 4.10 so we're good on that front. It's only the IOMMU optimizations for Ryzen in 4.12 that's an improvement over 4.11... which is only really useful for those doing wiz-bang VM pass-though stuff.
I don't agree with this statement. There's still a unRAID specific bug that makes Ryzen systems crash intermittently unless C-States are disabled in the BIOS. This causes high idle power usage (>100W) because the CPU never clocks down.
-
18 hours ago, JohanSF said:
Paul, thank you for clarifying once more. My strategy is to follow this thread and pull the trigger on an unRAID Ryzen server when you announce that the stability issues have been fixed and not a second before that.
I am in the same position, looking to replace my quadcore Haswell which idles at only 35W, about 40% of what an overclocked Ryzen system seems to consume.
Since Pauven says it's an unRAID specific problem I may just keep my unRAID Haswell system as a strict NAS and build a second Ryzen-based system with a different Linux distribution as my workstation which I'll shut down when it isn't in use.
-
On 6/16/2017 at 3:38 PM, 1812 said:
Link to thread?
Looks like this requries QEMU 2.9.0 to work. The parameters are simple enough to add to the unraid XML, but I haven't updated to 6.4-rc yet.
Once 6.4 is stable and those parameters are confirmed working we should be able to use macOS on unraid with unpatched clover versions.
-
1
-
-
Are Global C-States stable with the new 6.4-rc? It brings a new Kernel that should fix some Ryzen issues.
-
somebody (helgrind over at insanelymac) seems to have found a way around the clover patch, does anybody know how to convert this to unraid compatible XML?
I think I've found a way to avoid the ugly Clover patch: -cpu Penryn,vendor=GenuineIntel,kvm=on,+invtsc,vmware-cpuid-freq=on vmware-cpuid-freq requires kvm to be exposed and invtsc enabled, hence the kvm=on,+invtsc Tested on qemu 2.9.0. -
I'm curious has anybody managed to get Filevault working in a unRAID Sierra VM? It seems like it's working on regular Hackintoshes that support UEFI.
I think it would be really nice to have the disk image encrypted since unRAID itself does not focus on security and might be prone to getting hacked.
-
Does anybody happen to know if this works in unRAID?
https://github.com/r4m0n/ZenStates-Linux
If so, I wonder if some of these options may fix the Global C-State bug at a finer granularity than completely disabling the feature in the BIOS.
-
I guess lime tech is well aware...
-
1
-
-
I'm curious, do these drivers work inside a Windows VM?
http://wccftech.com/amds-new-ryzen-...iency/?utm_source=wccftech&utm_medium=related
-
I feel like fixing the Global C-State and NPT bugs, both issues that look like they could be software related, would go a long way towards making Ryzen attractive for Unraid. A 10-20W idle increase over my quadcore haswell Xeon would be acceptable, but an additional 40-50W of needless idle power consumption and mysteriously crippled multicore VM performance is not.
A shame really, looks like I'll have to wait for Skylake-X/Kabylake-X and lose the ECC support or wait a year or so for the refresh of Ryzen.
Power efficiency compared to other Linux Distributions
in Feature Requests
Posted
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.