Topic: Bitmain Announces the Antminer R4 and APW5 Power Supply, Designed for Silence - page 18. (Read 84827 times)
January 04, 2017, 03:13:02 PM
Cold restart: turn off PSU for 10-15 seconds, turn back on. Otherwise I try to never reboot my miners unless I have to. My R4B2 has been rock solid since I got it. My R4B4 is the moody one...
January 04, 2017, 03:09:50 PM
HEY BITMAIN, WOULD BE NICE TO SEE SOME HELP WITH THESE PROBLEMS INSTEAD OF CHARGING EVERYONE MORE MONEY TO FIX YOUR CRAP PRODUCTS.
Everyone should start bombarding Bitmain with complaints otherwise this type of behavior will continue
Everyone should start bombarding Bitmain with complaints otherwise this type of behavior will continue
Pool side and it should certainly be up to full speed by now. It's obviously doing the 'one board down' thing which seems to be not too uncommon if you check the R4 thread. Did it to me once while I was setting it up to mine here via nya, cold restart got it back - seems warm reboots can cause it for some reason.
Harrumph!
Harrumph!
What is the best way to do a full COLD shutdown with the R4 B2?
All I see in the web management console is the Restart option.
I don't want to just turn off the power supply for fear of this thing going batty or losing a board.
I've had it up and hashing on CKPool since 12/13/2016, and I have been restarting it once a week based on advice from here.
Yesterday was supposed to be the third reboot, but I'm holding off & might let it run for 2 or 3 weeks straight or even monthly b4 restarting.
Any advice would be appreciated.
Thanks all.
January 04, 2017, 02:43:42 PM
HEY BITMAIN, WOULD BE NICE TO SEE SOME HELP WITH THESE PROBLEMS INSTEAD OF CHARGING EVERYONE MORE MONEY TO FIX YOUR CRAP PRODUCTS.
Everyone should start bombarding Bitmain with complaints otherwise this type of behavior will continue
Everyone should start bombarding Bitmain with complaints otherwise this type of behavior will continue
January 04, 2017, 12:51:30 PM
Quote
The socket error state is expected and it's been like that since later batches of S7. Still, sorry for your loss.
Well I've just lost a couple of days mining so hopefully all is not lost
I've had the miner powered off since last night and going to try a factory reset when I get home! Say a prayer for me guys. This cost me about €1750 what with the miner, PSU, shipping and import taxes... I was hoping to make a ROI what with BTC doing great right now!
I will post an update later and let you know if the reset worked. I'm still getting 8.7TH/s but I'm worried about the temperature not being reported on one of the hashing boards. That makes me concerned that the device may over heat burn the building down.....
January 04, 2017, 12:15:00 PM
Similar issues guys.. R4 Batch 4.. After multiple restarts it stopped hashing on one board - It was working 'perfectly' at the start. After firmware update back to both boards but now on the affected board, there is no temp display. I am going to try a factory reset later today. It seems Bitmain are more concerned with getting your Bitcoin than with the quality of their releases. Just FYI I'm using an APW3 PSU which Bitmain confirmed would work prior to purchase.
The reason I put perfectly in commas is because the when the R4 started up at first, it would not hash.. It wouldn't detect the firmware but instead reported 'Socket Error - Connection Refused'. It still does this but exactly 8.5 minutes after boot, it detects the firmware and starts hashing.
Very messy Bitmain!
The reason I put perfectly in commas is because the when the R4 started up at first, it would not hash.. It wouldn't detect the firmware but instead reported 'Socket Error - Connection Refused'. It still does this but exactly 8.5 minutes after boot, it detects the firmware and starts hashing.
Very messy Bitmain!
The socket error state is expected and it's been like that since later batches of S7. Still, sorry for your loss.
January 04, 2017, 09:26:54 AM
Well, this seems to be rather common now. My one R4 B2 that's been running for 4 weeks had one board stop working yesterday. After reading here that it's been happening to others and that some have gotten it working again by updating the firmware, I tried that also. Firmware update seemed to go fine, but only 1 board working still and after the firmware update the other board seems to be working but it's showing a large number of total HW errors even though the working board errors are almost none. Now what?
I would disconnect the INOP board and hopefully you see less HW on the other board. I can't prove this but I would suspect keeping power going to the INOP board may further damage it.
I am sending one of my broken R4's to Denver and will keep everyone posted on turn around time. I have one other that needs repair that I might send to Hong Kong.
January 04, 2017, 06:53:31 AM
Similar issues guys.. R4 Batch 4.. After multiple restarts it stopped hashing on one board - It was working 'perfectly' at the start. After firmware update back to both boards but now on the affected board, there is no temp display. I am going to try a factory reset later today. It seems Bitmain are more concerned with getting your Bitcoin than with the quality of their releases. Just FYI I'm using an APW3 PSU which Bitmain confirmed would work prior to purchase.
The reason I put perfectly in commas is because the when the R4 started up at first, it would not hash.. It wouldn't detect the firmware but instead reported 'Socket Error - Connection Refused'. It still does this but exactly 8.5 minutes after boot, it detects the firmware and starts hashing.
Very messy Bitmain!
The reason I put perfectly in commas is because the when the R4 started up at first, it would not hash.. It wouldn't detect the firmware but instead reported 'Socket Error - Connection Refused'. It still does this but exactly 8.5 minutes after boot, it detects the firmware and starts hashing.
Very messy Bitmain!
January 04, 2017, 01:47:59 AM
Well, this seems to be rather common now. My one R4 B2 that's been running for 4 weeks had one board stop working yesterday. After reading here that it's been happening to others and that some have gotten it working again by updating the firmware, I tried that also. Firmware update seemed to go fine, but only 1 board working still and after the firmware update the other board seems to be working but it's showing a large number of total HW errors even though the working board errors are almost none. Now what?
January 02, 2017, 09:13:09 PM
firmware update did it for me all boards work althouhh
the temps of chip 1 is still shown as 97
74
appears i have a bad board too so anyoying now i have to figure out this waranty crap and waste hard earned btc on shipping screw you bitmain !
the temps of chip 1 is still shown as 97
74
appears i have a bad board too so anyoying now i have to figure out this waranty crap and waste hard earned btc on shipping screw you bitmain !
January 02, 2017, 07:03:35 PM
Just got my batch 4 hooked up today and of course it only hashes on one board. That is the last piece on Bitmain gear I will ever buy
i got a strange one as well only onr board hashesbut at first both boards hashed on the pool i only 5600th
but the first miner tab shows 8750 th , next tab show half
wtf lol
December 31, 2016, 12:51:28 PM
Just got my batch 4 hooked up today and of course it only hashes on one board. That is the last piece on Bitmain gear I will ever buy
When my R4 showed up it was a mess. High temps on the chips. It was not pretty. I opened tickets with Bitmain and they told me to immediately update to the latest software release. Strangely enough that seems to have worked for me. My temps returned to normal ranges and the miner seems happy now. So I would go ahead and do the software update and see if it helps at all.
Thanks, I will try that next.
I have a batch 2 that only hashes on one board as well and the update did not fix the problem.
Out of the four R4's that I own, 2 boards do not hash (25% failure) and I have not had much better luck with the S9
Sadly this seems to be a common story with Bitmain. The quality of their gear is poor.
December 31, 2016, 12:48:11 PM
Just got my batch 4 hooked up today and of course it only hashes on one board. That is the last piece on Bitmain gear I will ever buy
When my R4 showed up it was a mess. High temps on the chips. It was not pretty. I opened tickets with Bitmain and they told me to immediately update to the latest software release. Strangely enough that seems to have worked for me. My temps returned to normal ranges and the miner seems happy now. So I would go ahead and do the software update and see if it helps at all.
Thanks, I will try that next.
I have a batch 2 that only hashes on one board as well and the update did not fix the problem.
Out of the four R4's that I own, 2 boards do not hash (25% failure) and I have not had much better luck with the S9
EDIT: Well I updated firmware and now both boards do not hash. Fucking Bitmain junk
December 31, 2016, 12:43:07 PM
Just got my batch 4 hooked up today and of course it only hashes on one board. That is the last piece on Bitmain gear I will ever buy
When my R4 showed up it was a mess. High temps on the chips. It was not pretty. I opened tickets with Bitmain and they told me to immediately update to the latest software release. Strangely enough that seems to have worked for me. My temps returned to normal ranges and the miner seems happy now. So I would go ahead and do the software update and see if it helps at all.
December 31, 2016, 12:39:12 PM
Just got my batch 4 hooked up today and of course it only hashes on one board. That is the last piece on Bitmain gear I will ever buy
December 29, 2016, 10:05:19 PM
Quite sure they're all sold out. Keep an eye on this thread, bitmain usually announces new batch(es) a day or so before sales open. Then jump on it!
December 29, 2016, 05:25:23 AM
What is the link for the Batch 4?
I only see Batch 3 out and it is sold out.
I only see Batch 3 out and it is sold out.
December 29, 2016, 02:06:56 AM
R4 B2 @ CKPool. Difficulty currently set at 2048.
Is there a preferred setting for this value for the R4?
Is there a preferred setting for this value for the R4?
I would recommend not setting a difficulty and letting the pool set it. Kano.is has set the difficulty on my R4 at 6.2k
Thanks
both units hash to spec one at 8.7 TH and the other at 8 TH
I must say Bitmain out did themselves with these units I might just keep them as space heaters, they generate a nice bit of heat and are relatively quiet
really light and much smaller than what I imaginmed, I cant belive i had an SP 1350 or whatever that hashed for 4.5 TH a few years ago and was huge and weighed a ton
just crazy
December 29, 2016, 01:10:05 AM
R4 B2 @ CKPool. Difficulty currently set at 2048.
Is there a preferred setting for this value for the R4?
Is there a preferred setting for this value for the R4?
I would recommend not setting a difficulty and letting the pool set it. Kano.is has set the difficulty on my R4 at 6.2k
Thanks
December 28, 2016, 08:40:31 PM
R4 B2 @ CKPool. Difficulty currently set at 2048.
Is there a preferred setting for this value for the R4?
Is there a preferred setting for this value for the R4?
I would recommend not setting a difficulty and letting the pool set it. Kano.is has set the difficulty on my R4 at 6.2k
December 28, 2016, 07:48:16 PM
I have an R4 B2 that has luckily been humming along fine for over 2 weeks now at about 8.1THs.
I noticed a minimum difficulty setting for CKPool. Currently it is set at 2048.
https://www.kano.is/index.php?k=workmgt
Is there a preferred setting for this value for the R4?
Thanks
I noticed a minimum difficulty setting for CKPool. Currently it is set at 2048.
https://www.kano.is/index.php?k=workmgt
Is there a preferred setting for this value for the R4?
Thanks
Jump to: