zoggy

Members
  • Posts

    649
  • Joined

  • Last visited

Everything posted by zoggy

  1. I have RTL8125 port on my mobo, and I still get 2.5GbE link on 6.10.0/6.10.1 but not getting the full speed. ethtool shows: can see the same driver loaded on 6.9.2 + 6.10.0/6.10.1: lspci shows: Per the linked github repo, it looks like it loads r8169 by default and is used unless you blacklist? https://github.com/awesometic/realtek-r8125-dkms/blob/master/README.md#verify-the-module-is-loaded-successfully main computer + unraid on 2.5G switch, re-ran some iperf3 tests I did recently on 6.9.2. on 6.9.2 - 286 MBytes (2.40 Gbits/sec) on 6.10.1 - 179 MBytes (1.50 Gbits/sec) and how i'm testing, running iperf3 on unraid and connecting from remote. i normally do tcp+udp, but to rule out any overhead and other stuff just focusing on udp: 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 So yeah something deff changed *update 5/27* Tested 6.10.2 and same results as 6.10.0/6.10.1
  2. 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.
  3. after upgrading to 6.10 stable, when i go to "stats" it logs an error in unraid syslog:
  4. 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.
  5. gt = guest tools for more info: https://github.com/virtio-win/virtio-win-guest-tools-installer
  6. 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)
  7. 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.
  8. 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.
  9. 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).
  10. 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 ?
  11. for dynamix.system.temp -- noticed that this shows up in the unraid logs on unraid 6.9.2:
  12. 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?
  13. 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.
  14. The came from an outside source and I want to validate them. They are enterprise ssd with pretty high tbw, so doing a full drive write is trivial for them.
  15. I was noting that the change of going from preclear to UD Preclear means that I had to do an extra step now to get UD+ to remove the partition to clear, which is a change. Once a user is familiar with the process and the initial steps of getting UD, UD+, UD Preclear installed then it is not a huge deal.
  16. if a usb drive isnt booting its generally because its boot loader isnt right. you can either re-run the unraid usb creator ( https://unraid.net/download ) or just run the make_bootable file with it attached to your machine. now if its really only when that hdd is connected, perhaps its one of those esata/usb ports where they share and only one can be operational at once.. but not clear if your connecting the usb to external port or off usb header on the motherboard (which is whats recommended). if its external, move it to another usb port..
  17. I have a stack of 24 ssd that were part of a linux array that I'm pre-clearing. I figure this would be a good time to switch from the preclear plugin to UD w/UD prelear to test out. Uninstalled precleared, installed UD and put in SSD and it show "There are no disks that can be precleared." So normal preclear plugin normally would work fine as it doesn't care what was on the disk before. UD Preclear wont touch it because it sees it was part of a raid and has existing filesystem as you noted above. So installed UD+, and nuke partition on the disk and now I see I can preclear it. So had to install UD, UD Preclear, UD+ to be able to preclear a drive. Can we make it so the user doesn't need to install UD+ to nuke the drive partition in order to preclear a drive?
  18. its because your bios is detecting the hdd and tries to boot off of it. change your bios boot options to not boot off hdd / boot off the usb stick specifically.
  19. and to add some other comments from discord proxmox also having same issue with newer kernel - forum.proxmox.com/threads/solved-proxmox-7-linux-5-11-22-issue-with-lsi-2008-controllers.93781/ maybe this patch might help? https://lore.kernel.org/linux-scsi/20210518051625.1596742-3-suganath-prabu.subramani@broadcom.com/
  20. Nov 14 22:37:27 husky root: mover: started Nov 14 22:37:27 husky move: move: file /mnt/cache/TV/TV/Top Gear/Season 31/x.mkv Nov 14 22:37:31 husky move: move: file /mnt/cache/TV/TV/Top Gear/Season 31/x.nfo Nov 14 22:37:31 husky move: move: file /mnt/cache/TV/TV/Insecure/Season 05/x.mkv Nov 14 22:37:31 husky move: move: file /mnt/cache/TV/TV/Insecure/Season 05/x.nfo Nov 14 22:37:31 husky root: mover: finished I've noticed that on 6.9.2 the mover shows that it is instantly done, rather than reporting each file as its starting to copy... This gives the user false impression that it may be safe to shutdown as there is still activity going on. just tried again with 12G file: Nov 14 22:59:26 husky root: mover: started Nov 14 22:59:26 husky move: move: file /mnt/cache/Movies/Movies-HD/No.Time.to.Die.(2021)/No.Time.to.Die.2021.mkv Nov 14 22:59:40 husky move: move: file /mnt/cache/Movies/Movies-HD/No.Time.to.Die.(2021)/No.Time.to.Die.2021.nfo Nov 14 22:59:40 husky root: mover: finished says it finished, checking the Main page I see copying to parity + disk13 at 60MB/s on each for several minutes now.
  21. unraid 6.8.3 with ca version 2021.08.31 its showing there is an update but wont upgrade because of min version check, i could have sworn in the past it would just not show an update for an unsupported version? > plugin: installed Unraid version is too low, require at least version 6.9.0
  22. just take link, open up a new tab and put it in. for whatever reason it will not work if you try to do it directly from within the forum
  23. i was on vacation and sadly this mariadb docker auto upgraded (due to CA) and since the change to alpine (and maria 10.5) now my kodi instances randomly become unhappy with the db launching kodi results in it crashing because it cant get data from the db (it connects just errors on things), sample: 2021-09-01 09:58:50.454 T:24263 INFO <general>: Starting Kodi (19.1 (19.1.0) Git:20210508-85e05228b4). Platform: Android ARM 64-bit ... 2021-09-01 09:58:50.504 T:24263 INFO <general>: Contents of special://profile/advancedsettings.xml are... <advancedsettings> <loglevel>0</loglevel> <videodatabase> <type>mysql</type> <host>192.168.0.11</host> <port>3306</port> ... 2021-09-01 09:58:53.110 T:24291 INFO <general>: MYSQL: Connected to version 10.5.12-MariaDB-log 2021-09-01 09:58:53.115 T:24291 INFO <general>: Running database version MyMusic82 2021-09-01 09:58:53.121 T:24291 INFO <general>: Running database version MyVideos119 ... 2021-09-01 09:58:53.555 T:24263 INFO <general>: JSONRPC v12.3.0: Successfully initialized 2021-09-01 09:58:53.574 T:24292 ERROR <general>: SQL: [MyVideos119] An unknown error occurred Query: SELECT * FROM streamdetails WHERE idFile = 16300 2021-09-01 09:58:53.655 T:24292 ERROR <general>: GetStreamDetails(16300) failed ... 2021-09-01 09:58:53.836 T:24291 ERROR <general>: GetArtForItem(1125) failed 2021-09-01 09:58:53.836 T:24291 ERROR <general>: SQL: Missing result set! 2021-09-01 09:58:53.836 T:24291 ERROR <general>: GetArtForItem(181) failed 2021-09-01 09:58:53.841 T:24291 ERROR <general>: SQL: [MyVideos119] Commands were executed in an improper order Query: SELECT * FROM streamdetails WHERE idFile = 733 looking around, i found few different things saying that it may just be mariadb 10.5 itself found this, https://discourse.coreelec.org/t/the-state-of-mariadb-in-the-context-of-coreelec/13025 restarted docker, tried from another box and still no go: 2021-09-01 12:12:49.885 T:24465 INFO <general>: MYSQL: Connected to version 10.5.12-MariaDB-log 2021-09-01 12:12:49.891 T:24465 ERROR <general>: SQL: [MyMusic82] An unknown error occurred Query: SELECT idVersion FROM version 2021-09-01 12:12:50.005 T:24465 ERROR <general>: Process error processing job tried to downgrade mariadb docker to older tag (110.4.21mariabionic-ls31) but then on docker start up it just shows it crashing/starting: 210901 11:49:22 mysqld_safe Logging to syslog. 210901 11:49:22 mysqld_safe Starting mysqld daemon with databases from /config/databases 210901 11:49:23 mysqld_safe Logging to syslog. 210901 11:49:23 mysqld_safe Starting mysqld daemon with databases from /config/databases 210901 11:49:24 mysqld_safe Logging to syslog. 210901 11:49:24 mysqld_safe Starting mysqld daemon with databases from /config/databases 210901 11:49:25 mysqld_safe Logging to syslog. looking at why... # /usr/sbin/mysqld --basedir=/usr --datadir=/config/databases --plugin-dir=/usr/lib/mysql/plugin --pid-file=/var/run/mysqld/mysqld.pid --socket=/var/run/mysqld/mysqld 2021-09-01 12:38:58 0 [Note] /usr/sbin/mysqld (mysqld 10.4.21-MariaDB-1:10.4.21+maria~bionic-log) starting as process 7030 ... 2021-09-01 12:38:58 0 [ERROR] mysqld: Can't lock aria control file '/config/databases/aria_log_control' for exclusive use, error: 11. Will retry for 30 seconds ^C^C^C^C^C 2021-09-01 12:39:29 0 [ERROR] mysqld: Got error 'Could not get an exclusive lock; file is probably in use by another process' when trying to use aria control file '/config/databases/aria_log_control' 2021-09-01 12:39:29 0 [ERROR] Plugin 'Aria' init function returned error. 2021-09-01 12:39:29 0 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed. 2021-09-01 12:39:29 0 [Note] InnoDB: Using Linux native AIO 2021-09-01 12:39:29 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2021-09-01 12:39:29 0 [Note] InnoDB: Uses event mutexes 2021-09-01 12:39:29 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 2021-09-01 12:39:29 0 [Note] InnoDB: Number of pools: 1 2021-09-01 12:39:29 0 [Note] InnoDB: Using SSE2 crc32 instructions 2021-09-01 12:39:29 0 [Note] mysqld: O_TMPFILE is not supported on /tmp (disabling future attempts) 2021-09-01 12:39:29 0 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M 2021-09-01 12:39:29 0 [Note] InnoDB: Completed initialization of buffer pool 2021-09-01 12:39:29 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). 2021-09-01 12:39:29 0 [ERROR] InnoDB: Unsupported redo log format. The redo log was created with MariaDB 10.5.12. 2021-09-01 12:39:29 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error 2021-09-01 12:39:29 0 [Note] InnoDB: Starting shutdown... 2021-09-01 12:39:30 0 [ERROR] Plugin 'InnoDB' init function returned error. 2021-09-01 12:39:30 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 2021-09-01 12:39:30 0 [Note] Plugin 'FEEDBACK' is disabled. 2021-09-01 12:39:30 0 [ERROR] Could not open mysql.plugin table. Some plugins may be not loaded 2021-09-01 12:39:30 0 [ERROR] Failed to initialize plugins. 2021-09-01 12:39:30 0 [ERROR] Aborting I got it working on old tag finally. As I had ran "mysql_upgrade -u root -p" when it was on alpine/10.5 to try and get it to fix the problem that the upgrade caused: https://forum.kodi.tv/showthread.php?tid=364255&pid=3057634 So downgraded back to older tag but then in the database folder I had to nuke: aria_log.* / ib_logfile0 / mysql_upgrade_info Now things work like they did before just fine..