lehe

Hey @dubbly sorry I didn't check the forum for a while. I am using an ASUS PRIME B360M-A and now upgraded to an i7 8700k - no other requirements. Still using the forced ASPM setting for the Realtek NIC (RTL8111H) and not having a single crash or any Network issues for a year now. It's idling at around 16 W with a cheap power supply, four HDDs spun down, two SATA SSDs and one NVME running and a bunch of Docker containers, reaching C7 most of the Time. Definitely some room for improvement but currently I'm not willing to spend any money for a few watts in return.

Hey obowan, after a bit more tinkering with my asp settings and getting deeper into it I just found a solution: It is possible to force enable aspm for the device by using " echo 1 | sudo tee /sys/bus/pci/drivers/r8169/0000:02:00.0/link/l1_aspm " . The corresponding device number eg. "0000:02:00.0" you can get out of "lspci" I am now reaching C8 again even on Unraid 7.

Glad to hear you made some progress! I read about the issue with different SATA controllers a few times. One thing I found out in the meantime is that there is some kind of incompatibility with Realtek NICs with the Linux Kernel used since unraid 6.12.5. So we can only hope that it will be fixed at some point in the future. That is also the reason why I'm staying on 6.12.4.

Did you try optimizing with powertop --auto-tune &>/dev/null ? It helps with most devices preventing lower C-states. Been there and haven't found a solution either. The only fix I found is staying on Unraid 6.12.3 idling at C10 at around 11 W with an i3 8100. On anything newer including Unraid 7.0 b2 I'm stuck with C3 at around 15-20 W idle. Using " lspci -vv | awk '/ASPM/{print $0}' RS= | grep --color -P '(^[a-z0-9:.]+|ASPM;|Disabled;|Enabled;)' " you can check what devices have ASPM disabled.

The share was not created there and the space on both drives changed according to the size of the data. This is what I read before and why I chose /mnt/disk1/ and /mnt/poolname/ for the transfer and not /mnt/user/ . Is it better to copy/move between the shares in /mnt/user/ ? This is what made me wonder in the first place, and what I saw when I normally wrote to the array. But it had none when I checked, or at least not more than a few B/s, so it could have written to the parity disk later or after the move was complete. Would the system somehow know that the files are missing and the parity is not valid if it did not move correctly with MC, or does it only show after checking the parity again?

Alright, thank you for your answer! But how can it be that the parity is still ok if nothing has been changed on the parity drive and the files have been deleted from the disk in the array?

Hey guys, I'm still pretty new to using unraid as my main backup server. Yesterday I moved a bunch of uncritical data from the array to an unprotected drive in a separate pool using RenMov in MC to free up some space on the array. I moved the files from /mnt/disk1/Share 1/Folder/Movies to /mnt/unprotected disk/Share 2/Folder/Movies/ . The main page says that the parity is still in tact, but while moving the files to the other drive, the parity drive did not do any writes or reads, so I wonder if this has affected the parity on the main array? Should I do a full parity check to be sure?