 Show Posts
|
|
Pages: [1] 2 3 4 »
|
Did you try the reset button? I have never tried it but someone gave suggestions on how to use in the main S9 thread recently. It was something like, disconnect all the hashboards from power and from the control board, boot it up, hold the reset button for more than 10 seconds, let it reboot and wait 20 minutes. Go look for the exact directions though because I may be getting it wrong.
Close. (and it was me) Power down, remove power leads from hash boards. Leave power leads connected to controller. Turn on power, Wait a few seconds, then press the reset button and hold in for ~ 10 sec. Release button and leave it alone. The red led by the lan port should flash a few time to tell ya it's resetting. At this point, the older s9's needed maybe 5min at most. You should be able to log into the GUI and at least change your pool info. With the B16 on up or when using an older s9 with this new auto-tune software -- not sure. With no hash boards to fiddle with and speed test I have no idea what the firmware will make of it. Hopefully like with the older miners and firmware it will just shrug its shoulders and finish setting up the other parts of the miner... Probably would be a good idea to see what the Kernel Log reports while it tries to find boards  Anywho, if you can get to the GUI and set pools you should be good to power down, reconnect power to hash boards, maybe slaughter a chicken or lamb, then power up and see if the gods have been appeased... LOL Awesome thanks for the help - trying that right now - will let u know how i go  |
|
|
|
Hi there, I have 6 miners all S9's yes piece of shit that they are, had to shut them down this morning and when i restarted them, 2 refused to start. Absolutely nothing - cold dead bricks, tried swapping power supplies, connections, fans, boards, everything - am i missing something? How could they both brick? Are they bricked? Can anyone help??? Help please im stuck  Regards Loki |
|
|
|
|
Hi there, I have antminer s9's and wondering if someone can help me configure them for API access - step by step please?
I can remote SSH in to them not a problem, just have no idea what to do from there?
Thanks
R,.
|
|
|
|
I clean up the registry, but the monitor did not see S7 WTF?  ? one sees the other do not see how this can be? Yeh agreed that sounds weird? u don't have two Mantmonitors on ur c drive or anything like that? i know it sounds silly but have seen a few probs like that, the probs disappeared when we only had one on the drive etc. |
|
|
|
Ok so i had the same problem, i found nothing worked, until............. I deleted Mantmonitor - in regedit and then reinput all the core values, same again, it was only when i did this that everything works, so i deleted everything here as per below,  then I reinstalled and reinput the data etc, and voila, as per below everything now works  I use Open hardware monitor to monitor all the cpu functions as well  |
|
|
|
I'm using the latest and its fkin magic!   pegasus and galactica - 2 x SP35's erasmus, atlantia, defiant and orion = S3's Raider and Basestar = S2's I have the S3's reboot if their hash goes below 475 the SP35's auto reboot every 24hrs and the s2's just sit there Magic stuff !!! thanks Mdude! |
|
|
|
|
Hi there, have been running SP35's x 2 for a wee while now and running perfectly.
A few days ago, one decided to go offline and require a hard reboot, it did it again tonight.
In the logs i see this - Does anyone know what this means or what is happening?
Thanks
Oct 13 10:44:15 miner local1.warn minergate[553]: Bist took 10560 usec
Oct 13 10:44:31 miner local1.warn minergate[553]: HW WD 240s
Oct 13 10:44:35 miner local1.warn minergate[553]: Bist took 10476 usec
Oct 13 10:44:56 miner local1.warn minergate[553]: Bist took 70595 usec
Oct 13 10:45:01 miner cron.info crond[286]: crond: USER root pid 1353 cmd /usr/bin/php /etc/cron.d/RECORDHashrate
Oct 13 10:45:16 miner local1.warn minergate[553]: Bist took 85968 usec
Oct 13 10:45:32 miner local1.warn minergate[553]: HW WD 240s
Oct 13 10:45:36 miner local1.warn minergate[553]: Bist took 87469 usec
Oct 13 10:45:56 miner local1.warn minergate[553]: Bist took 49637 usec
Oct 13 10:46:01 miner cron.info crond[286]: crond: USER root pid 1664 cmd /usr/bin/php /etc/cron.d/RECORDHashrate
Oct 13 10:46:16 miner local1.warn minergate[553]: Bist took 91935 usec
Oct 13 10:46:32 miner local1.warn minergate[553]: HW WD 240s
Oct 13 10:46:36 miner local1.warn minergate[553]: Bist took 139502 usec
Oct 13 10:46:56 miner local1.warn minergate[553]: Bist took 112386 usec
Oct 13 10:47:01 miner cron.info crond[286]: crond: USER root pid 2027 cmd /usr/bin/php /etc/cron.d/RECORDHashrate
Oct 13 10:47:16 miner local1.warn minergate[553]: Bist took 109157 usec
Oct 13 10:47:32 miner local1.warn minergate[553]: HW WD 240s
Oct 13 10:47:36 miner local1.warn minergate[553]: Bist took 10557 usec
Oct 13 10:47:56 miner local1.warn minergate[553]: Bist took 32237 usec
Oct 13 10:48:01 miner cron.info crond[286]: crond: USER root pid 2383 cmd /usr/bin/php /etc/cron.d/RECORDHashrate
Oct 13 10:48:05 miner local1.warn minergate[553]: Bist took 11073 usec
Oct 13 10:48:06 miner local1.warn minergate[553]: Bist took 44830 usec
Oct 13 10:48:20 miner user.notice root: free-memory:449
Oct 13 10:48:26 miner local1.warn minergate[553]: Bist took 10526 usec
Oct 13 10:48:32 miner local1.warn minergate[553]: HW WD 240s
Oct 13 10:48:33 miner local1.warn minergate[553]: Bist took 89368 usec
Oct 13 10:48:34 miner local1.warn minergate[553]: Bist took 42818 usec
Oct 13 10:48:54 miner local1.warn minergate[553]: Bist took 22715 usec
Oct 13 10:49:01 miner cron.info crond[286]: crond: USER root pid 2721 cmd /usr/bin/php /etc/cron.d/RECORDHashrate
Oct 13 10:49:14 miner local1.warn minergate[553]: Bist took 24039 usec
Oct 13 10:49:32 miner local1.warn minergate[553]: HW WD 240s
Oct 13 10:49:34 miner local1.warn minergate[553]: Bist took 11076 usec
Oct 13 10:49:45 miner local1.warn minergate[553]: Bist took 32951 usec
Oct 13 10:49:46 miner local1.warn minergate[553]: Bist took 10906 usec
Oct 13 10:50:01 miner cron.info crond[286]: crond: USER root pid 3057 cmd /usr/bin/php /etc/cron.d/RECORDHashrate
Oct 13 10:50:06 miner local1.warn minergate[553]: Bist took 10941 usec
Oct 13 10:50:09 miner local1.warn minergate[553]: Bist took 53496 usec
Oct 13 10:50:10 miner local1.warn minergate[553]: Bist took 11069 usec
|
|
|
|
|
Its not about people breaking it or breaking in, we are talking about months here, genuinely they should have had this in hand.
But its all good, its a moot point now, version 3 running, finally they getting multipooling going, hey all good.
hope they keep the 12.5petahash
|
|
|
|
Too little too late imo, been at Antpool since 19th June, tired of the up and downs, this last down was the nail in the coffin for me at Slush. Especially after seeing "Please note our core systems have not been touched in months." This absolutely does not fill me with energy and confidence in regards to Slush. Once again slow to move and upgrade, ultimately it just looks like the Slush management are slow to move everytime and that hurts miners. |
|
|
|
been at Antpool now for exactly 1 week - averaging - 0.16077948 BTC averaging per day for 15TH 1.16043524 BTC Earnings Happy with that..... I'd be back to Slush in a flash if they had the consistency, thats the trouble though, this 2days, then 1 day then run of "bad luck" i cant afford it - seriously, power is too much money. I need consistency. |
|
|
|
So where has the hashrate gone that took Slush from 13+ TH to now a smidge under 8TH. That's 5TH that either left the network, or relocated to another pool.
What's up?
Have you seen this rotten ass luck! - fk that - i shifted to Antpool on the 19th, i keep checking, i KNOW i made a better move, averaging a good payout per day too. |
|
|
|
|
Myself, I think Slushie was good for a time, but tbh I've found it lacking, I've looked at all the "evidence" and we should be getting 5 a day minimum, we aren't and haven't been for a long time. Sadly I must move on.
It's been real Slushie.
Where am i now? crusing between the Ghash, elgius and btc guild. on average they outperform slushie by well...... ALOT.
|
|
|
|
Here's version 4.7. It adds HTTPS support for non API use. This probably does not work with Bitmain hardware, and may not work with all hosting configurations for Spondoolie hardware. Download link: MMinerMonitor47.zipM Works perfectly here -  |
|
|
|
man i just do not know what to think 1 day, 13:51:51 slush? what is going on?
WTF ! this is bullshitis maximus SLUSH! or should i say SLUDGE! cos thats what it feels like knee deep in shit atm ~! with NO MOVEMENT! |
|
|
|
My rental ran out. I haven't seen a block take longer than 24hrs in a long time. I'm done with mining btc for now.
Tell me about it .... 26hrs+ and counting ... what a day! that and the bitcoin price .... I don't blame you man, at least on slush, but if the block were ticking over, I'd keep mining up until the entire system imploded or I went broke, whichever first. WHAT THE FLAMING FUCK ! THIS IS GOING TO BE A 36 Hour Block! something smells like horse shit here there is no way a block could take this long with 10/THs of mining power FUCKING "A" 36 hr block -- if it looks like shit - its probably shit ! |
|
|
|
My rental ran out. I haven't seen a block take longer than 24hrs in a long time. I'm done with mining btc for now.
Tell me about it .... 26hrs+ and counting ... what a day! that and the bitcoin price .... I don't blame you man, at least on slush, but if the block were ticking over, I'd keep mining up until the entire system imploded or I went broke, whichever first. WHAT THE FLAMING FUCK ! THIS IS GOING TO BE A 36 Hour Block! |
|
|
|
OK, I fixed the 0Gh/s problem. No matter how many times I rebooted or what I did to my S3, I only got 0Gh/s. The fix was that I needed to physically reboot it. Now, its running fine on the 0103 firmware with the S3 voltage settings.
What voltage settings are you running? |
|
|
|
Of the last 3 firmwares, the 12/16 seem to be the best. I know they took it down, but it my early batch S3 up to 500G consistently. I think I will go back to that one. It was better than the 12/19.
OMG! Thank you thank you thank you Darthswan! - that firmware is stable as ! |
|
|
|
$283.91 on bitstampUSD. Sayonara smilingloki.
FFS!! it was at 306 this morning! 283.80 USD bid: 283.90 ask: 283.71 Oh that sux - if the wife sees this, she'll order shutdown! |
|
|
|
|
