Pages:
Author

Topic: Bitmain Announces the Antminer R4 and APW5 Power Supply, Designed for Silence - page 11. (Read 84827 times)

hero member
Activity: 630
Merit: 500
With the difficulty rising nearly exponentially is anyone really making money with this miner?  Doing the calculations it seems literally impossible to be profitable.
member
Activity: 123
Merit: 17
How often do you guys reboot R4?
Does it matter?
sr. member
Activity: 407
Merit: 255
Got back a repaired R4.  The top chain is not reporting temps and has two bad chips. It is still hashing at 8GH/s. So is this within the operating parameters that Bitmain tolerates? Kind of sucks to not get a 100% repaired R4.
legendary
Activity: 2408
Merit: 1102
Leading Crypto Sports Betting & Casino Platform
sent mine back for repair at thier cost they sent me a 'repaired' unit
that stopped hashing after one week.  nothing shows up on status screens after
multiple reboots i think the controller is bad as well as the boards
and of couse thier support is so slow sent an email with screen shots thuraday no response
legendary
Activity: 2464
Merit: 1710
Electrical engineer. Mining since 2014.
I too had to pay 70 EUR (EMS delivery) to ship my batch4 R4 for repair after second hash board failed.
It's irritating that they can't cover it (the 70 EUR shipment).
I'm already losing my money by not having the miner mining and then I have to pay the shipping too.
sr. member
Activity: 441
Merit: 250
No zuo no die why you try, u zuo u die dont be shy
Here's a screen grab from the miner. I've tried with only 1 hashboard connected and have also swapped the IO channels. Perhaps the temps are a bit low.

http://imgur.com/a/LB9JL

I don't think it's heat related. I had my second R4 heat output aimed at the intake of the faulty R4, I let them run for 10-15 minutes and then rebooted the faulty unit - no change. I guess I've got the triple hit, both R4's failed, I sent both back for warranty and now one of the repaired units has lost a hashboard. My miners operate in a datacenter which is kept at 20c.

Guys give the R4's a miss, it's going to cost me another $120 to send this unit back, so I've spent $360 on freight to get 1 solid weeks worth of mining. On the other hand my T9's have been mining away without a single hiccup. I guess it's only time until the other R4 fails.

This is really unbearably terrible. Sorry to hear that.
full member
Activity: 120
Merit: 100
Here's a screen grab from the miner. I've tried with only 1 hashboard connected and have also swapped the IO channels. Perhaps the temps are a bit low.

http://imgur.com/a/LB9JL

I don't think it's heat related. I had my second R4 heat output aimed at the intake of the faulty R4, I let them run for 10-15 minutes and then rebooted the faulty unit - no change. I guess I've got the triple hit, both R4's failed, I sent both back for warranty and now one of the repaired units has lost a hashboard. My miners operate in a datacenter which is kept at 20c.

Guys give the R4's a miss, it's going to cost me another $120 to send this unit back, so I've spent $360 on freight to get 1 solid weeks worth of mining. On the other hand my T9's have been mining away without a single hiccup. I guess it's only time until the other R4 fails.
sr. member
Activity: 277
Merit: 250
I have this random problem on one of the boards too. How's your temperature?
It's a little high around 93 chip temp, but that doesn't seem to be what causes it. The temp seems to be in the same range when it's running without incident. It's the autotune batch so there's not much I can do with the fan speed. It's in the garage where the ambient temp is around 40-50F, depending on the day. It'll go to Oregon mines when the outside temps start rising come summer.

My R4B1 didn't like cold air intake. Board temp was ok but one board just keep failing.
I planned to heat my crawl place under my house with it but can't because of cold air (5-10C ).
I move it into my house at higher ambient and this fixed my problem.

Below 20C , didn't run or badly. Higher ambient temp is ok.  

What's your intake temperature ?

It was in the house when I first booted it up to set it up. I keep it at 68F here. It booted up with one board bad. So I don't think the ambient temp is the problem.
sr. member
Activity: 307
Merit: 250
Red led blinking on the bad board ? Should be steady when full hashing, blinking when initialized.
Mine didn't light up until it was warm enough.
You can try a hairdryer to warm the bad board and reboot it. Watch if led's have some activities ... if not you're probably screw.

Edit: your board is detected but not hashing. My problem was board not detected at all .
full member
Activity: 120
Merit: 100
Here's a screen grab from the miner. I've tried with only 1 hashboard connected and have also swapped the IO channels. Perhaps the temps are a bit low.

http://imgur.com/a/LB9JL
sr. member
Activity: 307
Merit: 250
Had a strange issue with R4B2. Suddenly no shares were showing up on the pool...  Checked the gui when I got home and saw that all pools were alive but the last share sent was over 3 hours previously.  Weird, so I did a soft reboot and after the requisite time it spends restarting shares started showing up on the pool again.  This was after 56 days running, maybe hit another software bug when running for long periods and some register overflows or something.  Love that, keeps it interesting! /sarc
Had a similar problem with my batch 4. It would randomly stop hashing. Sometimes in as little as an hour and another was almost 30 days. A simple reboot seems to solve the problem with mine also.

I have this random problem on one of the boards too. How's your temperature?
It's a little high around 93 chip temp, but that doesn't seem to be what causes it. The temp seems to be in the same range when it's running without incident. It's the autotune batch so there's not much I can do with the fan speed. It's in the garage where the ambient temp is around 40-50F, depending on the day. It'll go to Oregon mines when the outside temps start rising come summer.

My R4B1 didn't like cold air intake. Board temp was ok but one board just keep failing.
I planned to heat my crawl place under my house with it but can't because of cold air (5-10C ).
I move it into my house at higher ambient and this fixed my problem.

Below 20C , didn't run or badly. Higher ambient temp is ok. 

What's your intake temperature ?
sr. member
Activity: 277
Merit: 250
Had a strange issue with R4B2. Suddenly no shares were showing up on the pool...  Checked the gui when I got home and saw that all pools were alive but the last share sent was over 3 hours previously.  Weird, so I did a soft reboot and after the requisite time it spends restarting shares started showing up on the pool again.  This was after 56 days running, maybe hit another software bug when running for long periods and some register overflows or something.  Love that, keeps it interesting! /sarc
Had a similar problem with my batch 4. It would randomly stop hashing. Sometimes in as little as an hour and another was almost 30 days. A simple reboot seems to solve the problem with mine also.

I have this random problem on one of the boards too. How's your temperature?
It's a little high around 93 chip temp, but that doesn't seem to be what causes it. The temp seems to be in the same range when it's running without incident. It's the autotune batch so there's not much I can do with the fan speed. It's in the garage where the ambient temp is around 40-50F, depending on the day. It'll go to Oregon mines when the outside temps start rising come summer.
sr. member
Activity: 441
Merit: 250
No zuo no die why you try, u zuo u die dont be shy
Had a strange issue with R4B2. Suddenly no shares were showing up on the pool...  Checked the gui when I got home and saw that all pools were alive but the last share sent was over 3 hours previously.  Weird, so I did a soft reboot and after the requisite time it spends restarting shares started showing up on the pool again.  This was after 56 days running, maybe hit another software bug when running for long periods and some register overflows or something.  Love that, keeps it interesting! /sarc
Had a similar problem with my batch 4. It would randomly stop hashing. Sometimes in as little as an hour and another was almost 30 days. A simple reboot seems to solve the problem with mine also.

I have this random problem on one of the boards too. How's your temperature?
sr. member
Activity: 277
Merit: 250
Had a strange issue with R4B2. Suddenly no shares were showing up on the pool...  Checked the gui when I got home and saw that all pools were alive but the last share sent was over 3 hours previously.  Weird, so I did a soft reboot and after the requisite time it spends restarting shares started showing up on the pool again.  This was after 56 days running, maybe hit another software bug when running for long periods and some register overflows or something.  Love that, keeps it interesting! /sarc
Had a similar problem with my batch 4. It would randomly stop hashing. Sometimes in as little as an hour and another was almost 30 days. A simple reboot seems to solve the problem with mine also.
full member
Activity: 120
Merit: 100
One of my returned R4's drop a board this afternoon, a quick restarted got it going again. It had been mining for just a touch over 7 days since it was returned. This makes me a little nervous.

OK - now the hashboard shuts down within a couple of minutes of a reboot.

I wish I had never purchased these units.
full member
Activity: 206
Merit: 100
One of my returned R4's drop a board this afternoon, a quick restarted got it going again. It had been mining for just a touch over 7 days since it was returned. This makes me a little nervous.
That's really bad. My two R4 batch 2 (both repaired) are working without problem almost month now. Hashing constantly over 16TH together.
full member
Activity: 120
Merit: 100
One of my returned R4's drop a board this afternoon, a quick restarted got it going again. It had been mining for just a touch over 7 days since it was returned. This makes me a little nervous.
legendary
Activity: 2408
Merit: 1102
Leading Crypto Sports Betting & Casino Platform
Had a strange issue with R4B2. Suddenly no shares were showing up on the pool...  Checked the gui when I got home and saw that all pools were alive but the last share sent was over 3 hours previously.  Weird, so I did a soft reboot and after the requisite time it spends restarting shares started showing up on the pool again.  This was after 56 days running, maybe hit another software bug when running for long periods and some register overflows or something.  Love that, keeps it interesting! /sarc

Bitmain is so much junk never buying thier junk again, i bough an r4 a board died sent it back for repair they sent me another one same fucking thing so done with them

I just want a fucking refund at this point , one month of lost mining time who is going to refund that huh ? fuck you bitmain
hero member
Activity: 1610
Merit: 538
I'm in BTC XTC
Had a strange issue with R4B2. Suddenly no shares were showing up on the pool...  Checked the gui when I got home and saw that all pools were alive but the last share sent was over 3 hours previously.  Weird, so I did a soft reboot and after the requisite time it spends restarting shares started showing up on the pool again.  This was after 56 days running, maybe hit another software bug when running for long periods and some register overflows or something.  Love that, keeps it interesting! /sarc
full member
Activity: 120
Merit: 100
The DC where my malfunctioning droid R4B4 has been sputtering along at half speed has started the RMA process along with various S9s they have there too. Nice failure rate on these units, hopefully this doesn't take too long...  Tongue

I sent my two R4's off last Tuesday, tracking indicates I should have them back tomorrow. I'm hoping for better luck this time around.

Two R4's are now back in service, hashing at full rate.

26 hours on, still going strong.
Pages:
Jump to: