kenzo86

Hi. Thank you to all involved in making this docker possible. I had recently set it up and all is working well. However I received s notification this morning from my appdata backup plugin which related to the docker itself "Please check the backup log! '/tmp/tmp/pulse' does NOT exist! Please check your mappings! Skipping it for now." Any idea what this can be? I imagine I eill be getting this message every week. The template didnt mention anything about assigning a host path or making folders of any sort.

Thanks for replying. 1) I have attached diagnostics. 2) User scripts in settings --> create a script which runs the 'nvidia-persistenced' line on array startup. ''#!/bin/bash nvidia-persistenced'' 3) I use the GPU for Invoke-AI and hopefully for steam-headless later on. The throttled sw power cap status at idle resolves after a server reboot (gpu idle). I've spoken to another user (Pri) on the official discord who has had the same issue unresolved for a while. At 100% load, the 3090 is in P0 (throttled: sw power cap) - see attached screenshot of GPU statistics. I have also attached a screenshot of the GPU statistics at idle with sw power cap and gigher power draw (should be 14w idle) The gpu is connected via a type 5 cable (12pin to 8+8) to psu. I did not change anything in bios after installing the dGPU. tower-diagnostics-20241017-1442.zip

Hi Thank you for making this driver possible. I recently purchased a 3090FE and it was pretty much plug and play with the help of this driver. I have enabled persistence mode using a user script (First array start) and the GPU was sitting GPU IDLE (P8) at around 11w. There didnt seem to be an issue with the iGPU that i am using for plex transcodes / immich transcodes. 2 days on, i noticed it is now sitting idle in throttled SW POWER CAP ACTIVE, and at a higher wattage 24w. memory is sitting at 405 Mhz constant, Occasionally, it switches to GPU IDLE, but then back again to SW POWER CAP. I tried disabling dockers, restarting the server, but this hasnt helped. Any Ideas? nvidia-smi -q

hi. yes, all working through some trial and error!

Thanks

Thanks for helping. Cable comes this evening, I will try again and post back. How do I check to see that power isn't a contributing factor?

Hi all, I've just returned from holiday and noted server was off, likely due to a power cut. I switched the server back on and drive 1 of 8 (only drive being filled atm) has a red cross - emulated but disabled. Smart report showed UDMA CRC error counts – I noted this 2–3 months ago, e.g count of 16, now 1000ish. ?dodgy mini-sas cable? (edited) I've done another quick smart check - "Completed without error" and done a read check I've put the server into maintenance mode (xfs array) and did a check on the affected drive with "-n" flag, I then removed "-n" and re-ran it to repair. No obvious errors shown. I then unassigned the drive, started server, then stopped, re-assigned the drive from drop down and restarted server. It ran a parity and then threw out read errors / udma crc errors etc - and still shows as emulated 1) I've ordered new mini sas 8087 cables for hba (replace cheap cables that came with it). Other than this, is there anything else i should be doing / should have done?? 2) Do I repeat the above steps after changing the cables? Smart log https://paste.quest/?05c43af72a2bf856#BmRZYzEi8EikFQ2MP5NyRtzsggiGdxdDvgKp7MiyNBBy System log attached Drive check report attached tower-syslog-20230929-1040.zip

Hi all, I just got my dockers up and running and wanted to setup wireguard for remote access of arrs etc. My dockers are running on a custom network as per advice from Ibracorp videos. I have following the following guide to et wireguard running: I have set up the following but still am not able to connect via android mobile - see remarks in screenshots below accessing via http://tower.local/Main 1. Enabled upnp on both unraid management access / router + switched off router firewall (router is using 1.1.1.1 DNS) 2. Enabled bridging (Network settings) 3. Enabled `Host access to custom networks:` (Docker settings) 4. Routed default local tunnel network pool through IP address of unraid on router 5. Disabled `use nat` 6. Configured duckdns for ddns local endpoint (docker installed and working) Any ideas would be much appreciated!! Here is the routed IP address: Here is the tunnel config: NOTE: all addresses bar ddns autopopulated Docker settings: