Search content
Sort by
Showing 5 of 5 results by jmacodex
Re: [Mining OS] SimpleMining.net - Easy to use GPU MINING Operating System
http://
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.
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.
Re: [Mining OS] SimpleMining.net - Easy to use GPU MINING Operating System
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?
Re: [Mining OS] SimpleMining.net - Easy to use GPU MINING Operating System
Tytanic,
One of the cards on my 8 card rig is running hotter than others, but how do I find it? SMOS doesn`t tell me what PCI slot that card is plugged in.
One of the cards on my 8 card rig is running hotter than others, but how do I find it? SMOS doesn`t tell me what PCI slot that card is plugged in.
you can turn cards off/on by pressing the corresponding number key on your keyboard if you attach a keyboard to the miner or log in through ssh. This works for cards 0-9, and then use the arrow keys to turn off/on cards 10-12.
using this you can disable all cards as soon as the miner loads, and then one by one turn them on and feel them with your hand for warmth. note which is which and keep it for later.
You mean while it is mining (the DOS like invironment) you will just push 0-9 to toggle/switch on/off a particular GPU? Could you post a Screenshot how it looked like.
Re: [Mining OS] SimpleMining.net - Easy to use GPU MINING Operating System
Hello all, do SMOS have logs where you can see which GPU_# caused an error? if none,
tytanick,
could you add that feature, maybe you can show it in the Notes section of the RigList, atleast the 5 last Error that caused reloading/restarting of the miner/os.
surely this will help find the OC values easier, this is due to I have a mixed Hynix, Micron and Samsung GTX1060 memory.
I also noticed, you have some update, what's new? its not yet in the change log.
My current OS version show NV1151, while change log only shows V1150
Thank you.
tytanick,
could you add that feature, maybe you can show it in the Notes section of the RigList, atleast the 5 last Error that caused reloading/restarting of the miner/os.
surely this will help find the OC values easier, this is due to I have a mixed Hynix, Micron and Samsung GTX1060 memory.
I also noticed, you have some update, what's new? its not yet in the change log.
My current OS version show NV1151, while change log only shows V1150
Thank you.