-
Nvidia card intermittently disappears
Update: nope, it's still happening. Worked absolutely fine for a while, now it's acting up again. I have a spare identical A2000 I can try, when I have some time.
-
Nvidia card intermittently disappears
@sgraaf as well - update: I've updated the BIOS (Asrock B550M Pro4 - the A2000 is in the first/main PCIe slot), and for whatever reason, it's now working solidly, for now at least. Honestly, no idea... will keep digging / monitoring and update this thread if this changes.
-
sergiup started following Nvidia card intermittently disappears
-
Nvidia card intermittently disappears
Running Unraid on a self-built box, up to date OS, Dockers, apps etc. I have an RTX A2000 6GB installed, which I use for Jellyfin transcoding and Ollama. I have to mention that it used to work absolutely fine a few months ago, even with both using the GPU at the same time. In the last month or so, it just... disappears. lspci still shows it, but nvidia-smi returns "No devices were found", and the GPU Statistics app shows the RTX A2000 but says "Vendor command returned unparseable data." At some random interval, it'll re-appear, the GPU Statistics app will show correct data, nvidia-smi will output correctly as well, but as soon as I try to use it within Ollama it'll disappear again. I've already tried to remove the Nvidia drivers, reboot, disable Docker, re-enable Docker, re-install Nvidia drivers, reboot, disable/re-enable Docker again with the relevant config, and nothing changes. Short of pulling it out and trying to diagnose the card in another Windows PC, I'm not quite sure what else to try... any ideas, please? Thank you! diagnostics-20250820-1858.zip
-
Tighter NFS permissions
I know I'm dragging this up from the past, but it's important; I've gone through this whole rigmarole as well, and I concur. "Private" is the most restrictive level, and will deny any NFS access to the share unless explicitly allowed using a rule (as above). You can use wildcard rules to allow various levels of access to an IP subnet or any non-specific IPs, although if using Private with a read-only rule for * then arguably you might be better off using Secure with additional rules for read-write for specific IPs.
-
Telegram Bot Notifications
Oh jeez, thank you for this! I was going to go through the whole chatid thing, but this worked absolutely fine. Thank you!
sergiup
Members
-
Joined
-
Last visited