rainmanjam
-
Posts
20 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by rainmanjam
-
-
-
3 hours ago, ich777 said:
Are you sure that your power supply is up to the task since most of the times it has to do with the power supply.
Do you have a display connected to actually see what's going on? It would be really cool if you have a display connected and you could take a picture what's happening on screen when it actually crashes.
I assume your machine is not automatically restarting?
I see nothing obvious from your syslog, the driver loads fine and it should in theory be working.
When I was hands on and watched it happen, the power just cut out and restarted the server
The power supply was fine. The power CABLE doesn't meet the specs for it.
https://www.evga.com/support/faq/FAQdetails.aspx?faqid=59690
Waiting on a 12 AWG cable to arrive. Sometimes you just need to get your eyes on it to figure out what's going on.- 1
-
30 minutes ago, ich777 said:
Are you sure that your power supply is up to the task since most of the times it has to do with the power supply.
Do you have a display connected to actually see what's going on? It would be really cool if you have a display connected and you could take a picture what's happening on screen when it actually crashes.
I assume your machine is not automatically restarting?
I see nothing obvious from your syslog, the driver loads fine and it should in theory be working.
No display connected so I can't see what's going on. I can connect one up.
I tailed the syslog via SSH but nothing stands out before crashing.
I have a 1200w power supply.
-
I'm having an issue where, consistently, when I use Nvidia drivers to do anything like LLM or even aHshcat for testing, Unraid crashes and I have to restart.
root@Tower:~# nvidia-smi -l Wed Mar 6 11:26:35 2024 +-----------------------------------------------------------------------------------------+ | NVIDIA-SMI 550.40.07 Driver Version: 550.40.07 CUDA Version: 12.4 | |-----------------------------------------+------------------------+----------------------+ | GPU Name Persistence-M | Bus-Id Disp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap | Memory-Usage | GPU-Util Compute M. | | | | MIG M. | |=========================================+========================+======================| | 0 NVIDIA GeForce RTX 3090 Off | 00000000:65:00.0 Off | N/A | | 0% 62C P0 119W / 420W | 0MiB / 24576MiB | 0% Default | | | | N/A | +-----------------------------------------+------------------------+----------------------+
-
Ok. I figured it out. using "--runtime=nvidia" in the "Extra Parameters:" container options throws an egg in the soup and causes crashes. Removing it stabilized everything.
-
I think this is an issue between docker/unraid/nvidia because I've been running the hashcat docker container and it crashes there as well.
-
It's the craziest thing. If anyone can help me find the issue, it would be appreciated.
-
-
If I can move everything off the cache portion to somewhere else, that would help a lot.
-
The initial idea was to use either cache or Fastlane as a caching read/write drive for data transfers. I'm just trying to get some advice on the best setup for the array of disks I currently have to make it faster for transfers and have stability with my VM/Docker services.
-
-
Thanks @trurl. I deleted Tabby from the appdata folder and that freed up space to get it back up and running.
- Docker and Libvirt were tested and are working fine.
- I brought it back down to 20G. I didn't know what adjusting the space would do bringing on a large docker instance.
- Fixed.
- Any advice on space adjustments?
-
-
https://github.com/milvus-io/milvus
https://hub.docker.com/r/milvusdb/milvus
Not really getting an error I can point to as to why it stops. -
Has anyone had issues with docker updates where 0.225.1 is installed and it won't update to 0.226.2 unless you force it in the configuration?
-
-
-
-
Having the same problem. I've changed DNS Servers and got the same issue.
Any ideas?
Everything is showing as protected. Default docker appdata location is not a cache-only share.
in General Support
Posted
How can I fix this?