Author

Topic: [Mining OS] SimpleMining.net - Manage Your GPU farm the easy way! (30 days free) - page 152. (Read 835515 times)

newbie
Activity: 28
Merit: 0
i was wondering what happened with my 2 Rigs the last 2 days - barely booting after 5 restart suddenly, Turned out there was a release !!

for some reason latest release start showing :

[ 88.973154] amdgpu 0000:01:00.0: VM fault (0x02, vmid 1) at page 1867826, read from 'TC4' (0x54433400) (72)
[ 88.973618] amdgpu 0000:01:00.0: GPU fault detected: 147 0x00088802
[ 88.974071] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x001EF614
[ 88.974520] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x02048002
[ 88.974958] amdgpu 0000:01:00.0: VM fault (0x02, vmid 1) at page 2029076, read from 'TC4' (0x54433400) (72)
[ 88.975408] amdgpu 0000:01:00.0: GPU fault detected: 147 0x0e004802
[ 88.975856] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x001EB48E
[ 88.976316] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x02088002
[ 88.976774] amdgpu 0000:01:00.0: VM fault (0x02, vmid 1) at page 2012302, read from 'TC6' (0x54433600) (136)
[ 88.977253] amdgpu 0000:01:00.0: GPU fault detected: 147 0x04984802
[ 88.977728] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x001C293B
[ 88.978207] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x02088002
[ 88.978679] amdgpu 0000:01:00.0: VM fault (0x02, vmid 1) at page 1845563, read from 'TC6' (0x54433600) (136)
[ 88.979507] amdgpu 0000:01:00.0: IH ring buffer overflow (0x000878E0, 0x00008370, 0x000078F0)



---

Then Reboot but doesnt Boot ! 2 Rigs at the same day start doing it on 14/ May  - its been working fine since 8 months no change to overlocking or miner versions



this happens usually if a riser is faulty or if your OC is to strong.
sr. member
Activity: 756
Merit: 250
Please add Optiminer ZERO 1.2.0 thanks!!!
newbie
Activity: 72
Merit: 0
i was wondering what happened with my 2 Rigs the last 2 days - barely booting after 5 restart suddenly, Turned out there was a release !!

for some reason latest release start showing :

[ 88.973154] amdgpu 0000:01:00.0: VM fault (0x02, vmid 1) at page 1867826, read from 'TC4' (0x54433400) (72)
[ 88.973618] amdgpu 0000:01:00.0: GPU fault detected: 147 0x00088802
[ 88.974071] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x001EF614
[ 88.974520] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x02048002
[ 88.974958] amdgpu 0000:01:00.0: VM fault (0x02, vmid 1) at page 2029076, read from 'TC4' (0x54433400) (72)
[ 88.975408] amdgpu 0000:01:00.0: GPU fault detected: 147 0x0e004802
[ 88.975856] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x001EB48E
[ 88.976316] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x02088002
[ 88.976774] amdgpu 0000:01:00.0: VM fault (0x02, vmid 1) at page 2012302, read from 'TC6' (0x54433600) (136)
[ 88.977253] amdgpu 0000:01:00.0: GPU fault detected: 147 0x04984802
[ 88.977728] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x001C293B
[ 88.978207] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x02088002
[ 88.978679] amdgpu 0000:01:00.0: VM fault (0x02, vmid 1) at page 1845563, read from 'TC6' (0x54433600) (136)
[ 88.979507] amdgpu 0000:01:00.0: IH ring buffer overflow (0x000878E0, 0x00008370, 0x000078F0)



---

Then Reboot but doesnt Boot ! 2 Rigs at the same day start doing it on 14/ May  - its been working fine since 8 months no change to overlocking or miner versions
newbie
Activity: 1
Merit: 0
Hi team can you  add  optiminer 1.2 for mining ZeroCoin Equihash 192_7
newbie
Activity: 1
Merit: 0
out of nowhere i am getting the
Remove dead screens with 'screen -wipe' error

somewhere in this book of 457 pages is the solution i think
but before i find i am old and in a weelchair
so i hope someone can help me with a answer for this problem.

rig was running fine for a couple of months

