I am having issues with my Ethereum mining rig.

[Atilgan79]

Hello,

This is my first post to the forum.
I am also new to mining and crypto currencies. I read and study as much as I can. I have been in IT over 25 years (I am not a newbie into IT) but very new into CryptoCurrencies.

Ok enough back ground information,

I am building a rig to mine Ethereum.

Details of the rig:
- Motherboard: ASRock H81 Pro BTC R2.0 Intel LGA1150 DDR3 1x PCIe 2.0 x16 2x SATA3 2x USB3.0 HDMI/D-SUB Motherboard
- GPUs: 6x MSI Radeon RX 470 8G OC
- RAM: Kingston HyperX Fury 4GB 1600MHz DDR3 CL10 DIMM (HX316C10F/4), Blue
- CPU: Intel Celeron Processor G1840, 2M Cache, 2.8 GHz, BX80646G1840
- SSD: SanDisk SanDisk SSD Plus Solid State Drive Components Other SDSSDA-120G-G26
- PSUs: 2x EVGA 850 GQ, 80+ GOLD 850W, Semi Modular, EVGA ECO Mode, 5 Year Warranty, Power Supply 210-GQ-0850-V1 (In the rig, I had 1x EVGA 1000 GQ, 80+ GOLD 1000W, Semi Modular, EVGA ECO Mode, 5 Year Warranty, Power Supply 210-GQ-1000-V1. I was hitting already 955W, I decided to use 2 smaller W PSUs)
- Risers: 6-Pack PCI-E 16x to 1x Powered Riser Adapter Card w/ 50cm USB 3.0 Extension Cable & MOLEX to SATA Power Cable - GPU Riser Extender Cable - Ethereum Mining ETH
- OS: Ubuntu 16.04
- Claymore: 9.5
- AMD drivers: AMDGPU-Pro
- Frame: Custom built aluminum frame


The rig (all parts were on my study table.), everything was working fine, I build an aluminum frame to place the rig into.
While the rig was on my study table,  I had issue with the 6th GPU, sometimes the OS did not recognize the 6th GPU. After changing too many ricers, I managed to get ubuntu recognize the 6th GPU. I see it (sudo lshw -businfo | grep -i display).

When I run claymore I will get the purple screen at logon. (GNU GRUP version 2.02) I have done the modification from 'quiet splash' to 'nomodeset' and 'no splash' )

- 'nomodeset' --> After booting into linux and running claymore:

▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒ͻ
▒      Claymore's Dual ETH + DCR/SC/LBC/PASC GPU Miner v9.5      ▒
▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒ͼ

This pool (eth-eu2.nanopool.org) does not support Ethereum addresses as login (or requires worker name in "Login.Worker" format) and cannot be used for devfee mining, therefore it is not supported.
However, you can mine on this pool if you specify "-allpools 1" option, default pools (different from this pool) will be used for devfee.
Please read "Readme" file for details.This pool (eth-eu2.nanopool.org) does not support Ethereum addresses as login (or requires worker name in "Login.Worker" format) and cannot be used for devfee mining, therefore it is not supported.
However, you can mine on this pool if you specify "-allpools 1" option, default pools (different from this pool) will be used for devfee.
Please read "Readme" file for details.Pool eth-eu2.nanopool.org removed from the list
This pool (eth-us-east1.nanopool.org) does not support Ethereum addresses as login (or requires worker name in "Login.Worker" format) and cannot be used for devfee mining, therefore it is not supported.
However, you can mine on this pool if you specify "-allpools 1" option, default pools (different from this pool) will be used for devfee.
Please read "Readme" file for details.This pool (eth-us-east1.nanopool.org) does not support Ethereum addresses as login (or requires worker name in "Login.Worker" format) and cannot be used for devfee mining, therefore it is not supported.
However, you can mine on this pool if you specify "-allpools 1" option, default pools (different from this pool) will be used for devfee.
Please read "Readme" file for details.Pool eth-us-east1.nanopool.org removed from the list
This pool (eth-us-west1.nanopool.org) does not support Ethereum addresses as login (or requires worker name in "Login.Worker" format) and cannot be used for devfee mining, therefore it is not supported.
However, you can mine on this pool if you specify "-allpools 1" option, default pools (different from this pool) will be used for devfee.
Please read "Readme" file for details.This pool (eth-us-west1.nanopool.org) does not support Ethereum addresses as login (or requires worker name in "Login.Worker" format) and cannot be used for devfee mining, therefore it is not supported.
However, you can mine on this pool if you specify "-allpools 1" option, default pools (different from this pool) will be used for devfee.
Please read "Readme" file for details.Pool eth-us-west1.nanopool.org removed from the list
This pool (eth-asia1.nanopool.org) does not support Ethereum addresses as login (or requires worker name in "Login.Worker" format) and cannot be used for devfee mining, therefore it is not supported.
However, you can mine on this pool if you specify "-allpools 1" option, default pools (different from this pool) will be used for devfee.
Please read "Readme" file for details.This pool (eth-asia1.nanopool.org) does not support Ethereum addresses as login (or requires worker name in "Login.Worker" format) and cannot be used for devfee mining, therefore it is not supported.
However, you can mine on this pool if you specify "-allpools 1" option, default pools (different from this pool) will be used for devfee.
Please read "Readme" file for details.Pool eth-asia1.nanopool.org removed from the list
ETH: 1 pool is specified
Main Ethereum pool is us1.ethermine.org:4444
PuTTY X11 proxy: unable to connect to forwarded X server: Network error: Connection refused
No AMD cards in the list.
No NVIDIA CUDA GPUs detected.
No AMD OPENCL or NVIDIA CUDA GPUs found, exit

- 'no splash' --> Booting does not complete.

After the following line, the boot up is stuck there, nothing else happens:
'27.730113] Rebooting in 30 seconds'



In advance, I really appreciate all the help that could be provided.

Sincerely,

Ati

[1713973369]

1713973369

[1713973369]

1713973369

[1713973369]

1713973369

[1713973369]

1713973369

[Atilgan79]

I have this issue when I plug the 6th GPU into the PCIE1 on the mobo. I tried too many risers connected to this mobo. I tried another GPU on PCIE socket (that worked), so I rule out the mobo issue. The GPU that was having issue, I plugged it into PCIEx socket, it did not work, many risers were tried.

I received the GPUs about a week ago. It was working fine. Now it is not working, I contacted the seller. This might be a deffective GPU.

While waiting for a response from the seller, please give me some more ideas, something else that I could test.

The 6th GPU was working while the rig was sitting on my desk. (Initially it was not working, when I changed too many risers it started working).

With some risers the 6th GPU is nor recognized. I do not see it with 'sudo lshw -businfo | grep -i display'.

Now I have a riser that does show the 6th GPU. But the claymore will stop with the log provided above (in the first post)

Ati

[mirny]

Read that log again. What is it saying?
"Please read "Readme" file for details."
Did you read readme already?
I think you don't.
Just read it, and you will see, you will solve your problem by yourself.
Believe me.

[Atilgan79]

Hello,

The log located at: /var/log/boot.log

I read it and it did not tell me anything.

sesentech@sesentech-desktop:~/Downloads/amdgpu-pro-fans$ cat  /var/log/boot.log
[  OK  ] Started Show Plymouth Boot Screen.
[  OK  ] Started Forward Password Requests to Plymouth Directory Watch.
[  OK  ] Reached target Paths.
[  OK  ] Reached target Basic System.
         Starting Restore /etc/resolv.conf if the system crashed before the ppp link was shut down...
         Starting LSB: automatic crash report generation...
         Starting Modem Manager...
         Starting System Logging Service...
         Starting LSB: Speech Dispatcher...
         Starting LSB: daemon to balance interrupts for SMP systems...
[  OK  ] Started Run anacron jobs.
[  OK  ] Started Regular background program processing daemon.
[  OK  ] Started CUPS Scheduler.
[  OK  ] Reached target Printer.
         Starting Detect the available GPUs and deal with any system changes...
[  OK  ] Started Snappy daemon.
         Starting Auto import assertions from block devices...
         Starting LSB: Record successful boot for GRUB...
         Starting Avahi mDNS/DNS-SD Stack...
         Starting Thermal Daemon Service...
         Starting Login Service...
         Starting Accounts Service...
         Starting Permit User Sessions...
[  OK  ] Started ACPI event daemon.
         Starting LSB: Set the CPU Frequency Scaling governor to "ondemand"...
[  OK  ] Started D-Bus System Message Bus.
[  OK  ] Started Avahi mDNS/DNS-SD Stack.
[  OK  ] Started Make remote CUPS printers available locally.
         Starting Network Manager...
         Starting Save/Restore Sound Card State...
