Creativity404
-
Posts
18 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Creativity404
-
-
8 minutes ago, miker905 said:
Lol. Yes of course....See below. It would be good if the "Coin" field wasn't mandatory.
Try getting rid of "DOGE:" in your wallet adress
-
1
-
-
7 minutes ago, miker905 said:
Hi,
I realize its a windows command line, I was just copying to show the parameters I use in windows. When I attempt to do this in docker I get a "Execution Error" / "Server" error. I assume it is because the way Unmineable needs to see the Wallet. "DOGE:walletID.tag". As you can see from the command line I don't specify a coin either with a command line. I am unable to find any details for the error that pops up when I start the docker.
* I have just started using Unraid and am very much a newbie.
thanks
Mike
Do you actually replace "mywallet" with your wallet?
Show a screenshot of how you have the docker settings -
On 4/26/2021 at 1:01 AM, miker905 said:
Quick question. I run xmrig on a pc and thought I'd like to run it on the unraid server as well. How would I pass the following command line through this docker image?
xmrig.exe -o rx.unmineable.com:3333 -a rx -k -u DOGE:mywallet.mytag
Thanks
Mike
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:
https://xmrig.com/docs/miner/command-line-options
You should then understand what to put into additional arguments-
1
-
-
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.
I will troubleshoot/diagnose at the next opportunity.
-
1
-
-
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. -
4 hours ago, joecool169 said:
I don't know if this helps you any, but my vm always has that at the bottom if the log and yet it works fine. I read somewhere here that those aren't really errors.
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
-
Did you guys end up finding a fix?
-
11 hours ago, John_M said:
I'm afraid I don't know what to suggest to help you any further.
Thank you though, at least i got a little bit further.
-
1 hour ago, lnxd said:
🤔 This is odd. Can you please force an update to the container to make sure you are on a version that handles sigterm, and then please share your diagnostics.zip when the container is unresponsive? Also, are you running the latest-root tag or latest?
When it is unresponsive, do the logs not load via docker logs XMRig -f as well as the Unraid WebUI or just the WebUI? And does the first command output something and then not continue, or output nothing at all?
Also, when you say a clean shut down do you mean of the container or does it hang your whole server during a shutdown? Because when you shut down, Unraid will try stopping the docker daemon, which tells docker to send sigterm to all running containers, and after about 10 seconds it will send sigkill to them.A couple of things to try:
- docker exec -ti XMRig apt-get install -y htop && htop
- When it is frozen, can you please run docker stop ----time=60 XMRig, see if it takes the full minute to stop. If it does, this means sigterm is failing. This shouldn't happen, but your diagnostics.zip could explain why it does.
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 Bi forced an update but it was latest.
I am going to try:
docker logs XMRig -f
- docker exec -ti XMRig apt-get install -y htop && htop
- When it is frozen, can you please run docker stop ----time=60 XMRig, see if it takes the full minute to stop. If it does, this means sigterm is failing. This shouldn't happen, but your diagnostics.zip could explain why it does.
I will report back 😃
-
20 minutes ago, Creativity404 said:
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 slowI have looked this up and fixed it with a script that runs at first array start:
echo 0 > /sys/class/vtconsole/vtcon0/bind
echo 0 > /sys/class/vtconsole/vtcon1/bind
echo efi-framebuffer.0 > /sys/bus/platform/drivers/efi-framebuffer/unbindNow failed to MMAP has dissapeared but i am once more stuck on the same:
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)
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 thenShould 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 thenNow 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) -
26 minutes ago, John_M said:
You have both the amdgpu and radeon driver modules enabled and installed. You can't pass through a GPU that's bound to a Linux driver. You need to revert to the default condition of having them blacklisted to stand any chance of using the GPU in a VM.
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 slowI have looked this up and fixed it with a script that runs at first array start:
echo 0 > /sys/class/vtconsole/vtcon0/bind
echo 0 > /sys/class/vtconsole/vtcon1/bind
echo efi-framebuffer.0 > /sys/bus/platform/drivers/efi-framebuffer/unbindNow failed to MMAP has dissapeared but i am once more stuck on the same:
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)
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 -
27 minutes ago, John_M said:
Diagnostics would be more useful than screenshots. What happens if you bind both items in IOMMU group 22 to the VFIO driver?
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.
-
-
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:
Quote#!/bin/bash
docker restart XMRig
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 logs dont load.
-
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!-
1
-
-
Hello everyone,
I am a new and inexperienced user of unraid and I am trying to pass through my primary (and only) AMD GPU
I am using Legacy not UEFI
The vbios is made/extracted/dumped by using this actual card.
If anyone has any suggestion i will gladly try them. A solution would make my day and make me very gratefull.System hardware:
MB: Gigabyte aorus x570 pro wifi ITX
CPU: Ryzen 7 2700GPU: Radeon Sapphire HD7950
VM log:
QuoteErrorWarningSystemArrayLogin
-uuid 3a72533f-3cd1-3cfb-472f-f158cbddb7ee \
-display none \
-no-user-config \
-nodefaults \
-chardev socket,id=charmonitor,fd=31,server,nowait \
-mon chardev=charmonitor,id=monitor,mode=control \
-rtc base=localtime \
-no-hpet \
-no-shutdown \
-boot strict=on \
-device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x7.0x7 \
-device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x7 \
-device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x7.0x1 \
-device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x7.0x2 \
-device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x3 \
-blockdev '{"driver":"file","filename":"/mnt/user/domains/Windows 10/vdisk1.img","node-name":"libvirt-3-storage","cache":{"direct":false,"no-flush":false},"auto-read-only":true,"discard":"unmap"}' \
-blockdev '{"node-name":"libvirt-3-format","read-only":false,"cache":{"direct":false,"no-flush":false},"driver":"raw","file":"libvirt-3-storage"}' \
-device virtio-blk-pci,bus=pci.0,addr=0x4,drive=libvirt-3-format,id=virtio-disk2,bootindex=1,write-cache=on \
-blockdev '{"driver":"file","filename":"/mnt/user/isos/Win10_20H2_v2_EnglishInternational_x64.iso","node-name":"libvirt-2-storage","auto-read-only":true,"discard":"unmap"}' \
-blockdev '{"node-name":"libvirt-2-format","read-only":true,"driver":"raw","file":"libvirt-2-storage"}' \
-device ide-cd,bus=ide.0,unit=0,drive=libvirt-2-format,id=ide0-0-0,bootindex=2 \
-blockdev '{"driver":"file","filename":"/mnt/user/isos/virtio-win-0.1.190-1.iso","node-name":"libvirt-1-storage","auto-read-only":true,"discard":"unmap"}' \
-blockdev '{"node-name":"libvirt-1-format","read-only":true,"driver":"raw","file":"libvirt-1-storage"}' \
-device ide-cd,bus=ide.0,unit=1,drive=libvirt-1-format,id=ide0-0-1 \
-netdev tap,fd=33,id=hostnet0 \
-device virtio-net,netdev=hostnet0,id=net0,mac=52:54:00:4d:c3:3b,bus=pci.0,addr=0x2 \
-chardev pty,id=charserial0 \
-device isa-serial,chardev=charserial0,id=serial0 \
-chardev socket,id=charchannel0,fd=34,server,nowait \
-device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \
-device usb-tablet,id=input0,bus=usb.0,port=1 \
-device ich9-intel-hda,id=sound0,bus=pci.0,addr=0x8 \
-device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 \
-device 'vfio-pci,host=0000:09:00.0,id=hostdev0,bus=pci.0,addr=0x5,romfile=/mnt/user/isos/vbios/Sapphire HD7950 Tahiti.rom' \
-device vfio-pci,host=0000:09:00.1,id=hostdev1,bus=pci.0,addr=0x6 \
-sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \
-msg timestamp=on
2021-04-08 23:53:11.127+0000: Domain id=1 is tainted: high-privileges
2021-04-08 23:53:11.127+0000: Domain id=1 is tainted: host-cpu
char device redirected to /dev/pts/0 (label charserial0)XML file:
Quote<?xml version='1.0' encoding='UTF-8'?>
<domain type='kvm'>
<name>Windows 10</name>
<uuid>3a72533f-3cd1-3cfb-472f-f158cbddb7ee</uuid>
<metadata>
<vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/>
</metadata>
<memory unit='KiB'>5242880</memory>
<currentMemory unit='KiB'>5242880</currentMemory>
<memoryBacking>
<nosharepages/>
</memoryBacking>
<vcpu placement='static'>14</vcpu>
<cputune>
<vcpupin vcpu='0' cpuset='1'/>
<vcpupin vcpu='1' cpuset='9'/>
<vcpupin vcpu='2' cpuset='2'/>
<vcpupin vcpu='3' cpuset='10'/>
<vcpupin vcpu='4' cpuset='3'/>
<vcpupin vcpu='5' cpuset='11'/>
<vcpupin vcpu='6' cpuset='4'/>
<vcpupin vcpu='7' cpuset='12'/>
<vcpupin vcpu='8' cpuset='5'/>
<vcpupin vcpu='9' cpuset='13'/>
<vcpupin vcpu='10' cpuset='6'/>
<vcpupin vcpu='11' cpuset='14'/>
<vcpupin vcpu='12' cpuset='7'/>
<vcpupin vcpu='13' cpuset='15'/>
</cputune>
<os>
<type arch='x86_64' machine='pc-i440fx-5.1'>hvm</type>
<loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader>
<nvram>/etc/libvirt/qemu/nvram/3a72533f-3cd1-3cfb-472f-f158cbddb7ee_VARS-pure-efi.fd</nvram>
</os>
<features>
<acpi/>
<apic/>
<hyperv>
<relaxed state='on'/>
<vapic state='on'/>
<spinlocks state='on' retries='8191'/>
<vendor_id state='on' value='none'/>
</hyperv>
</features>
<cpu mode='host-passthrough' check='none' migratable='on'>
<topology sockets='1' dies='1' cores='7' threads='2'/>
<cache mode='passthrough'/>
<feature policy='require' name='topoext'/>
</cpu>
<clock offset='localtime'>
<timer name='hypervclock' present='yes'/>
<timer name='hpet' present='no'/>
</clock>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>restart</on_crash>
<devices>
<emulator>/usr/local/sbin/qemu</emulator>
<disk type='file' device='disk'>
<driver name='qemu' type='raw' cache='writeback'/>
<source file='/mnt/user/domains/Windows 10/vdisk1.img'/>
<target dev='hdc' bus='virtio'/>
<boot order='1'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
</disk>
<disk type='file' device='cdrom'>
<driver name='qemu' type='raw'/>
<source file='/mnt/user/isos/Win10_20H2_v2_EnglishInternational_x64.iso'/>
<target dev='hda' bus='ide'/>
<readonly/>
<boot order='2'/>
<address type='drive' controller='0' bus='0' target='0' unit='0'/>
</disk>
<disk type='file' device='cdrom'>
<driver name='qemu' type='raw'/>
<source file='/mnt/user/isos/virtio-win-0.1.190-1.iso'/>
<target dev='hdb' bus='ide'/>
<readonly/>
<address type='drive' controller='0' bus='0' target='0' unit='1'/>
</disk>
<controller type='pci' index='0' model='pci-root'/>
<controller type='ide' index='0'>
<address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
</controller>
<controller type='virtio-serial' index='0'>
<address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
</controller>
<controller type='usb' index='0' model='ich9-ehci1'>
<address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/>
</controller>
<controller type='usb' index='0' model='ich9-uhci1'>
<master startport='0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/>
</controller>
<controller type='usb' index='0' model='ich9-uhci2'>
<master startport='2'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/>
</controller>
<controller type='usb' index='0' model='ich9-uhci3'>
<master startport='4'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/>
</controller>
<interface type='bridge'>
<mac address='52:54:00:4d:c3:3b'/>
<source bridge='br0'/>
<model type='virtio-net'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
</interface>
<serial type='pty'>
<target type='isa-serial' port='0'>
<model name='isa-serial'/>
</target>
</serial>
<console type='pty'>
<target type='serial' port='0'/>
</console>
<channel type='unix'>
<target type='virtio' name='org.qemu.guest_agent.0'/>
<address type='virtio-serial' controller='0' bus='0' port='1'/>
</channel>
<input type='tablet' bus='usb'>
<address type='usb' bus='0' port='1'/>
</input>
<input type='mouse' bus='ps2'/>
<input type='keyboard' bus='ps2'/>
<sound model='ich9'>
<address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/>
</sound>
<hostdev mode='subsystem' type='pci' managed='yes'>
<driver name='vfio'/>
<source>
<address domain='0x0000' bus='0x09' slot='0x00' function='0x0'/>
</source>
<rom file='/mnt/user/isos/vbios/Sapphire HD7950 Tahiti.rom'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
</hostdev>
<hostdev mode='subsystem' type='pci' managed='yes'>
<driver name='vfio'/>
<source>
<address domain='0x0000' bus='0x09' slot='0x00' function='0x1'/>
</source>
<address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/>
</hostdev>
<memballoon model='none'/>
</devices>
</domain>System devices ( Sorry for the bad readability)
-
Am running into the same problem but google and the search function helped me out. ( I am also a total unraid noob)
Plug your usb boot device into a pc go into the config folder and delete the vfio config file.-
1
-
Unassigned Devices Preclear - a utility to preclear disks before adding them to the array
in Plugin Support
Posted · Edited by Creativity404
Added logs
Goodday everyone,
I'm adding 2, 12 TB drives to my system. 1 precleared succesfully the other one did not.
In the log it says:
Y5JB79JC_19045: Post-Read: cmp command failed - disk not zeroed
Y5JB79JC_19045: Post-Read: dd command failed, exit code [141]
Would anybody have some advice for me? It would be greatly appreciated.
Is the drive faulty? should i run another preclear?
APOLLO-unassigned.devices.preclear-20220607-0200.zip