dezai

Hey Guy´s, i can confirm that the problems from the "wrong cable errors" came from the 2x750W PowerSupplies. I´m now using the 2x1100w and it is working. But i have another problem, Tesla P40 doesnt go to the Idle State - it stay´s at P0 and uses 50W, is there a fix for that?

No no all good it is a 8Pin EPS 12V from the Riser and a 8 Pin EPS 12V in the GPU - and i´ve got a cable for exact that setup / R730 - Tesla P40. But the R730xd can only Support 250W GPU´s with the 1100W PSU´s. In my server are the 750W PSU´s - if you are using those the PCIE Riser only gets 125-150W to the 8 PIN 12V EPS Connector. Thats the reason why every GPU in my house is working correctly but the P40 did not. If you are using the 1100W PSU you will get 225W to the 8 PIN 12V EPS Connector / 75 from the PCIE Slot. I´ve got 2x 1100W PSU´s from a reseller for 17,50€ each, i can test it hopfully next week. Part from a reddit thread with the same Problem:  GPUs require a redundant 1100W power supply and GPU enablement kit I will get back in touch here when the PSU´s are in the Server.

Ok i did some research and it was the last thing i thought about. I´m using the R730xd with 2x750W PSU ,CPUs are 2x120W ,P40 250W, so i thought i´m fine with the 2x750W (i´ve also tried non redundant mode). After some research i found out, that Dell is limiting the GPU TDP to 150W (even if you use the 225W Riser) if you are using the 750W PSU. So my GTX 970 is working fine / P2000 is also working just fine. But the P40 doesnt work..... I´m trying to get 2x 1100W PSU´s now..... Yep i did use the Spaceinvader Script, i´ve deleted it now and put the nvidia-persistenced command in to the "go file" And yep i´m using your Driver for a long time So a little conlusion.....if my Dell server would give the p40 250W - it should work out of the box with the driver? 😮 😮

🥰Ok let´s try it Attatched the Diagnostics / Screenshot from the P40 in System Devices / Screenshot from your great driver with the working P2000 r730xd-diagnostics-20240120-2122.zip

Hi guy´s, i think i fucked up. I´ve got a P40 for real cheap and i thought it would be a great card for Unraid - Docker - Stable Difuion / Comfy-UI. But i think it is not supported in the driver v545.29.06 Is there a way to get this to work in docker? My System Dell R730xd (no reBar Support - only above 4G SR-IOV etc.) 2x E5-2680 V4 128GB DDR ECC RAM A lot of SSD Storage With best regards Marc

Hi guy´s is there a fix for that problem? I´ve come back from Truenas to unraid and installed AMP. The last time i´ve used unraid the AMP Docker worked perfectly but now no Steam Game loads and it is stuck at this loop displayed in randit´s screenshot. Are there solutions for this problem?

Hey Guys, i´m trying to passtrough a 5700 XT to a windows VM. I´ve followed every steps from Spaceinvader. - Exportet vbios in Windows using GPUZ - Changed the Maschine Typ to Q35-4.2 - Edited the XML GPU settings (routed the Sound Part to the same slot, etc. everything from the spaceinvader video The Problem is, maschine is booting up (checked it with existing windows VDISK and fresh one), but nothing happens (i only see the moment when the VFIO Settings are reservating the GPU (i´ve set this up in unraid 6.9 - there it is integrated in System devices) If i connect to the vm using RDP i can see the screen but under Device Manager there is no AMD GPU (MS Basic WIndows Adapter) The funny thing is, if i try this with a linux VM - everything is working fine and i receiv the bootscreen etc. Can you please tell me what i´ve done wrong with the windows VM?

so far.....the drive errors have gone but i get now new errors, i can´t get da diagnostics data and i can´t see the docker/vm´s in the dashboard. But they are still running. Errors in the syslog: Apr 20 22:58:20 Tower kernel: CPU: 10 PID: 3278 Comm: kworker/10:2 Tainted: G O 4.19.107-Unraid #1 Apr 20 22:58:20 Tower kernel: Call Trace: Apr 20 23:12:14 Tower kernel: CPU: 5 PID: 26716 Comm: kworker/u64:5 Tainted: G W O 4.19.107-Unraid #1 Apr 20 23:12:14 Tower kernel: Call Trace: Apr 20 23:15:14 Tower kernel: CPU: 5 PID: 26716 Comm: kworker/u64:5 Tainted: G W O 4.19.107-Unraid #1 Apr 20 23:15:14 Tower kernel: Call Trace: And the server locked up again today. I´ve set this fix from spaceinvader a few weeks ago: rcu_nocbs=0-15 For me as a linux noob it appears, that there is an issue with the cpu?

Sorry in my masseage 5 hours ago ther was no new diagnostics. Attatched the diagnostics from the past 6 hours. It looks good at this moment.tower-diagnostics-20200419-1449.zip

can it be a cable problem? After changing the ssd the other ssd spit out errors - no i changed to another sata cable and everything is fine after the reboot. I give it some time again and keep you updated

Ok Problems are stil lthere......attatched new diagnostics....tower-diagnostics-20200419-0831.zip Parity Sync is stuck at 50% - drives are spindown - some docker containers went offline this morning. I don´t know what i can do with this build - that is realy horrible

Ok one of my ssd´s is damaged SDC can´t get formatted any more and spit out BTRFS Errors. I remove this ssd ent test the server again. RAM is after 6 hours memtest ok - no errors. I order no one new Cache drive SSD for the server A littlebit strange is, that i can use it in windows "normaly" - crystaldisk info is telling me that the drive is ok?

if i reboot the server it get stuck completly. pause unpause is not possible..... Is there anything else which is a problem in the diagnostics?

Hi Guy´s, sorry but i have new problems with my server. Last weekend my server locked completly down. I couldn´t get into the webui/ssh into the server. So i killed him and he started normaly after that and he started a parity sync. And now he is stuck at this sny at 5%. Attatched the diagnostics - can you please help me with that? I´ve upgraded the storage pool last week (started with a completly new pool with new drives and copied everything from the backup server). Everything is up and running - only the parity sync is stuck. tower-diagnostics-20200416-2048.zip

Thank you for your help johnnie.black. The Server is up and running since yesterday No more bad logs - all the Dockers and VM´s are back up and running. Everything is fine with the LSI HBA Currently i´m only waiting for a good price for 8-14 TB HDD´s to upgrade my server and build a backup Server with the 3TB WD Drives.

lame.........HBA deliverydate is next monday

The First Controller was 6 Port that was correct. I thought that i have a funcional 4 Port but With that one of geht read Errors With the connected SSD Cache. So i Turn down the Box for a cupple of days and wait for the 9211-8i which ist already IT Mode flashed. I hope that will fix the Problems..... Product links to the old Cards https://www.amazon.de/dp/B00AZ9T3OU/ref=cm_sw_r_other_apa_i_vVItEbNVE12EZ https://www.amazon.de/dp/B07THFN3Q2/ref=cm_sw_r_other_apa_i_nUItEb0X2P25H

Ok i´m done with that card - ordered now a HBA. Hope this will arrive asap. I´m using actually a 4 port sata controller and actually everything is fine. I hope everything is fixed with the hba.

So switching to a LSI 9211-i8 flashed it mode can solve the problem?

Hi Guy´s update time....... .....pc doesnt´crash and BTRFS errors are away - now i have the same problems in you´re link: I set the option for typical current idle but it did not fixed my problems. Attatched new diagnostics file. Problem is - my array is working fine - but i can´t open my docker containers and there are new errors in the diagnostics....: Feb 19 19:18:31 Server kernel: ata10.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Feb 19 19:18:31 Server kernel: ata10.00: failed command: WRITE DMA Feb 19 19:18:31 Server kernel: ata10: hard resetting link Is there a known fix for that? I´m realy sad about the actual situation because i had everythng running one week ago..... Could it be a problem with the sata controller i´ve built in? https://www.amazon.de/gp/product/B07THFN3Q2/ref=ppx_yo_dt_b_asin_title_o07_s00?ie=UTF8&psc=1 server-diagnostics-20200219-1915.zip

Ahhhhh ok i didn´t know that but i also received informations, that sdj (parity disk) spit out errors so i wanted to start from zero I have a backup for all data so that is now big problem. Just a matter of time Ok i realy think this solved the problem for me. If i set everything on auto in the bios it set the ram to 1866mhz, so i set this to manualy 1866 mhz and actually everything is fine after 2 hours. I´m starting to put the files from the backup onto the array and see tomorrow what the logs looks like. But at this moment - zero errors. Thank you very very much.

Oh ok that could be the problem. Today i thought it is a good idea to start from zero and i formatted all the drives - create new cache and drive pool. But the server ist now offline after 2 hours. I know, that i´ve set the ram 4x 8GB DDR4 3200mhz ram with xmp to 3200mhz with 4x8tgb. So yes.....that is the problem i think. I´m currently at the office - i will check this today and read the link from you - but after the first informations, ram is an obvious problem in my configuration.

Hi Guys, at first sorry for my bad english :). I was realy happy since last week with my unraid build. It is online since round about 1-2 years with no problems with a socket 1150 base. I upgraded to a ryzen plattform last week and i used the tutorial from spaceinvade one (thanks to you man, the videos are realy amazing). I´ve added the line, "kernel /bzimage append rcu_nocbs=0-15 initrd=/bzroot" to the usb stick for my ryzen 7 1700 So since last weekend my unraid build is spamming BTRFS cristical (device md2) all over the screen if the array is started. And after round about 20 minutes it came to a dead end where the server is shutting down - hang up. With "end trace e162fe777f177cd9" At first i thought it is the parity drive, so i removed the parity drive but the problem is the same. I also diabled the cache array - same problem. Don´t worry i have a backup from all that data. Sooo....what do you need from me to help me with this problem? Syslog attatched. at this moment when the errors appear i turned off the array. and if i put the parity into the array (actually i preclear the parity), these errors appears without turning off the array. At this point i don´t know what to do anymore...... syslog.txt server-diagnostics-20200217-2154.zip

Good Morning Guy´s, thank you ich77 for these new dockers. At this moment i test the csgo docker, in the network everything works fine, but with set Steamusername and password and portforwarding 27015 + DYNDNS adress it doesn´t appear in the online list, only in the lan list. Is there something i forgot? I don´t know if it´s possible but a Dayz Standalone server would be nice

Thank you for youre answer. I´ve tested last night, what happens when i only set the DNS in my Fritzbox Router. Not in the WIndows client. When i use this, steamcache creates folders when i use battlenet. But not with Steam. But i changed yesterday a lot in my server. So i try to test it today after work and set no secondary ip adress in my router and see if this fix my problem. EDIT: hmmmmmmit´s so strange. Now it doens´t work... Settings: I reinstalled the docker container, no errors, in the powershell everything is ok. But when i downloade a game nothing happend. ALSO one strange thing is, when i turn the steamcache docker off. I can browse normaly.......but why? The DNS Server is OFFLINE......why i can browse normaly in the www? I don´t understand where is my fault? Ok.....is ther a problem if i haven´t a ipv4 adress? In Germany you only get a ds-lite tunnel. An other guy has the same problem: https://github.com/steamcache/steamcache-dns/issues/24 I think my problem is ipv6 Ohhhh i hate my internetprovider. My Internetconnection has no IPV4. And all my IPV4 requests are tunneld through IPv6.......so i have NO IPV4 requests and steamcache can´t cache anything. Is that right? And how can i change that?