a similar problem, appeared a couple of days ago, at 5 rigs. Until now, they worked without errors. on the dashboard it is shown that the rig is digging, but in fact there is froze.
For me the same problem appeared 3 days ago. One of the rigs worked 11 of his last 24 hours mining eth with claymore-eth-v11.7 (or attemps to). The last night i switched to claymore-xmr-v11.3 and there is no problem for 14 hours.
full member
Activity: 198
Merit: 100
MSI Z270-A PRO with 7 GPU used to run  fine for almost a year. Suddenly yesterday I had ~50 restarts so I tried to figure out what is going on.

Didn't find any suspicious change notes so I started to review my hardware.

First: It is mining well for about 4-10 minutes then it shows error "gpu fault detected 147" after this error all GPUs still mining for about 10 seconds then instantly reboots with command: "sysrq resetting" which isn't any watchdog of Claymore.

What I tried already: reduced OC, increased voltage, different PSU, brand new risers, checked all cables if they are burned or heating up fast (all were fine, healthy and cold) and it's no change.

Guys what has happened, have you any suggestions? My script which worked fine for some time looks like this:
Code:
-wd 1 -r 1 -epool eu1.ethermine.org:4444 -ewal wallet.$rigName -esm 0 -epsw x -allpools 1 -dcri 14

Strange I had the exact same issue from tuesday. A rig that was working perfectly from months, suddenly reboot every few minutes with these kind of errors. I have removed one of the cards, and now it's more stable. So may be it's indeed a riser issue. No time to check further for now.
ext
newbie
Activity: 3
Merit: 0
out of nowhere i am getting the
Remove dead screens with 'screen -wipe' error

somewhere in this book of 457 pages is the solution i think
but before i find i am old and in a weelchair
so i hope someone can help me with a answer for this problem.

rig was running fine for a couple of months

a similar problem, appeared a couple of days ago, at 5 rigs. Until now, they worked without errors. on the dashboard it is shown that the rig is digging, but in fact there is froze.
newbie
Activity: 4
Merit: 0
Hi guys, anyone here knows how to successfully program OhGodETHlargement on startup.

Tried editing rc.local, but once miner updates, file gets erased.

Thank you
legendary
Activity: 1834
Merit: 1080
---- winter*juvia -----
MSI Z270-A PRO with 7 GPU used to run  fine for almost a year. Suddenly yesterday I had ~50 restarts so I tried to figure out what is going on.

Didn't find any suspicious change notes so I started to review my hardware.

First: It is mining well for about 4-10 minutes then it shows error "gpu fault detected 147" after this error all GPUs still mining for about 10 seconds then instantly reboots with command: "sysrq resetting" which isn't any watchdog of Claymore.

What I tried already: reduced OC, increased voltage, different PSU, brand new risers, checked all cables if they are burned or heating up fast (all were fine, healthy and cold) and it's no change.

Guys what has happened, have you any suggestions? My script which worked fine for some time looks like this:
Code:
-wd 1 -r 1 -epool eu1.ethermine.org:4444 -ewal wallet.$rigName -esm 0 -epsw x -allpools 1 -dcri 14

I can almost guarantee you that you have a faulty pci riser.

Motherboards have higher quality and solid warranty.

PCI risers, have limited warranty and may have been manufactured in the back alleys in Guangdong.
newbie
Activity: 25
Merit: 0
out of nowhere i am getting the
Remove dead screens with 'screen -wipe' error

somewhere in this book of 457 pages is the solution i think
but before i find i am old and in a weelchair
so i hope someone can help me with a answer for this problem.

rig was running fine for a couple of months
member
Activity: 103
Merit: 10
Yeah, the alot of settings are tied together on the MSI board.  If the 4G is enabled, UEFI is automatically enabled as well and it won't let you independently switch the UEFI to Legacy Mode.  If 4G is disabled, legacy mode is available, but then there is a 4 GPU limit.
glad to see I'm not the only one who has ran into this issue lol!
Jumping on the bandwagon here as well.  I have one rig still running ethos because of this issue.  Would love to see a solution that doesn't require me to get a different motherboard (ethos is working, so that won't happen - just prefer SMOS if I have a choice)
Then burn the image on an ancient little 2.5" mechanical SATA disk to get around the problem?
Unfortunate as it might be that solution doesn't work either, I have tried HDD's SSD's usb's no matter what type of boot device it is it just doesn't work Sad
newbie
Activity: 14
Merit: 0
MSI Z270-A PRO with 7 GPU used to run  fine for almost a year. Suddenly yesterday I had ~50 restarts so I tried to figure out what is going on.

