sakh1979

Hi @ich777 , Doing pre-purchase due diligence before buying an RTX 5060 Ti for local LLM (Ollama) + Frigate vision + Plex on my unRAID box, and wanted to check with you directly given you've mentioned owning Blackwell hardware yourself. My setup: Currently on a GTX 1070 (Pascal), unRAID 7.2.5, Supermicro X11SSM-F / Xeon E3-1245 v5. Planning to replace it with a PNY RTX 5060 Ti 16GB (GB206). What looked promising: SpaceInvaderOne's Feb 2026 "Paperless-ngx Part 3" tutorial shows a clean setup — RTX 5070 Ti (GB203), Open Source Driver v590.48.01, selected from a version-pinned list in the plugin, Update & Download, restart, done. No issues shown. What gave me pause: I found a separate report of an RTX 5060 Ti (GB206 specifically) failing to initialize on unRAID 7.2.4, driver 595.71.05 open-source. lspci sees the card, kernel modules load (nvidia, nvidia_uvm, nvidia_drm, nvidia_modeset), but nvidia-smi reports "No devices were found." dmesg shows: NVRM: GPU0 kbusVerifyBar2_GB202: MMUTest BAR2 readback VA = 0x0 returned garbage NVRM: GPU0 RmInitNvDevice: *** Cannot initialize the device NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x24:0x72:1344) NVRM: GPU0 _kgspBootGspRm: unexpected WPR2 already up, cannot proceed with booting GSP NVRM: GPU0 RmInitAdapter: Cannot initialize GSP firmware RM I also found this same WPR2/GSP-boot error class as two separate open, unresolved issues on NVIDIA's own open-gpu-kernel-modules repo (on different hardware, not GB206) — and apparently this error family goes back to driver branches on Turing/Ampere too, so it looks like a known-but-intermittent NVIDIA firmware quirk rather than something specific to Blackwell, GB206, or your plugin. Questions, if you have a minute: Have you tested or heard reports of a GB206 (RTX 5060/5060 Ti) specifically on unRAID? Any known issues, or is it working cleanly for others? Is there a specific driver version you'd currently recommend for a fresh GB206 install? Any known BIOS-side mitigation for this GSP-init failure class — specifically Above 4G Decoding / Resizable BAR? Is this the kind of thing your open-source driver CI work (I saw the PR building version-pinned nvos builds) would eventually help with, or is it purely upstream NVIDIA GSP firmware territory outside the plugin's control either way? Haven't bought the card yet — trying to get real data before spending ~$600 rather than finding out the hard way. Appreciate anything you can share.

@JorgeB, thank you for your input and time. I will order a new set of cables and replace the existing ones. I have already order a new hard drive. If new errors are logged then I'll replace the drive as well.

Here is the result from the extended SMART test. @JorgeB, could you please review the result? tower-smart-20251205-0701.zip

@JorgeB, thanks for looking at the logs. I have started the extended SMART test on the parity disk. I'll report back after the completion with the result.

All - On December 1st, while running the monthly Parity Check, I was altered that there were 168 errors on the parity drive. Could someone please take a look at the attached log and let me know the next steps to remedy this? Thanks! tower-diagnostics-20251203-2344.zip

Hello - I saw this segfault error message in the unRAID log this morning. Could you please help me understand what is causing this error message? Apr 23 17:49:24 Tower emhttpd: read SMART /dev/sdf Apr 23 18:03:00 Tower kernel: PMS GTP[28513]: segfault at 4b10 ip 0000151f881b87ca sp 0000151f7d6fe908 error 4 in ld-musl-x86_64.so.1[151f881a8000+53000] Apr 23 18:03:00 Tower kernel: Code: 14 66 85 d2 74 02 f4 9b 8b 57 f8 81 fa ff ff 00 00 7f 02 f4 9b 83 e1 1f 89 d0 c1 e0 04 48 98 48 29 c7 48 8b 47 f0 48 83 c7 f0 <48> 39 78 10 74 02 f4 9b 8b 70 20 83 e6 1f 39 ce 73 02 f4 9b 8b 78 Apr 23 18:04:03 Tower kernel: traps: PMS GTP[24800] general protection fault ip:1496b29b87d0 sp:1496a92aa908 error:0 in ld-musl-x86_64.so.1[1496b29a8000+53000] Apr 23 18:05:03 Tower emhttpd: read SMART /dev/sde Apr 23 18:05:33 Tower emhttpd: read SMART /dev/sdg Diagnostics attached as well. Thanks, Sagun tower-diagnostics-20230424-0721.zip

Thank you for confirming! I came here to verify that the host-passthrough mode works before I upgrade to 6.9. I have been holding back upgrading from 6.7.2 to 6.8.3 just for this reason.

+ 1 Please add docker-compose

I see it, thanks Joe.

Hi Joe - I do not see a link to download preclear_disk.sh even after I have logged in: http://lime-technology.com/forum/index.php?topic=2817 Is there something I am missing? Thanks, Sagun