• Content Count

  • Joined

  • Last visited

Community Reputation

5 Neutral

About Creativity404

  • Rank
  1. Try getting rid of "DOGE:" in your wallet adress
  2. Do you actually replace "mywallet" with your wallet? Show a screenshot of how you have the docker settings
  3. Do you understand your command line? also it is a windows command line so you can't just paste it into a terminal. edit the docker: basically you are going to edit the pool, your wallet, and the rest goes into additional xmrig arguments. Look here for the command line options and familiarize yourself with what your command line actually does: You should then understand what to put into additional arguments
  4. Update but without better/additional info: So after 3 days(usually just 1) of running without fail the problem has occurred again. I notice the problem has occurred because there will be 2-3 hyperthreads stuck on 100% I have been unable to try anything because this time the whole server became unresponsive since the thread of core 0 became "stuck". I could still see the dashboard since it was already open but i couldnt view any other page or open the web terminal. I went and looked at the physical machine but it just showed a black screen as output.
  5. I have disabled gpu drivers in order to tinker with passing through my gpu, and ever since (last night) the problem does not occur anymore. So when i had amdgpu & radeon drivers enabled the problem was consistent, and reproducable but now it seems to not occur at all. I prefer to pass through the GPU and leave the drivers dissabled. But that is a whole different problem i am struggling with. if i fail to pass through the GPU i will try to enable the drivers again and will continue to diagnose this problem.
  6. Sadly they are not just false errors, when i pass through the GPU i cant remote it with splashtop and can't ping it either
  7. Did you guys end up finding a fix?
  8. Thank you though, at least i got a little bit further.
  9. I am running latest-root When i mean a clean shutdown, i mean the whole server. The docker doesnt respond to anything, and when i try to reboot the server it hangs. i will have to go push the physical reset button or: echo 1 > /proc/sys/kernel/sysrq echo b > /proc/sysrq-trigger (^i found that online I'm a total linux noob) Pulling image: lnxd/xmrig:latest-root IMAGE ID [latest-root]: Pulling from lnxd/xmrig. Status: Image is up to date for lnxd/xmrig:latest-root TOTAL DATA PULLED: 0 B i forced an update but it was latest. I a
  10. Should i make a new diagnostic? And would the enabled drive rmodules be the reason as to why i couldnt bind the card? i will try to bind the GPU now, maybe it will work then Now i am able to bind the GPU and succesfully boot, but still stuck on: 2021-04-17 00:01:54.095+0000: Domain id=1 is tainted: high-privileges 2021-04-17 00:01:54.095+0000: Domain id=1 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial0)
  11. Ah, i was under the impression of the exact opposite 😅 thank you Now it says it has failed to mmap 2021-04-16 23:47:47.321+0000: Domain id=1 is tainted: high-privileges 2021-04-16 23:47:47.321+0000: Domain id=1 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial0) 2021-04-16T23:47:48.073497Z qemu-system-x86_64: -device vfio-pci,host=0000:0a:00.0,id=hostdev0,bus=pci.0,addr=0x5,romfile=/mnt/disk1/isos/vbios/HD7950.rom: Failed to mmap 0000:0a:00.0 BAR 0. Performance may be slow I have looked this up and fixed it with a script that runs at first
  12. Thank you for replying! The system does not boot when i bind them. similar to this persons post: Sorry i am very new to unraid and I did not know I could make a diagnostics report, i have found the function and made one. If i can help you or anyone else help me understand/diagnose my problem better in any way please let me know. i don't mean to be a person who just says: "it doesn't work plz fix it FOR me" I have googled and searched the forum but havent found an answer or a similar problem.
  13. After running this docker for a few hours the docker becomes unresponsive to shutdown/reboot. When i try to do anything with it the entire docker proces becomes unresponsive. I have not assigned the first core to the docker so unraid still runs and responds. but with the docker being unresponsive i am unable to do a clean shutdown. Any idea why this might be happening? I could make an hourly(or every 3-4) user script: But id prefer to know how/why it happens and if there is a neater solution. The docker keeps running/mining btw, just unresponsive and
  14. Is there a default passphrase or email configured if youd want to change your pool payout settings? I found it searching the thread, my bad. Thank you for this docker!