Didn't find any suspicious change notes so I started to review my hardware.

First: It is mining well for about 4-10 minutes then it shows error "gpu fault detected 147" after this error all GPUs still mining for about 10 seconds then instantly reboots with command: "sysrq resetting" which isn't any watchdog of Claymore.

What I tried already: reduced OC, increased voltage, different PSU, brand new risers, checked all cables if they are burned or heating up fast (all were fine, healthy and cold) and it's no change.

Guys what has happened, have you any suggestions? My script which worked fine for some time looks like this:
Code:
-wd 1 -r 1 -epool eu1.ethermine.org:4444 -ewal wallet.$rigName -esm 0 -epsw x -allpools 1 -dcri 14
newbie
Activity: 18
Merit: 0
Hello All, and thank you Tyanick for making such an easy to use plateform !!!

As Banman24 said there is a real issue with SMOS and 4g decoding.

I have 2 motherboards MSI Z270 A PRO and GIGABYTE H110-D3A  and when I enable 4G encoding the system don't boot. I bought the second motherboard (Gigabyte one)in order to get all 6 card running, I suspected my first motherboard to have an Issue but...same result.
 
I find SMOS to be a very good mining solution and for now I am building two rigs with 4 cards each (to bypass this problem) but as Banman24 said the best solution would be that Tyanick make SMOS UEFI

I have no clue if it is complicated but I am sure now that I am not the only one facing this pretty annoying problem and...if there was an easy solution we would all be very glad.


PS: I didn't knew about legacy option on the Gigabyte so maybe I could have my six cards running if I find the legacy option

PS to Tyanick: I didn't find any information on the SMOS website regarding the legacy option which must be set on most motherboard in order to start with more than 4 cards. This information was quite hard to find and I think it should be on the frontpage ....
 
jr. member
Activity: 94
Merit: 1
Yeah, the alot of settings are tied together on the MSI board.  If the 4G is enabled, UEFI is automatically enabled as well and it won't let you independently switch the UEFI to Legacy Mode.  If 4G is disabled, legacy mode is available, but then there is a 4 GPU limit.
glad to see I'm not the only one who has ran into this issue lol!
Jumping on the bandwagon here as well.  I have one rig still running ethos because of this issue.  Would love to see a solution that doesn't require me to get a different motherboard (ethos is working, so that won't happen - just prefer SMOS if I have a choice)
Then burn the image on an ancient little 2.5" mechanical SATA disk to get around the problem?
newbie
Activity: 83
Merit: 0
Hello. I can not find a Nexus miner in simplemining platform!
Do you have a miner for Nexus in simplemining.net for 1080ti ?
newbie
Activity: 1
Merit: 0

good day, use simpleminig and buy a router mpl3220 tplink that makes the change from WAN to USB (3g / 4g) to support the internet connection, but the flaw I have is that when I use the simplemining usb connection does not detect that connection, Do you have any idea why this happens? or what I should do to detect it.
newbie
Activity: 197
Merit: 0
hello
i need to install "openvpn" on SMOS
can anybody help me
member
Activity: 93
Merit: 10
Yeah, the alot of settings are tied together on the MSI board.  If the 4G is enabled, UEFI is automatically enabled as well and it won't let you independently switch the UEFI to Legacy Mode.  If 4G is disabled, legacy mode is available, but then there is a 4 GPU limit.
glad to see I'm not the only one who has ran into this issue lol!
Jumping on the bandwagon here as well.  I have one rig still running ethos because of this issue.  Would love to see a solution that doesn't require me to get a different motherboard (ethos is working, so that won't happen - just prefer SMOS if I have a choice)
newbie
Activity: 8
Merit: 0
What's up guys
Does the notification off when ur rig is down for 10 min or so still work with telegram...? If so where do i go to configure it thanx
Jump to: