Author

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

newbie
Activity: 19
Merit: 0
Inverted, I have same problem!!!

Sick of those random restarts. I used to have them around specific time every day, now now they are random. Sometimes rig restarts and keeps mining, but sometimes goes offline and doesn`t restart - I`m loosing coins because of this shit!!!

Hi,

Which card are you using?

Which coin are you mining?

Which miner are you using?

newbie
Activity: 210
Merit: 0
Inverted, I have same problem!!!

Sick of those random restarts. I used to have them around specific time every day, now now they are random. Sometimes rig restarts and keeps mining, but sometimes goes offline and doesn`t restart - I`m loosing coins because of this shit!!!
newbie
Activity: 19
Merit: 0
Hello, I am looking to find out the reason why my rigs are restarting again and again after some duration of time? (Duration is random)

There is no power cut.
No Voltage Fluctuations.

1. Why do you think it's restarting again and again? (8-9 times in last 24 hours)

2. How can I start the logging of logs in SMOS?

Thanks.
newbie
Activity: 10
Merit: 0
I love this software, although I only have 1 rig with a 280x and a 290x lol but I love it nonetheless Smiley I have no complaints as such but I wish the dashboard was as attractive and informative as hiveos. Just wanted to say thankyou for the software it’s rock solid Smiley
newbie
Activity: 20
Merit: 0
I have same problem but I can't solve this problem...
I have motherboard H110 Pro BTC+ and I flash with last BIOS update.
I already did installation recomendations that are in SimpleMining Site.
I attach error that I have when I boot SimpleMining OS.
I already reflash my pen drive and have same problem...
Anyone can help to explain  to me what I have to do?
https://mega.nz/#F!FEJ3xRQQ!sxivx5tR-Biip2f8wSH9MQ


I did notice these after usb drive corruption even thought I flashed and tried with another as well as new USB drives, same motherboard. But it goes through and starts mining. If anyone has any idea if that is normal or how should it be fixed, please share.
newbie
Activity: 35
Merit: 0
Hi,

Can you Add OptiminerZero as i would like to mine Zero coin.

I was trying to mine GOBYTE coin using ccminer-tpruvot-v2.1 and ccminer-tpruvot-v2.2.5-cuda8.0 but it says not-supported.

Some one help me to mine GoByte and Zero coin


That is what I linked above optiminer 2.1.2 Tytanick said he is looking into it as above as well.

Hi,

I thought it is a different script that is why i requested seperately.

If we can able to mine it is good.

Once if Admin added the miner can you share the script to mine GoByte and Zero coin

Regards,
Muthu
newbie
Activity: 31
Merit: 0
Hi,

Can you Add OptiminerZero as i would like to mine Zero coin.

I was trying to mine GOBYTE coin using ccminer-tpruvot-v2.1 and ccminer-tpruvot-v2.2.5-cuda8.0 but it says not-supported.

Some one help me to mine GoByte and Zero coin


That is what I linked above optiminer 2.1.2 Tytanick said he is looking into it as above as well.
newbie
Activity: 35
Merit: 0
Hi,

Can you Add OptiminerZero as i would like to mine Zero coin.

I was trying to mine GOBYTE coin using ccminer-tpruvot-v2.1 and ccminer-tpruvot-v2.2.5-cuda8.0 but it says not-supported.

Some one help me to mine GoByte and Zero coin
newbie
Activity: 1
Merit: 0
I have same problem but I can't solve this problem...
I have motherboard H110 Pro BTC+ and I flash with last BIOS update.
I already did installation recomendations that are in SimpleMining Site.
I attach error that I have when I boot SimpleMining OS.
I already reflash my pen drive and have same problem...
Anyone can help to explain  to me what I have to do?
https://mega.nz/#F!FEJ3xRQQ!sxivx5tR-Biip2f8wSH9MQ
legendary
Activity: 2660
Merit: 1096
Simplemining.net Admin
So after about 2 straight weeks of mining perfectly, the SMOS just went down with no error code, overheating, or anything I could see.

I tried the internet connection, a new USB, and unplugging/restarting the rig.

Lastly, I deleted the current rig that was not connecting and now when I plug in SMOS can't find any rig in my dashboard.

The monitor code says that it wants me to connect to the rig that I can't see.

What am I missing?
Please connect LCD to your rig and see what happens there, make a video and if it will be unclear please send it to our support at [email protected]

MR TYTANICK
Can you please add optiminer 2.1.2 i would very much appreciate  https://github.com/Optiminer/OptiminerEquihash
I am looking into this.

Hi. Can you add Raven AMD Miner ?
https://github.com/aceneun/sgminer-gm-x16r
Also looking into this miner but first approach failed on compilation under linux. We will be trying.


Also we need to make few adjustments in Telegram BOT notification system and i think that it will be soon live Smiley
newbie
Activity: 29
Merit: 2
So after about 2 straight weeks of mining perfectly, the SMOS just went down with no error code, overheating, or anything I could see.

I tried the internet connection, a new USB, and unplugging/restarting the rig.

Lastly, I deleted the current rig that was not connecting and now when I plug in SMOS can't find any rig in my dashboard.

The monitor code says that it wants me to connect to the rig that I can't see.

What am I missing?
newbie
Activity: 31
Merit: 0
MR TYTANICK

Can you please add optiminer 2.1.2 i would very much appreciate  https://github.com/Optiminer/OptiminerEquihash
member
Activity: 448
Merit: 88
newbie
Activity: 42
Merit: 0
Update v1150
- fix for ethminer blocking stats in dashboard
- fix in Nvidia OC script on p104 p106

Thank You very much, sure nobody can imagine the load you have with such amount of users, all demanding new miners, improvements etc.

But from the other hand, we have to give some sort of feedback.

I have p104 with modded bios. On win i can hit 40Mhs eth @ 100watt per card from the wall with underwolt and memory boost.
On smos no matter what i do i can't go over 35.xx Mhs @ 110 watt...
newbie
Activity: 210
Merit: 0
Tytanick,

Can you please update Nvidia driver to latest 390.42:
http://www.nvidia.com/download/driverResults.aspx/131853/en-us

Your current one is 390.25
full member
Activity: 626
Merit: 159
Been using SMOS for a few weeks now. Not bad at all and overall and I am making about 2-3 more a day on each of my 8 x rigs... The only drawback for me is that I really miss having CPU mining capabilities built in to a single system.

I need to touch up on my Ubuntu...
newbie
Activity: 5
Merit: 0
http://
the log on the dashboard containing like 5 last reboot reasons would be great. As logging locally just corrupts usb flash memory within a week or two, already gone through that couple of times...


after claymore 11.0 , my rig are restarting every few hours, i am unable to understand the problem so till now i am using claymore 11.0, plz do some for your customers...



SSH into your rig. When it reboots the SSH session will end, but whatever happened to cause the crash will still be displayed. Very easy/fast way to troubleshoot. likely you have a card overclocked too high for the new Claymore improvements in 11.3+

"SSH session will end, but whatever happened to cause the crash will still be displayed" this means monitoring the rig like 24/7 with a display, this defeats the purpose of SMOS, the point of the log is to check what happened after several hours/days in operation because after a day or two my rig has restarted already a couple of hours ago.

would like also to ask (not so technical person), is the SSH in PuTTY any different from direct SSH?



If you want to dig through the log you can also do that. The log is there, just SSH into the miner and pull it up. The way I suggested is much more efficient use of your time. You don't need 24/7 monitoring. Just run it on your personal computer, and when the miner reboots you'll see the cause in PuTTY whenever you're back at your personal computer. Do this for a couple days until you eliminate the cause of your reboots.

As you said, the miner reboots a couple times and hours before you get to look into it. Digging through logs will take hours of your time to scroll back to try and find the crashes. My suggestion will put the cause of the crash immediately in front of you with minimal effort.

To answer your question, PuTTY works well as an SSH client on Windows. If you hover over your rig's name in SMOS you'll see the ip address of the rig. log into that address with PuTTY. username: "miner", password "miner". once you log into it type "screen -x miner" and you'll pull up the miner screen. let it run until the miner reboots/crashes. when it crashes you'll get a pop-up in PuTTY that the connection disconnected, but you'll be able to see what caused the drop.



i've been using putty "screen -x miner" since I use SMOS, it is also in the help section.

like just now, one of my rig stopped, and screen can only show the hash rate has dropped to 8Mhs across all 6GPUs..
"Digging through logs will take hours of your time" SMOS is designed for a farm setup, so it will be impractical to dig all of your rig.
having a log that show only what caused the crash will help, we are not asking for the whole log, we are only interested what caused the crash.








newbie
Activity: 30
Merit: 0
undervolting on rx series still not working...
newbie
Activity: 55
Merit: 0
the log on the dashboard containing like 5 last reboot reasons would be great. As logging locally just corrupts usb flash memory within a week or two, already gone through that couple of times...


after claymore 11.0 , my rig are restarting every few hours, i am unable to understand the problem so till now i am using claymore 11.0, plz do some for your customers...



SSH into your rig. When it reboots the SSH session will end, but whatever happened to cause the crash will still be displayed. Very easy/fast way to troubleshoot. likely you have a card overclocked too high for the new Claymore improvements in 11.3+

"SSH session will end, but whatever happened to cause the crash will still be displayed" this means monitoring the rig like 24/7 with a display, this defeats the purpose of SMOS, the point of the log is to check what happened after several hours/days in operation because after a day or two my rig has restarted already a couple of hours ago.

would like also to ask (not so technical person), is the SSH in PuTTY any different from direct SSH?



If you want to dig through the log you can also do that. The log is there, just SSH into the miner and pull it up. The way I suggested is much more efficient use of your time. You don't need 24/7 monitoring. Just run it on your personal computer, and when the miner reboots you'll see the cause in PuTTY whenever you're back at your personal computer. Do this for a couple days until you eliminate the cause of your reboots.

As you said, the miner reboots a couple times and hours before you get to look into it. Digging through logs will take hours of your time to scroll back to try and find the crashes. My suggestion will put the cause of the crash immediately in front of you with minimal effort.

To answer your question, PuTTY works well as an SSH client on Windows. If you hover over your rig's name in SMOS you'll see the ip address of the rig. log into that address with PuTTY. username: "miner", password "miner". once you log into it type "screen -x miner" and you'll pull up the miner screen. let it run until the miner reboots/crashes. when it crashes you'll get a pop-up in PuTTY that the connection disconnected, but you'll be able to see what caused the drop.
newbie
Activity: 5
Merit: 0
the log on the dashboard containing like 5 last reboot reasons would be great. As logging locally just corrupts usb flash memory within a week or two, already gone through that couple of times...


after claymore 11.0 , my rig are restarting every few hours, i am unable to understand the problem so till now i am using claymore 11.0, plz do some for your customers...



SSH into your rig. When it reboots the SSH session will end, but whatever happened to cause the crash will still be displayed. Very easy/fast way to troubleshoot. likely you have a card overclocked too high for the new Claymore improvements in 11.3+

"SSH session will end, but whatever happened to cause the crash will still be displayed" this means monitoring the rig like 24/7 with a display, this defeats the purpose of SMOS, the point of the log is to check what happened after several hours/days in operation because after a day or two my rig has restarted already a couple of hours ago.

would like also to ask (not so technical person), is the SSH in PuTTY any different from direct SSH?

Jump to: