norgoe

Thanks, never would have thought that totally valid filenames for the OS get checked like that. Would be great if this check could be disabled on a per share base, to have it active on other shares.

I do not know what lately was changed in regards to handling filenames, but for me, it broke filehandling for log-files of proxmox Backup Server and I am bombarded daily with about 250 Mails (in a timespan of approximately 25 minutes) from t20 Unraid Status: Mover Tuning Notification with content like this: Link: http://t20.local/Settings/Scheduler Event: Unraid Status Subject: Mover Tuning Notification Description: Error: Invalid filename path: 'appdata/pbs/logs/tasks/98/UPID:t20:0000000A:09EE5498:00000001:67788810:garbage_collection:Backup:root@pam:' Importance: warning These files all exist and contain logging data and should be synced from ssd to rotating rust. root@t20:/mnt/user# ls -la appdata/pbs/logs/tasks/98/UPID:t20:0000000A:09EE5498:00000001:67788810:garbage_collection:Backup:root@ pam: -rw-r--r-- 1 34 34 12496 Jan 4 02:09 appdata/pbs/logs/tasks/98/UPID:t20:0000000A:09EE5498:00000001:67788810:garbage_collection:Backup:root\@pam: root@t20:/mnt/user# I already deleted a bunch of these messages and hoped the problem would be fixed soon. Regarding my inbox it at least exists since the 28th or march. I currently disabled sending mails for warnings, which I really hate. I really would appreciate if someone familiar with the script can take a look at it and find a solution. Regards Norbert

Autotune did not enable all powersaving options for me, thus I enabled them manually and afterwards added the quirks manually to the go file. You have powersavin on all USB ports disabled - enable them manually in powetop. And you did not show the Tunables section - go there and set everyrging from bad to good. Spin down all harddrives and recheck your powerconsumption. P.S.: And like mgutt said, the NM620 will most probably disable all Package powersave better than C2 (at least it did for me on both my intel systems - see some posts above).

Hi, thanks for this topic. I felt stupid when my dell T20 got power thirsty in idle mode after plugging in an M.2 SSD (with a passive PCIE adaptercard). Seems like the Lexar NM620 2TB is one of those drivers, that keep the cpu package above C3 level. With this SSD plugged in, the XEON can't get below C2 anymore. Unplugging the Lexar and it can reach C6 - swapping to a Samsung 970 EVO Plus and C6 is back again. Trying the Lexar NM620 in a thinkcentre M900 Tiny with I5 6500T show the same "defect by design". Nothing else than C2 reachable. With the 970 the 6500T gets down to C8. Idling on 4.6W vs. 7W....