-
Consant crashes on gpu usage with ryzen
For me it was that 1 of my vm’s and 1 of my docker container tried to use more ram that what was assigned so server just turned off. you could try to disable your docker containers and see if the issue still persist when you install your vm. Also do install a plugin called fix common problems to see if that catches on anything. If you’re using something to download media try disabling it and then try everything
-
Consant crashes on gpu usage with ryzen
SOLVED. Was a memory issue where it only used 0.5Gb of ram and overloaded and crashed.
-
Help with IOMMU Binding
Hello! I'm having a lot of issues binding one of my gpu's to VFIO. i just installed a geforce gtx 1080TI to my server and when i go in system devices to bind my gpu to VFIO to boot its grayed out and says "in use by unraid", i can't for the life of me figure out what its being used to or how to pass it through. i've tried without having vm's and dockers enabled and uninstalled all plugins but i keep getting the same message. Does anyone have any idea what could cause this?
-
Consant crashes on gpu usage with ryzen
Server crashed around 8 times within 24 hours, same as before, tried moving the p2000 to different pci slot and removed the 1080ti still same issue, even with just the 1080ti on another pci slot
-
AceBoyden started following Consant crashes on gpu usage with ryzen
-
Consant crashes on gpu usage with ryzen
Hello! Some time back ago i made a similar post to this one and that is my unraid server keeps crashing if gpu is being used. I.E i watch something on jellyfin or plex it might crash, the server does not crash if my gpu's aren't being used so it can stay up for days just fine, but as soon as someone uses my plex or jellyfin there is a chance it will crash, it can happen almost instantly from it being used or an hour in or so (i think depending on file type). So i am once again asking if anyone can see something that is in my diagnostics (from the most recent crash, i watched a show and it crashed). i have tried doing a memtest aswell and that is all fine. tried installing my p2000 and using that and it works great until server crashes. Tried running unraid without plex or jellyfin (no crashes, i can run them fine by itself, as soon as someone waches something then theres an issue). i have tried different ram, only 1 drive, no gpu, safemode, different motherboard, different cpu (same type but different chip) and disabling c-type, set ram speed to 2933 and power setting in bios as was recommended for keeping ryzen servers stable. Ryzen seems to not be able to log "Machine Check Events detected on your server" as good as intel not sure why but i can't see anything except for the standard safe to ignore messages from MCE: Syslinux conf: OS GUI kernel /bzimage append rcu_nocbs=0-23 initrd=/bzroot,/bzroot-gui video=efifb:off OS kernel /bzimage append rcu_nocbs=0-23 initrd=/bzroot video=efifb:off Server parts: Motherboard: ASUS TUF GAMING B550-PRO CPU: AMD Ryzen 9 5900X 12-Core RAM: 128 GiB DDR4 Multi-bit ECC Storage: Seagate IronWolf PRO 3,5" NAS HDD 8TB x6 Cache: Kingston KC3000 M.2 2280 NVMe SSD 1TB Encoding gpu: Quadro p2000 VM GPU: Geforce gtx 1080TI If anyone has any ideas as to why this happends please do let me know, i will be forever thankful fatbeast-diagnostics-20230612-0158.zip
-
Parity Disk on new tower fails
Ok when i’ll get home i’ll change speed to 2933 and hopefully that’ll fix some stuff
-
Parity Disk on new tower fails
I am using ECC ram yes, not sure why it says i have overclocked ram when its on auto in bios 😛
-
Parity Disk on new tower fails
Appears i have some ECC errors? fatbeast-syslog-20230301-0846.zip
-
Parity Disk on new tower fails
Hopefully they work, i cant see anything special in there fatbeast-syslog-20230301-0757.zip fatbeast-diagnostics-20230301-0856.zip
-
Parity Disk on new tower fails
It appears the crashes was caused by the thumb drive, i changed it out and did a mew fresh install and now it seems stabel-ish, still gives me some machine errors (can post logs later but unavailable right now), and the array has stopped twice, stopped by "areay health check failed", i tested all my drives after this and none came up bad and they were all perfect, anyone got any ideas on that issue?
-
Parity Disk on new tower fails
not sure if relevant but the "crashed" has happened 19 times in a span of 1 hour edit: disabled c sate in bios now so i'll see how it goes tomorrow if that helped any way edit edit: after checking sys logs after disabling c state im not getting an error im not fully sure what means, if it is the cpu or the ram.. bigboy-diagnostics-20230225-2341.zip bigboy-syslog-20230225-2241.zip
-
Parity Disk on new tower fails
I disabled overclocking on the ram and set it to "auto" in bios, same as set the "Power Supply Idle Control" to "typical current idle" in bios as well. i changed the ram to check (removed one by one and did a new set aswell) yet still have the same issues, it appears it dosn't happen if array is started in maintanance mode (this only lasted 11 hours as that was the time the parity sync took, then i startet array normally). it went fine for a few hours then saw the server was down again (not fully down but array had been stopped and auto start was set to "no" again). it appears what happends is that the OS itself restarts but not the system, i was in my server room while the crash happened and saw on my monitor in there that the os was restarting but not the system itself. i tried checking the drives and unplugging 1 by 1 there aswell and tested everyone alone, still same problem occoured. i can have no vm's or containers running and it will still happend, none of my friends or collegues can find any errors physical or in the diognostic logs i sent them before and after the crashes. any other suggestions? (also changed cpu to the same type just a different one i had spare and problem is still there) could it be my usb stick i have unraid on? everything should be fine there aswell
-
Parity Disk on new tower fails
it seems to only reboot after the rust server on pterodactly starts, i moved that first to start (rebooted immidetly), moved it last (rebooted after some time) and now i deleted that one and it has not rebooted yet, started array in maintance now to see if that works for parity sync, but i still keep getting "machine check events - Your server has detected hardware errors" but not sure where to find whats wrong on where
-
Parity Disk on new tower fails
*sorry, it reboots after around 10 minutes of being on, not stopping array alone. not sure why it keeps rebooting after being on for around 10 minutes, i fear it might be something to do with the cache drive and how i set it up in appdata but im no genius
-
Parity Disk on new tower fails
not sure why but after that reboot the array turns off around 10 minutes being on and i need to turn them on, also auto start keeps turning back to off from on