dogjunior
|
|
February 28, 2017, 05:35:07 AM |
|
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.
|
|
|
|
powrslave
|
|
March 02, 2017, 12:44:44 AM |
|
How often do you guys reboot R4? Does it matter?
|
|
|
|
Brob12321
|
|
March 02, 2017, 01:01:45 AM |
|
With the difficulty rising nearly exponentially is anyone really making money with this miner? Doing the calculations it seems literally impossible to be profitable.
|
|
|
|
NotFuzzyWarm
Legendary
Online
Activity: 3682
Merit: 2607
Evil beware: We have waffles!
|
|
March 02, 2017, 01:36:09 AM Last edit: March 02, 2017, 05:09:30 PM by NotFuzzyWarm |
|
How often do you guys reboot R4? Does it matter?
For me, especially with any auto-tune Ant -- only when needed because sustained hash rate dropped substantially. If using miner software like Awesome Miner try restarting just CGminer - not the Bitmain GUI soft-reboot of the whole controller. Should skip the normal initialization needed. For my s7's and older s9's is good to reboot every month or so. I've noticed that all of my ants from at least s5's get - odd - after 30-50 days. Seem to run fine but things like HW errors gets stuck, maybe hash rates drops several %. Reboot and all is well again.
|
|
|
|
VRobb
|
|
March 02, 2017, 03:28:06 AM |
|
Funny you'd say that, notfuzzy... my R4 stopped sending shares to the pool after 56 days though the gui showed the pool was alive and all was apparently well. Soft reboot got it sending shares to the pool again. I figured it was a register of some sort overflowing and halting the code somewhere in there. Amateur hour if you ask me.
|
I don't believe in superstition because it's bad luck: 13thF1oor6CAwyzyxXPNnRvu3nhhYeqZdc These aren't the Droids you're looking for: S5 & S7 (Sold), R4B2, R4B4 (RIP), 2x S9 obsolete, 2xS15-28, S17-56, S17-70 Pushing a whopping 1/5 PH! Oh The SPEED!!!
|
|
|
VRobb
|
|
March 02, 2017, 04:53:55 PM |
|
Hey, you guys see that Bitmain is handing out coupons for buyers of certain batches of the S9? We buyers of flaky R4's should be close behind, no?
|
I don't believe in superstition because it's bad luck: 13thF1oor6CAwyzyxXPNnRvu3nhhYeqZdc These aren't the Droids you're looking for: S5 & S7 (Sold), R4B2, R4B4 (RIP), 2x S9 obsolete, 2xS15-28, S17-56, S17-70 Pushing a whopping 1/5 PH! Oh The SPEED!!!
|
|
|
IITravel01
|
|
March 02, 2017, 07:43:08 PM |
|
Neither of my browsers will log on to www.bitmaintech.com (both state the site is unsafe), anyone else having this problem?
|
|
|
|
Micky25
Legendary
Offline
Activity: 974
Merit: 1000
|
|
March 02, 2017, 07:46:12 PM |
|
The reason behind that coupons is probably not to make good on the customer, but to leverage sales. R4=100% failure rate? Coupons for everyone then! Hey, you guys see that Bitmain is handing out coupons for buyers of certain batches of the S9? We buyers of flaky R4's should be close behind, no?
|
|
|
|
lightfoot
Legendary
Offline
Activity: 3122
Merit: 2242
I fix broken miners. And make holes in teeth :-)
|
|
March 03, 2017, 10:48:06 PM |
|
Neither of my browsers will log on to www.bitmaintech.com (both state the site is unsafe), anyone else having this problem? Looks like an expired cert on their side. Oops. Meantime question: Would it be worth my looking into these things to see if they can be fixed stateside?
|
|
|
|
|
NotFuzzyWarm
Legendary
Online
Activity: 3682
Merit: 2607
Evil beware: We have waffles!
|
|
March 04, 2017, 05:21:00 AM |
|
or just type in Bitmain.com
|
|
|
|
HagssFIN
Legendary
Offline
Activity: 2436
Merit: 1706
Electrical engineer. Mining since 2014.
|
|
March 04, 2017, 02:39:02 PM |
|
Well my faulty R4 is now fixed and on the way back to my place. Fedex has it in Cologne (Germany) at the moment. No details about what was repaired though.
|
|
|
|
hall85296
Newbie
Offline
Activity: 1
Merit: 0
|
|
March 04, 2017, 06:49:48 PM |
|
I have a question about shipping an R4 back to bitmain for warranty work because it has stopped hashing on the bottom board. When returning for warranty work do i have to pay any duties or taxes going into Hong Kong? Also does any one have a sample shipping label you could share with me? When trying to add "TUNG-D INTERNATIONAL DEVELOPMENT LIMITED Warehouse No.3811" to the company name on UPS it cuts it off and i just want to make sure it does not get lost in the mail. this whole process is a pain for a miner that is only 60 days old.
|
|
|
|
Micky25
Legendary
Offline
Activity: 974
Merit: 1000
|
|
March 04, 2017, 09:16:18 PM |
|
I have a question about shipping an R4 back to bitmain for warranty work because it has stopped hashing on the bottom board. When returning for warranty work do i have to pay any duties or taxes going into Hong Kong? Also does any one have a sample shipping label you could share with me? When trying to add "TUNG-D INTERNATIONAL DEVELOPMENT LIMITED Warehouse No.3811" to the company name on UPS it cuts it off and i just want to make sure it does not get lost in the mail. this whole process is a pain for a miner that is only 60 days old.
You "only" have to pay the shipping costs. For the adress, just use every available field and space and do not take care, which field is for what. The final result should look like this: Tel. and e.mail come from fields outside the adress space here. And I agree, they should absolutely make this a free pickup service.
|
|
|
|
VRobb
|
|
March 08, 2017, 03:21:53 AM |
|
My sick droid R4B4 has finally arrived at the imperial droid maintenance facility, and hopefully will be repaired and sent back to the btc mine at my Hoth like DC. Ran for about a day before a hashboard died, and that was on December 28th... Was running at half speed for a bit, but seriously folks LAME!
|
I don't believe in superstition because it's bad luck: 13thF1oor6CAwyzyxXPNnRvu3nhhYeqZdc These aren't the Droids you're looking for: S5 & S7 (Sold), R4B2, R4B4 (RIP), 2x S9 obsolete, 2xS15-28, S17-56, S17-70 Pushing a whopping 1/5 PH! Oh The SPEED!!!
|
|
|
HagssFIN
Legendary
Offline
Activity: 2436
Merit: 1706
Electrical engineer. Mining since 2014.
|
|
March 08, 2017, 05:59:46 AM |
|
I got my faulty 8.7Th/s unit fixed back here in Finland and mining smoothly again so far Smooth delivery via Fedex, no need to deal with customs.
|
|
|
|
VRobb
|
|
March 09, 2017, 01:23:23 PM |
|
Repair finished, R4B4 is being sent back to Hoth... Fingers crossed all is good!
|
I don't believe in superstition because it's bad luck: 13thF1oor6CAwyzyxXPNnRvu3nhhYeqZdc These aren't the Droids you're looking for: S5 & S7 (Sold), R4B2, R4B4 (RIP), 2x S9 obsolete, 2xS15-28, S17-56, S17-70 Pushing a whopping 1/5 PH! Oh The SPEED!!!
|
|
|
HagssFIN
Legendary
Offline
Activity: 2436
Merit: 1706
Electrical engineer. Mining since 2014.
|
|
March 09, 2017, 08:10:48 PM |
|
They shipped my repaired 8.7Th/s unit back with newer firmware version December 9. Temps are better (lower) than before. December 2 firmware version is the newest one available at Bitmain.com at the moment. I asked about download link for the December 9 firmware to update my other 8.7Th/s unit which has high-ish temps, but they said they are still testing it. They said that it will be available at the support page when it's ready.
|
|
|
|
LASERminer
|
|
March 14, 2017, 07:50:30 PM |
|
With the difficulty rising nearly exponentially is anyone really making money with this miner? Doing the calculations it seems literally impossible to be profitable.
Maybe your calculations do not include profit from selling used unit before it becomes obsolete
|
|
|
|
kapir
Newbie
Offline
Activity: 1
Merit: 0
|
|
March 14, 2017, 10:57:16 PM |
|
One of my R4's that stopped hashing on one board has stopped hashing completely after trying to restore the original firmware. The hardware version listed under system overview says " Socket connect failed: Connection refused".
I have tried powering off several times, reboots, updating firmware, etc. No more hashing. There has to be an easy fix to this without sending to Hong Kong or letting sit in Denver for weeks on end. Any thoughts?
EDIT: unplugged the original board that did not hash and fired back up, the one remaining board is hashing again at 4th/s!
Exactly same fault here - I think we discovered common issue. Same thing happened to me
|
|
|
|
|