zoggy

Members
  • Posts

    664
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by zoggy

  1. I've never seen this before until 6.11.4 and now 6.11.5 and have the same plugins for a bit now. The newest plugin I installed was the "CA Mover Tuning" one, which per my logs I've had installed since 6.11.0-rc3 (August). I do not have array auto start. When array comes up after upgrade, says config is good. I go to start array, and in firefox 107 it shows the resend prompt. If you hit cancel, it works fine. If you hit resend, it puts the array in a 'stale configuration' state. Where you can only reboot/shutdown server. plugins: CA Auto Update Applications CA Backup / Restore Appdata CA Cleanup Appdata CA Mover Tuning Community Applications Dynamix Active Streams Dynamix System Information Dynamix System Statistics Dynamix System Temperature Fix Common Problems Tips and Tweaks Unassigned Devices Unassigned Devices Plus Unassigned Devices Preclear unBALANCE
  2. the gui lets you create a share like '.downloads' but then it says it was deleted when creating and the gui fails to show it, but it it actually created it: root@unraid:/mnt/user/.downloads# pwd /mnt/user/.downloads
  3. for what you were installing with nerdpack, look for what you had set to yes in it's cfg (even if nerdpack is disabled): grep yes /boot/config/plugins/NerdPack/NerdPack.cfg for what is installed currently in unraid: ls -lah /var/lib/pkgtools/packages/
  4. or once you are on 6.11 you can install several just via CA with, "<x> package".. python2/3 for example are there also with 6.11, there are several plugins that are included by default that save the need for many people to use nerdpack anyways. for example perl is included now.
  5. another update, 6.10.x corrected/enabled a lot of the asus sensors but still had no fans. with unraid 6.11rc3 I can confirm fans are there now as well and all is working well: **update** updating to 6.11rc4 I can see even more fan/sensors added (asusec).
  6. if you are confused, just enable mover logging, enable test mode on the mover tuning plugin, and set the "Move Now button follows plug-in filters:" to yes. so you can just fire off the script and see what it would move. tweak values and repeat. once all good, turn off test mode... testing myself as i have it set to move stuff older than 10 days and "Move All from Cache-yes shares pool percentage:" set to 50%. with mover running weekly. with only 18% cache used, and a few files older than 10 days. firing it off.. it moved a few files older than 10 days. so the logic to move by age does not limit by the cache usage.
  7. unraid 6.11rc already comes with docker engine 20.10.17 # docker version Client: Version: 20.10.17 API version: 1.41 Go version: go1.17.11 Git commit: 100c701 Built: Mon Jun 6 22:56:42 2022 OS/Arch: linux/amd64 Context: default Experimental: true Server: Docker Engine - Community Engine: Version: 20.10.17 API version: 1.41 (minimum version 1.12) Go version: go1.17.11 Git commit: a89b842 Built: Mon Jun 6 23:01:45 2022 OS/Arch: linux/amd64 Experimental: false containerd: Version: v1.6.6 GitCommit: 10c12954828e7c7c9b6e0ea9b0c02b01407d3ae1 runc: Version: 1.1.2 GitCommit: v1.1.2-0-ga916309f docker-init: Version: 0.19.0 GitCommit: de40ad0 but "docker compose" is not valid # docker compose docker: 'compose' is not a docker command. See 'docker --help' so looks like docker-compose-plugin will still have to be installed.
  8. you could always just grab unrar latest and install it yourself. on most linux distros as they are always behind on unrar i just install non-free then replace with latest: wget https://www.rarlab.com/rar/rarlinux-x64-612.tar.gz tar -xzf rarlinux*.tar.gz sudo mv rar/unrar /usr/bin/unrar sudo chmod 755 /usr/bin/unrar are you trying to update unrar for docker? (lsio has already updated, so have a few others now)
  9. minor cosmetic bug, it shows the same log entry but one is skipfile list one is skipfiles type : mvlogger "No Skipfiles Argument Supplied" mvlogger "No Skipfiles Argument Supplied" https://github.com/hugenbd/ca.mover.tuning/blob/master/source/ca.mover.tuning/usr/local/emhttp/plugins/ca.mover.tuning/age_mover#L149 kinda shocked there isnt an option to skip a folder, as lots of people probably want to skip their seeding/incomplete folder so mover doesnt move files out from under a downloader (let alone waste disk io and slow everything down). guessing people just get creative and try to just set folder as hidden? or use move by age and set the age high engouh?
  10. Noticed that if i resize the window large enough the _ would show up again and shrinking, it would disappear..
  11. If you open up a docker console, the _ character can be seen on the cli (editline) just fine. Then if you use less to view a file and then exit. Then the _ is no longer visible. If you press enter afterwards you can see it actually is there, just the editline is not showing it. I assume its prob some line height issue? example:
  12. My main computer + unraid are on a 2.5G switch and both have 2.5GbE ports. The unraid box has a realtek RTL8125 2.5GbE port on the motherboard, testing I would get full speed on 6.9.2 but after upgrading to 6.10.0 (and tested .1 + .2) the performance dropped. iperf3 udp test: unraid: iperf3 -s -p 5003 from windows machine, udp w/8 connections for 10 seconds: X:\iperf-3.1.3-win64> ./iperf3.exe -c 192.168.0.11 -p 5003 -P8 -t10 -i1 -b 3G -u on 6.9.2 - 286 MBytes (2.40 Gbits/sec) on 6.10.1 - 179 MBytes (1.50 Gbits/sec) ethtool shows: can see the same driver loaded on 6.10.2 vs 6.9.2: lspci shows:
  13. I was checking something recently after upgrading to 6.10.2 and noticed that DiskSpeed created its main folder with a unknown user pid: :/mnt/user/appdata# ls -ld DiskSpeed/ drwxrwxrwx 1 65534 users 18 Apr 13 10:12 DiskSpeed// :/mnt/user/appdata/DiskSpeed# ls -alh total 0 drwxrwxrwx 1 65534 users 18 Apr 13 10:12 ./ drwxrwxrwx 1 nobody users 292 May 21 02:46 ../ drwxrwxrwx 1 65534 users 10 Apr 13 10:12 Instances/ seemed to work just fine however?
  14. For me I just had to go re-select the probes in settings > system temp. since the sensors names changed as newer linux kernel has better support for my mobo.
  15. after upgrading to 6.10 stable, when i go to "stats" it logs an error in unraid syslog:
  16. sharing above PSA since sandisk are not advisable. but anyways, since the drive is working for you it makes me just think your boot partition just needs re-doing once you have 6.10 installed. try running make_bootable script for your os.
  17. gt = guest tools for more info: https://github.com/virtio-win/virtio-win-guest-tools-installer
  18. If you actually click on the link the kernel bug report you would see that yes, while the mobo are similar one has to add the mobo string to the appropriate driver to make it the sensor info work. Its comically stupid and does not scale, which is about half of the chatter about with how dumb getting sensors data with asus is. Then if you would have clicked on the link I shared about the driver you would see even further proof of this. How even different variations of the same board have to be added due to how its checked. snippet: As you noted what mobo you have, can see others reporting same issue: ROG STRIX X570-F GAMING - https://bugzilla.kernel.org/show_bug.cgi?id=204807#c112 Your hwinfo noted that card has NCT6798D but nct6775 driver is to be used. While sensors-detect knows to associate the NCT67* to nct6775 it doesnt mean that the driver fully supports your mobo. Some of it is deciding which method to get the sensor data and which can use wmi and so on, where the whole whitelisting mobo name comes into play. Looking at that linux driver history for nct6775, can see that "ROG STRIX X570-F GAMING" was added: 2021-10-12 - https://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git/commit/drivers/hwmon/nct6775.c?id=6e2baac88cddbb440095c45058bc666df3108a1f Then you would have to see what kernel that then made it into, and if you are using it. Which is why I asked the other use if you just tried newer linux kernel to see if it works. As I've been in this same boat, where I had 0 support and then newer kernel exposed some sensor data.. so now I get cpu temp but still no mobo or fans (until 6.10x)
  19. you can just start the system up with newest rc, just dont start array if your worried about anything with your data/dockers/etc. then check to see if sensors/fans etc are working so you gather data and know. then revert back to stable release for actual peace of mind and daily use.
  20. unless you are both using the same motherboard then i dont see how you can use the logic that it wont make a difference. as ive even linked proof that x boards had improvements in detection of wmi sensors via kernel update.
  21. you should try upgrading to next release (6.10rc4) and see if everything is magically supported for ya (as it includes much newer linux kernel/drivers/etc).
  22. i would not recommend the acpi_enforce_resources=lax i've tried that before and it caused unraid to fail to boot until removed. which lead me to find this: about asus and the buggy issues with reading fan/temps: https://bugzilla.kernel.org/show_bug.cgi?id=204807 oct 2021 - lot of asus wmi boards got supported via NCT677x: https://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git/commit/?id=cd0b8e410937 so basically you just have to wait for newer kernel to get better support. you using 6.10rc3 ?
  23. for dynamix.system.temp -- noticed that this shows up in the unraid logs on unraid 6.9.2:
  24. In unraid, Settings > Management Access > Local TLD unraid's help says: Enter your local Top Level Domain. May be blank. But in FCP it is unhappy about a blank TLD. Easy enough to ignore, but I do not recall it used to complain about this.. is there a recent unraid change that requires the user to set this now?
  25. To note small change in output formatting, original gfjardim plugin had the time/speed/result right aligned: # # # Step 1 of 5 - Pre-read verification: [0:32:00 @ 417 MB/s] SUCCESS # # Step 2 of 5 - Zeroing the disk: [0:45:02 @ 296 MB/s] SUCCESS # # Step 3 of 5 - Writing unRAID's Preclear signature: SUCCESS # # Step 4 of 5 - Verifying unRAID's Preclear signature: SUCCESS # # Step 5 of 5 - Post-Read verification: [0:25:24 @ 525 MB/s] SUCCESS # # # # # ############################################################################################################################ # Cycle elapsed time: 1:42:29 | Total elapsed time: 1:42:29 # ############################################################################################################################ With new 'enhanced' version it is not: # Step 1 of 5 - Pre-read verification: [0:30:36 @ 436 MB/s] SUCCESS # # Step 2 of 5 - Zeroing the disk: [0:44:05 @ 302 MB/s] SUCCESS # # Step 3 of 5 - Writing Unraid's Preclear signature: SUCCESS # # Step 4 of 5 - Verifying Unraid's Preclear signature: SUCCESS # # Step 5 of 5 - Post-Read verification: [0:25:27 @ 524 MB/s] SUCCESS # # # #################################################################################################### # Cycle elapsed time: 1:40:11 | Total elapsed time: 1:40:12 # #################################################################################################### So far everything looks to be running the same, similar speed and no issues so far.