[  OK  ] Started System Logging Service.
[  OK  ] Started Restore /etc/resolv.conf if the system crashed before the ppp link was shut down.
[  OK  ] Started Auto import assertions from block devices.
[  OK  ] Started Permit User Sessions.
[  OK  ] Started Save/Restore Sound Card State.
[  OK  ] Started Thermal Daemon Service.
[  OK  ] Started Network Manager.
[  OK  ] Started Login Service.
         Starting Network Manager Wait Online...
         Starting Authenticate and Authorize Users to Run Privileged Tasks...
         Starting Network Manager Script Dispatcher Service...
[  OK  ] Started Network Manager Script Dispatcher Service.
         Starting Hostname Service...
[  OK  ] Started Hostname Service.
[  OK  ] Started Authenticate and Authorize Users to Run Privileged Tasks.
[  OK  ] Started Modem Manager.
[  OK  ] Started Accounts Service.
[  OK  ] Started LSB: Speech Dispatcher.
[  OK  ] Started Detect the available GPUs and deal with any system changes.
         Starting Light Display Manager...
[  OK  ] Started LSB: automatic crash report generation.
[  OK  ] Started LSB: daemon to balance interrupts for SMP systems.
[  OK  ] Started LSB: Record successful boot for GRUB.
[  OK  ] Started LSB: Set the CPU Frequency Scaling governor to "ondemand".
[  OK  ] Started Raise network interfaces.
[  OK  ] Reached target Network.
[  OK  ] Started Unattended Upgrades Shutdown.
         Starting OpenBSD Secure Shell server...
[  OK  ] Started OpenBSD Secure Shell server.

Ahhh,

I was looking at the boot.log.

I see, the claymore logs.

/usr/local/claymore95/

Thanks I will keep you posted.


Best Regards

Ati

[Atilgan79]

Sorry for the stupid question.

The readme fiel is named as 'Readme!!!.txt'

When I try to open it I get the following:

sesentech@sesentech-desktop:/usr/local/claymore95$ cat Readme!!!.txt
-bash: !.txt: event not found
sesentech@sesentech-desktop:/usr/local/claymore95$

When I try to rename the file Readme!!!.txt

sesentech@sesentech-desktop:/usr/local/claymore95$ mv  Readme!!!.txt  Readme.txt
-bash: !.txt: event not found
sesentech@sesentech-desktop:/usr/local/claymore95$

I get the same.

Sincerely,

Ati

[Atilgan79]

I tried, cat, vim, nano. All give me the same.

[Atilgan79]

K, I figured it out

cat Readme\!\!\!.txt

Will give the results.

Let me read the txt.

[Atilgan79]

@mirny

I really appreciate it.

I read it before but I guess I did not pay attention to it much.

I really appreciate your assistance.

'For AMD cards, Catalyst (Crimson) 15.12 is required for best performance and compatibility. You can get very bad results for different drivers version, or miner can fail on start
up.
For AMD 4xx/5xx cards (Polaris) you can use any recent drivers.
For AMD cards, set the following environment variables, especially if you have 2GB cards:

GPU_FORCE_64BIT_PTR 0
GPU_MAX_HEAP_SIZE 100
GPU_USE_SYNC_OBJECTS 1
GPU_MAX_ALLOC_PERCENT 100
GPU_SINGLE_ALLOC_PERCENT 100'

-------------------------------------

As for my card I need to get 'POLARIS 10'

Let me try now.

Best Regards

Ati

[Atilgan79]

I still cannot get it to run. Now 1 more card cases me problems.

I can mine only on 4 cards now (2 of them are causing claymore to crash.)

I reinstalled amdgpu-pro drivers so many times.

Right now 1 of the GPU is unplugged.

I can see all 5 cards + onboard

sesentech@sesentech-desktop:/usr/local/claymore10$ sudo lshw -businfo | grep -i display
pci@0000:01:00.0             display        Ellesmere [Radeon RX 470/480/570/580]
pci@0000:00:02.0             display        Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller
pci@0000:02:00.0             display        Ellesmere [Radeon RX 470/480/570/580]
pci@0000:03:00.0             display        Ellesmere [Radeon RX 470/480/570/580]
pci@0000:04:00.0             display        Ellesmere [Radeon RX 470/480/570/580]
pci@0000:05:00.0             display        Ellesmere [Radeon RX 470/480/570/580]

2 of the GPUs are not working.

Please help.

Ati

[vectisitch]

it is just easier to limit your rigs to 4 cards. easier for fault finding and far less unstable. i never run more than 4 cards per rig