Guys start putting technical discussion in here. This thread was never really meant for it and findings don't get amalgamated into the OP.
Topic: ANTMINER S2 Discussion and Support Thread - page 144. (Read 355820 times)
Which is the default username and password?
Root?
Root?
Root?
Root?
user: root
pass: root
Which is the default username and password?
Root?
Root?
Root?
Root?
Found my culprit with the faulty antminer.
Seems one of my slots doesn't report any temperatures when a module is running in it.
This makes the fans go haywire and probably trip a security thing in the antminer it self or the PSU
so running with 1 blade less works fine?
S1's were a breeze compared to what ive gone through with this one S2.
its no longer hashing but all my other rigs are back online and happy...
im gunna try an ether switch and see if it helps.
i really like the S2 design, its much more professional looking and the boards slotting in like they do is sweet.... but, it aint hashing and that sucks ass
im gonna name it 'seriousS2'
its no longer hashing but all my other rigs are back online and happy...
im gunna try an ether switch and see if it helps.
i really like the S2 design, its much more professional looking and the boards slotting in like they do is sweet.... but, it aint hashing and that sucks ass
im gonna name it 'seriousS2'
S2 is nothing compared to S1 .
Sorry you guys have so many problems with the S2. S1 looks like a breeze compared to this.
Any info on batch 3?
No problems for me. Setting up couple of S2 batch 2's was pretty much plug and play. Now hashing at around 1025 GH/s each in my living room. The noise of the fans speeding up and slowing down is quite annoying. I will move them to a DC this weekend. Any info on batch 3?
Sorry you guys have so many problems with the S2. S1 looks like a breeze compared to this.
Any info on batch 3?
Any info on batch 3?
my avg hashing speed at poll is 930 gh
why?
what is the avg?
why?
what is the avg?
Edgar, Batch 3??
And seems like you are fighting a bad PSU, and maybe a bad blade or slot. I would test the blade in another slot just to be sure (and maybe opposite of BBB) , or in another good S2 if possible.
And I think that with the 9 blades you will eventually settle down to around 900GH/s. And keeping the case lid on does seem to allow the fans to cool the unit better.
And seems like you are fighting a bad PSU, and maybe a bad blade or slot. I would test the blade in another slot just to be sure (and maybe opposite of BBB) , or in another good S2 if possible.
And I think that with the 9 blades you will eventually settle down to around 900GH/s. And keeping the case lid on does seem to allow the fans to cool the unit better.
after 20 minutes cooling down (and changing S1 IP) reset buttin works...
will try again with stock settings & 1l1l1l1l1ls SD image
Off the bat its doing nothing,
Antminer S2
192.168.1.99
0GH/s
Max 0C
so its not hashing for 1l1l1l1l1l either....
im 24 hrs deep now with this fkn rig... not happy at all
So it doesn't work with 1l1l1l1l1l's SD image (unmodified)... that worries me. That image worked for me (and obviously 1l1l1l1l1l). Must be a piece of faulty hardware because we know that software image works.will try again with stock settings & 1l1l1l1l1ls SD image
Off the bat its doing nothing,
Antminer S2
192.168.1.99
0GH/s
Max 0C
so its not hashing for 1l1l1l1l1l either....
im 24 hrs deep now with this fkn rig... not happy at all
A couple of shots in the dark:
1) Try running 1l1l1l1l1l's SD image on another new SD card (just to rule out the chance of a faulty new SD card).
2) Try running it with just one hashing card, to see if you can get anything hashing at all. If that works, build it up slowly one card at a time, testing each time that each additional card works. If one card doesn't work, try a different card and a different slot until you can get one card hashing. If you can't get even one card to hash then something central must be the issue: BBB, daughter-board that BBB sits on, backplane at the bottom...
Found my culprit with the faulty antminer.
Seems one of my slots doesn't report any temperatures when a module is running in it.
This makes the fans go haywire and probably trip a security thing in the antminer it self or the PSU
This probably won't help but, I lived overseas and remember that not only did most electronics have a 110/220 volt selector but some had an internal 50/60 hrz cycle switch. Things like clockradio's would do weird things if the cycle switch was in the wrong position but they would still try to work. I doubt the PSU's have this 50/60 setting but it could explain some of the issues if the supplier screwed up.
PSU is now officially DEAD....
Emailing Bitmain AGAIN....
Emailing Bitmain AGAIN....
looks like Bitmain should've listened to all the numerous shouts made here about properly sizing the psu, or atleast gave the option of no psu and/or better ventilated the unit.
For those looking to turn off their units gracefully, use the powerdown command from the CLI, ive tested it a few times and it seems to work.
PSU is now officially DEAD....
Emailing Bitmain AGAIN....
edgar, I have a dead PSU too...haven't emailed BITMAIN about yet since I was going to give it one more try, but I know what is going to happen. It will work for 8 hrs and then shut down again, and since I haven't had the chance to baby sit it I haven't been able to test it. Emailing Bitmain AGAIN....
When it first when down, even after power off for 5 mins and then trying again, it didn't work, but 15/20 mins. later it worked again, except I didn't give it 2nd try since I wasn't going to baby sit it then and there. I installed one of own know GOOD working PSU. And now 29 of 30 Antminer S2 blades hashing away.
Sorry to hear you haven't been able to hash with it yet, but let the PSU cool down and it will work again for now.
Edgar, were you able to log in to your S2?
eventually yes, using
192.168.1.99/index.html
thanks to Zelek Uther for that...
Still not hashing though, despite 24 hrs of 'surgery'
I've also found that chopping and changing ip addresses doesn't always work very well, especially on windows networks and sometimes a router reboot solves things or just wait 5 mins after each time you change something to make sure the network has updated.
Not having fun with these.
Had to drill the screws to plug in the stupid ribbon cable. Had to take out a fan to get there. Internal ethernet cable is busted, had to replace it. Everything inside is covered in spooge. All the cards are loose and shaky.
Now Im stuck at 0gh/s. anyone have any ideas?
Had to drill the screws to plug in the stupid ribbon cable. Had to take out a fan to get there. Internal ethernet cable is busted, had to replace it. Everything inside is covered in spooge. All the cards are loose and shaky.
Now Im stuck at 0gh/s. anyone have any ideas?
This happened to me. Re-flash the firmware from the Bitmain webpage if you havent already (grab the latest one). fired right up after for me.
I already did that. Having cooling issues now. Seems like if any module touches 63C the entire thing shuts down.
I've not received my unit yet, but read that others have had success by taking out a board or 2 to take some load off the psu. I'd suggest removing the boards closest to the psu as they seem to get the hottest... it might help with the overheating issue.
Edgar, were you able to log in to your S2?
Sorry, but Bitmain failed here.
Not having fun with these.
Had to drill the screws to plug in the stupid ribbon cable. Had to take out a fan to get there. Internal ethernet cable is busted, had to replace it. Everything inside is covered in spooge. All the cards are loose and shaky.
Now Im stuck at 0gh/s. anyone have any ideas?
Had to drill the screws to plug in the stupid ribbon cable. Had to take out a fan to get there. Internal ethernet cable is busted, had to replace it. Everything inside is covered in spooge. All the cards are loose and shaky.
Now Im stuck at 0gh/s. anyone have any ideas?
This happened to me. Re-flash the firmware from the Bitmain webpage if you havent already (grab the latest one). fired right up after for me.
System Upgrade Failed
tar: invalid magic tar: short read cp: can't stat '*': No such file or directory
send it back boss.
what? the whole thing?
surely we can work out which component is borked, no?
hopeful for ya. best luck.
Jump to: