so I changed my curent nas box from an i4-3775 16GB GTX710 video to a I7-8700k 64GB RTX2600 and I noticed it could be sluggish, so I checked out the logs and saw this error com up and wondering what it means truly

the 8700K is non overclocked and is a 6 cpu 12 threads. (counted I think 0->11), should I have reinstalled the OS?

Nov  3 13:35:52 Nas kernel: CPU: 11 UID: 0 PID: 1727 Comm: udevd Tainted: P           O        6.18.54-Unraid #1 PREEMPT(voluntary) 
Nov  3 13:35:52 Nas kernel: Tainted: [P]=PROPRIETARY_MODULE, [O]=OOT_MODULE
Nov  3 13:35:52 Nas kernel: Hardware name: System manufacturer System Product Name/TUF Z390-PRO GAMING, BIOS 3006 10/12/2021
Nov  3 13:35:52 Nas kernel: RIP: 0010:__warn_thunk+0x21/0x30
Nov  3 13:35:52 Nas kernel: Code: 90 90 90 90 90 90 90 90 90 0f 1f 44 00 00 80 3d 4f 80 7b 01 00 75 15 48 c7 c7 05 a1 55 82 c6 05 3f 80 7b 01 01 e8 4f 5e 04 00 <0f> 0b c3 cc cc cc cc cc cc cc cc cc cc cc cc 90 90 90 90 90 90 90
Nov  3 13:35:52 Nas kernel: RSP: 0018:ffffc9000d12bb88 EFLAGS: 00010286
Nov  3 13:35:52 Nas kernel: RAX: 0000000000000000 RBX: 0000000000000040 RCX: 0000000000000002
Nov  3 13:35:52 Nas kernel: RDX: 0000000000000326 RSI: ffffffff828b7a88 RDI: 00000000ffffffff
Nov  3 13:35:52 Nas kernel: RBP: ffffc9000d12bbd8 R08: 0000000000000000 R09: 0000000000002000
Nov  3 13:35:52 Nas kernel: R10: 0000000000000008 R11: 00aaaaaa00aaaaaa R12: 00000000000000ff
Nov  3 13:35:52 Nas kernel: R13: ffffffffa0e8583c R14: ffffc9000d12bc90 R15: 0000000000000040
Nov  3 13:35:52 Nas kernel: FS:  0000146ea023f780(0000) GS:ffff8890aaa2e000(0000) knlGS:0000000000000000
Nov  3 13:35:52 Nas kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Nov  3 13:35:52 Nas kernel: CR2: 0000146ea0043000 CR3: 0000000168904002 CR4: 00000000003706f0

Attach Diagnostics ZIP to your NEXT post in this thread.

okay so, I did do the missed update from 7.3.2 to 7.3.4 and here is the log extract (cpu number changed ??) I also attached the diagnostics.

Nov  5 22:03:40 Nas kernel: CPU: 1 UID: 0 PID: 1726 Comm: udevd Tainted: P           O        6.18.58-Unraid #2 PREEMPT(voluntary) 
Nov  5 22:03:40 Nas kernel: Tainted: [P]=PROPRIETARY_MODULE, [O]=OOT_MODULE
Nov  5 22:03:40 Nas kernel: Hardware name: System manufacturer System Product Name/TUF Z390-PRO GAMING, BIOS 3006 10/12/2021
Nov  5 22:03:40 Nas kernel: RIP: 0010:__warn_thunk+0x21/0x30
Nov  5 22:03:40 Nas kernel: Code: 90 90 90 90 90 90 90 90 90 0f 1f 44 00 00 80 3d af 80 7b 01 00 75 15 48 c7 c7 da af 55 82 c6 05 9f 80 7b 01 01 e8 5f 5f 04 00 <0f> 0b c3 cc cc cc cc cc cc cc cc cc cc cc cc 90 90 90 90 90 90 90
Nov  5 22:03:40 Nas kernel: RSP: 0018:ffffc9000d147b80 EFLAGS: 00010282
Nov  5 22:03:40 Nas kernel: RAX: 0000000000000000 RBX: 0000000000000040 RCX: 0000000000000002
Nov  5 22:03:40 Nas kernel: RDX: 0000000000000324 RSI: ffffffff828b7a88 RDI: 00000000ffffffff
Nov  5 22:03:40 Nas kernel: RBP: ffffc9000d147bd0 R08: 0000000000000000 R09: 0000000000002000
Nov  5 22:03:40 Nas kernel: R10: 0000000000000008 R11: 00aaaaaa00aaaaaa R12: 00000000000000ff
Nov  5 22:03:40 Nas kernel: R13: ffffffffa0ec3864 R14: ffffc9000d147c88 R15: 0000000000000040
Nov  5 22:03:40 Nas kernel: FS:  0000149d0261d780(0000) GS:ffff8890aa7ab000(0000) knlGS:0000000000000000
Nov  5 22:03:40 Nas kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Nov  5 22:03:40 Nas kernel: CR2: 0000149d02ff0000 CR3: 0000000103c3a006 CR4: 00000000003706f0
Nov  5 22:03:40 Nas kernel: Call Trace:
Nov  5 22:03:40 Nas kernel: <TASK>
Nov  5 22:03:40 Nas kernel: warn_thunk_thunk+0x16/0x30
Nov  5 22:03:40 Nas kernel: ? nvkms_alloc+0x62/0xa0 [nvidia_modeset]
Nov  5 22:03:40 Nas kernel: _nv003382kms+0x30/0xc0 [nvidia_modeset]
Nov  5 22:03:40 Nas kernel: ? sched_clock+0xc/0x20
Nov  5 22:03:40 Nas kernel: ? kmem_cache_debug_flags+0xc/0x20
Nov  5 22:03:40 Nas kernel: ? kmem_cache_debug_flags+0xc/0x20
Nov  5 22:03:40 Nas kernel: ? _nv003369kms+0x39/0xa0 [nvidia_modeset]
Nov  5 22:03:40 Nas kernel: ? _nv002973kms+0x44/0x50 [nvidia_modeset]
Nov  5 22:03:40 Nas kernel: ? __pfx_exact_match+0x10/0x10
Nov  5 22:03:40 Nas kernel: ? __pfx_exact_match+0x10/0x10
Nov  5 22:03:40 Nas kernel: ? nvKmsModuleLoad+0x25/0x200 [nvidia_modeset]
Nov  5 22:03:40 Nas kernel: ? __pfx_nvkms_init+0x10/0x10 [nvidia_modeset]
Nov  5 22:03:40 Nas kernel: ? nvkms_init+0x1a5/0xff0 [nvidia_modeset]
Nov  5 22:03:40 Nas kernel: ? __pfx_nvkms_init+0x10/0x10 [nvidia_modeset]
Nov  5 22:03:40 Nas kernel: ? do_one_initcall+0x81/0x1b0
Nov  5 22:03:40 Nas kernel: ? __kmalloc_cache_noprof+0x361/0x390
Nov  5 22:03:40 Nas kernel: ? do_init_module+0x22/0x230
Nov  5 22:03:40 Nas kernel: ? do_init_module+0x60/0x230
Nov  5 22:03:40 Nas kernel: ? init_module_from_file+0xac/0xe0
Nov  5 22:03:40 Nas kernel: ? __do_sys_finit_module+0x14a/0x270
Nov  5 22:03:40 Nas kernel: ? do_syscall_64+0x6b/0x7a0
Nov  5 22:03:40 Nas kernel: ? entry_SYSCALL_64_after_hwframe+0x76/0x7e
Nov  5 22:03:40 Nas kernel: </TASK>
Nov  5 22:03:40 Nas kernel: ---[ end trace 0000000000000000 ]---

nas-diagnostics-20261105-2216.zip

That message is not a CPU error, it's a warning the kernel logs once per boot when the Nvidia driver module loads. The proprietary Nvidia driver isn't built with one of the kernel's Spectre mitigation features, so the kernel prints that trace, but the GPU and the server work normally. The CPU number in it is just whichever core was loading the driver at that moment, which is why it changed. You can safely ignore it.

You also didn't need to reinstall, Unraid detects the new hardware on boot, and nothing in the diagnostics points to a problem with the upgrade.

The diagnostics look clean, but they were taken right after boot. If the server still feels sluggish, please describe what exactly is slow (the WebGUI, file transfers, a specific container, etc.) and when it happens, and post new diagnostics taken while it's happening.

Thank you JorgeB for replying, I appreciate that alot.

I did not reinstall I mi-spoke there, I was meaning to ask if I should. but you answer the question.

well I will check again and see, I would say when I connect the webgui and pres enter to the nas.local/login it can take 10-12 seconds before anything appears on screen (login screen of unraid)

after entering details, it will take 5-7 seconds to load the main screen of the server itself. and the rest of interface when I click a choice on menu will take about 3-4 seconds to switch from one screen to another

maybe I am imagining the speed slow down, but it seemed a lot snappier on the previous hardware. I walked around menus and posted another diagnostic.

I will say running movies, music or files there seem to be no issues. maybe it is just me?

additional edit: After thinking about it, I used the 192.xxx.xxx.xxx/login method instead of NAS. Local/login, and the web Gui was instantaneous and menus are snappy. I wonder why the difference?

nas-diagnostics-20261106-0754.zip

Edited 6 hours ago6 hr by PBUREAU66
additonal information added

That's a useful finding, and it means the server itself is fine. If the WebGUI is instant by IP address and slow only through Nas.local, the extra time is spent on your computer before the request reaches the server, resolving the name or picking the address to use. The new hardware isn't the cause.

Your server is set to IPv4+IPv6, so Nas.local can resolve to an IPv6 address as well as the IPv4 one. Some clients, especially Windows, can be slow to resolve .local names, or try IPv6 first and wait before falling back to IPv4.

To see which one it is, from the computer you use for the WebGUI please post the output of:

ping Nas.local

ping -4 Nas.local

Please also tell us which OS and browser you're using, and whether it's the same from another device.

In the meantime, using the IP address works well. Your server has a static IP, so it won't change. If you prefer to use the name, you can add an entry to the hosts file on your PC that maps Nas to 192.168.1.222, or add it as a DNS entry on your router if it supports that.