cosmas

@JorgeB Thank you, that works now to enable again "ACPI CPU Freq".

@dlandon Thank you for the new version of this plugin. But some settings are missing. At "Normal CPU Scaling Governor" there is missing "Balanced Power". At "Power Saving CPU Scaling Governor" there is missing "Balanced Performance". And the descriptions maybe need to be updated. My CPU does only support "performance" and "power save" :((

@dlandon thank you, that works fine. The driver is now again "ACPI CPU Freq".

@dlandon The problem is, that I dont know, how to remove the driver from the kernel.

@JorgeB How can I disable amd-pstate-epp driver and enable acpi-cpufreq driver?

@dlandon I double checked everything. But it does not work its always the amd-pstate-epp driver. Please check.

With the driver "AMD Pstate" you can only set the Governor to "Power Save" and "Performance". "On demand" and "conservative" does not work.

I tried your workaround and rebooted, but it does not work. Its still the amd-pstate-epp. root@nas01:~# cd /boot/config/modprobe.d/ root@nas01:/boot/config/modprobe.d# ls -al total 128 drwx------ 2 root root 32768 Feb 24 21:40 ./ drwx------ 12 root root 32768 Feb 24 21:45 ../ -rw------- 1 root root 25 Feb 24 21:40 amd-pstate-epp.conf -rw------- 1 root root 207 Jan 17 23:47 zfs.conf root@nas01:/boot/config/modprobe.d# cat amd-pstate-epp.conf blacklist amd-pstate-epp root@nas01:/boot/config/modprobe.d# update: after your update from today, its displayed as "Driver: AMD Pstate"

@dlandon # cat /sys/devices/system/cpu/amd_pstate/cpb_boost cat: /sys/devices/system/cpu/amd_pstate/cpb_boost: No such file or directory This is in the directory: # cd /sys/devices/system/cpu/amd_pstate/ root@nas01:/sys/devices/system/cpu/amd_pstate# ls -al total 0 drwxr-xr-x 2 root root 0 Feb 21 11:59 ./ drwxr-xr-x 26 root root 0 Feb 21 11:33 ../ -r--r--r-- 1 root root 4096 Feb 21 20:38 prefcore -rw-r--r-- 1 root root 4096 Feb 21 20:38 status

# ls /sys/devices/system/cpu/amd_pstate/ prefcore status

Hello @dlandon The result for "cat /sys/devices/system/cpu/cpufreq/boost" on Unraid 7 is: # cat /sys/devices/system/cpu/cpufreq/boost cat: /sys/devices/system/cpu/cpufreq/boost: No such file or directory

The output is: 0 but I reverted to Unraid 6.

@dlandon It was: ACPI CPU Freq Now it is: amd-pstate-epp Yes there are problems in this forum with pictures it seems...

@dlandon What information is missing? I think everything is displayed on my screenshots. Where can I find the missing information? Thats the complete area at the settings with Unraid 6:

I downgraded to Unraid 6.12.14 and my server needs now again less power. It was about 45 to 50 watts with Unraid 7.0.0. As I already wrote, I reported this to the author of "Tips and Tweaks" plugin, as I think thats the problem.

Hello, I wrote to the plugin author of "Tips and Tweaks" now, because I think it might not work correct anymore with Unraid 7.0.0.

Hello, it seems that your plugin "Tips and Tweaks" does not work correct anymore after updating to Unraid 7.0.0. - my server need now about 35% more power. You can also see on the screenshot, that the options for performance boost are not displayed anymyore and my Normal CPU Scaling Governor is set to conservative, but on the right there is displayed "performance". With Unraid 6.12.14 everything worked fine. Would you please check this? This is with Unraid 6.12.14: nas01-diagnostics-20250220-1928.zip

Hello, I upgraded to Unraid 7.0.0. between 17th January 2025 and 18th January 2025. Today I have seen, that my server now needs about 35% more power. There was no change of the hardware and no additional software. I am using the plugin from dlandon "Tips and Tweaks" to reduce the CPU scaling (conservative). Can anyone help? nas01-diagnostics-20250220-1928.zip

Hello @JorgeB, sorry for my mistake. I changed it now to: default menu.c32 menu title Lime Technology, Inc. prompt 0 timeout 50 label Unraid OS menu default kernel /bzimage append initrd=/bzroot usb_storage.quirks=2109:0715:u And rebooted. The reboot works fine again now. And the disk is now again displayed as "Samsung SSD..." and not anymore as "Icy Box....". # lsusb -t /: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 480M |__ Port 001: Dev 002, If 0, Class=Human Interface Device, Driver=usbfs, 12M /: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 10000M |__ Port 002: Dev 002, If 0, Class=Mass Storage, Driver=usb-storage, 5000M /: Bus 003.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 480M /: Bus 004.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 10000M |__ Port 002: Dev 002, If 0, Class=Mass Storage, Driver=usb-storage, 10000M /: Bus 005.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 480M |__ Port 002: Dev 002, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 003: Dev 003, If 0, Class=Wireless, Driver=btusb, 480M |__ Port 003: Dev 003, If 1, Class=Wireless, Driver=btusb, 480M |__ Port 003: Dev 003, If 2, Class=Wireless, Driver=[none], 480M /: Bus 006.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 10000M |__ Port 002: Dev 002, If 0, Class=Hub, Driver=hub/4p, 5000M The parity disk works fine so far and the parity-sync is at the moment at 10.2%. Thank you for your fast help! nas01-diagnostics-20250119-2148.zip

Hello @JorgeB I made the changes and reboot: On flash drive in folder syslinux I changed the file syslinux.cfg: default menu.c32 menu title Lime Technology, Inc. prompt 0 timeout 50 label Unraid OS menu default kernel /bzimage append initrd=/bzroot usb_storage.quirks=2109:0715 label Unraid OS GUI Mode kernel /bzimage append initrd=/bzroot,/bzroot-gui # lsusb -t /: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 480M |__ Port 001: Dev 002, If 0, Class=Human Interface Device, Driver=usbfs, 12M /: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 10000M |__ Port 002: Dev 002, If 0, Class=Mass Storage, Driver=usb-storage, 5000M /: Bus 003.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 480M /: Bus 004.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 10000M |__ Port 002: Dev 002, If 0, Class=Mass Storage, Driver=uas, 10000M /: Bus 005.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 480M |__ Port 002: Dev 002, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 003: Dev 003, If 0, Class=Wireless, Driver=btusb, 480M |__ Port 003: Dev 003, If 1, Class=Wireless, Driver=btusb, 480M |__ Port 003: Dev 003, If 2, Class=Wireless, Driver=[none], 480M /: Bus 006.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 10000M |__ Port 002: Dev 002, If 0, Class=Hub, Driver=hub/4p, 5000M label Unraid OS Safe Mode (no plugins, no GUI) kernel /bzimage append initrd=/bzroot unraidsafemode label Unraid OS GUI Safe Mode (no plugins) kernel /bzimage append initrd=/bzroot,/bzroot-gui unraidsafemode label Memtest86+ kernel /memtest I reset config and selected the parity drive again. It works for about 0.4% and then again errors: an 19 13:26:05 nas01 kernel: I/O error, dev sda, sector 69661720 op 0x1:(WRITE) flags 0x4000 phys_seg 128 prio class 0 Jan 19 13:26:05 nas01 kernel: md: disk0 write error, sector=69661656 Jan 19 13:26:05 nas01 kernel: md: disk0 write error, sector=69661664 Jan 19 13:26:05 nas01 kernel: md: disk0 write error, sector=69661672 Jan 19 13:26:05 nas01 kernel: md: disk0 write error, sector=69661680 Jan 19 13:26:05 nas01 kernel: md: disk0 write error, sector=69661688 Jan 19 13:26:05 nas01 kernel: md: disk0 write error, sector=69661696 Jan 19 13:26:05 nas01 kernel: md: disk0 write error, sector=69661704 Jan 19 13:26:05 nas01 kernel: md: disk0 write error, sector=69661712 Jan 19 13:26:05 nas01 kernel: md: disk0 write error, sector=69661720 Jan 19 13:26:05 nas01 kernel: md: disk0 write error, sector=69661728 Jan 19 13:26:05 nas01 kernel: md: disk0 write error, sector=69661736 Jan 19 13:26:05 nas01 kernel: md: disk0 write error, sector=69661744 # lsusb -t /: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 480M |__ Port 001: Dev 002, If 0, Class=Human Interface Device, Driver=usbfs, 12M /: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 10000M |__ Port 002: Dev 002, If 0, Class=Mass Storage, Driver=usb-storage, 5000M /: Bus 003.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 480M /: Bus 004.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 10000M |__ Port 002: Dev 002, If 0, Class=Mass Storage, Driver=uas, 10000M /: Bus 005.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 480M |__ Port 002: Dev 002, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 003: Dev 003, If 0, Class=Wireless, Driver=btusb, 480M |__ Port 003: Dev 003, If 1, Class=Wireless, Driver=btusb, 480M |__ Port 003: Dev 003, If 2, Class=Wireless, Driver=[none], 480M /: Bus 006.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 10000M |__ Port 002: Dev 002, If 0, Class=Hub, Driver=hub/4p, 5000M One thing also happens: when I try to reboot, the system hangs. I have to power off and on. nas01-diagnostics-20250119-1331.zip

After some minutes, the error is here agein and parity-sync stopped with error: Unraid Parity disk errorAlert [NAS01] - Parity disk in error state (disk dsbl)ICY_BOX_IB-247-C31_000000123B64-0:0 (sda) Parity disk - ICY_BOX_IB-247-C31_000000123B64-0:0 (sda) (errors 80) # lsusb -t /: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 480M |__ Port 001: Dev 002, If 0, Class=Human Interface Device, Driver=usbfs, 12M /: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 10000M |__ Port 002: Dev 002, If 0, Class=Mass Storage, Driver=usb-storage, 5000M /: Bus 003.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 480M /: Bus 004.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 10000M |__ Port 002: Dev 002, If 0, Class=Mass Storage, Driver=uas, 10000M /: Bus 005.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 480M |__ Port 002: Dev 002, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 003: Dev 003, If 0, Class=Wireless, Driver=btusb, 480M |__ Port 003: Dev 003, If 1, Class=Wireless, Driver=btusb, 480M |__ Port 003: Dev 003, If 2, Class=Wireless, Driver=[none], 480M /: Bus 006.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 10000M |__ Port 002: Dev 002, If 0, Class=Hub, Driver=hub/4p, 5000M nas01-diagnostics-20250118-2130.zip

Meanwhile I reverted to 7.0.0., precleared disk (only read test, then stopped) and format it. All without errors. Now its parity disk again and Parity-Sycn started. # lsusb -t /: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 480M |__ Port 001: Dev 002, If 0, Class=Human Interface Device, Driver=usbfs, 12M /: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 10000M |__ Port 002: Dev 002, If 0, Class=Mass Storage, Driver=usb-storage, 5000M /: Bus 003.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 480M /: Bus 004.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 10000M |__ Port 002: Dev 002, If 0, Class=Mass Storage, Driver=uas, 10000M /: Bus 005.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 480M |__ Port 002: Dev 002, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 003: Dev 003, If 0, Class=Wireless, Driver=btusb, 480M |__ Port 003: Dev 003, If 1, Class=Wireless, Driver=btusb, 480M |__ Port 003: Dev 003, If 2, Class=Wireless, Driver=[none], 480M /: Bus 006.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 10000M |__ Port 002: Dev 002, If 0, Class=Hub, Driver=hub/4p, 5000M nas01-diagnostics-20250118-2044.zip

After update to 7.0.0 my parity disk (8TB Samsung SSD) which is connected on USB with a ICY BOX does not work anymore. There are many write errors displayed. Parity stopped working. I could see that with the old version 6.12.14 this disk was displayed as "Samsung_SSD_870_QVO......." and after update it was "ICY_BOX_IB-247-C31_000000123B64-0:0" with same 8TB. I reverted to 6.12.14 now. What could be the reason for this? A new USB driver maybe in unRAID 7.0.0.?

@abraunegg I found the reason for the problem with this --resync loop: It was because there was the code "sync_dir = "/onedrive/data" " missing in the config file. It seems that the new version need this setting, the older versions not. After adding sync_dir = "/onedrive/data" to the config file, the file is not touched by onedrive docker, means the date and time is not changed and the resync loop stopped. I have seen, when installing new docker container, "sync_dir = "/onedrive/data" " is added automatically in the config file... so I found the reason for this problem.

@ADvorsky Yes I am sure. But it should NEVER change the config file.