 Show Posts
|
|
Pages: [1]
|
Has anyone had any experience with Bitmain RMA process? I sent 2 blades back over 3 weeks ago and havent heard anything. Ive dropped a few emails and no response.
I sent them an S2 blade back from the US, via their UPS account. Total travel time was about a week, and I had an email thread that they worked with me in a few times. Your situation doesn't reflect my experience. Where did you ship from, and has the part made it back to them? I sent it back from New Zealand to their China office. I used their account and ive emailed a contact person there, it took them about 10 days to apologize for the delay but doesnt bother answering my rma query, and that was 3 days ago. Speak of the devil.... just got a reply with tracking number for returning parts but over 3 weeks is still a bit long. |
|
|
|
Has anyone had any experience with Bitmain RMA process? I sent 2 blades back over 3 weeks ago and havent heard anything. Ive dropped a few emails and no response.
I sent them an S2 blade back from the US, via their UPS account. Total travel time was about a week, and I had an email thread that they worked with me in a few times. Your situation doesn't reflect my experience. Where did you ship from, and has the part made it back to them? I sent it back from New Zealand to their China office. I used their account and ive emailed a contact person there, it took them about 10 days to apologize for the delay but doesnt bother answering my rma query, and that was 3 days ago. |
|
|
|
|
Has anyone had any experience with Bitmain RMA process? I sent 2 blades back over 3 weeks ago and havent heard anything. Ive dropped a few emails and no response.
|
|
|
|
|
My batch 3 S2 is plagued with problems.
1. Impossible to reboot/shutdown(Hot or cold) without having do SD recovery. (SD recovery never works first time around)
2. 1 blade intermittently gets XXX00XX ---XX--00 in ASIC status
3. 1 blade permanently gets XXX00XX ASIC Status
4. 1 blade after 2 days stops hashing and temperature shows its about 20 degrees cooler.
Asked for repeated RMA but support keeps on ignoring requests or offers troubleshooting solutions that are no longer relevant.
Pretty pitiful really, I don't how this unit could have passed their Quality Control process.
|
|
|
|
This is an ongoing issue with Bitmain in general. I too was just hit with a failed part, and the turn around on failed product WILL result in serious loss in mining payouts. There is an advantage to going with Bitmain for mining hardware, however due to their support on hardware with issues, you need to factor in as serious losses in revenue .
Yeah I've accepted that I will probably never reach ROI, and its very frustrating/depressing watching your investment go from bad to worse. Bad to worse => to worser.... Got the blue screen of death.... S2 turns on but only getting a blank blue LCD display on the S2. I've re-imaged SD card but did nothing. Waiting for a Bitmain to reply for a RMA request. Don't give up yet. i've had the same thing. try removing all the boards (power off first, of course), then power on. watch the controller board for blue lights. they mean the controller has found a usable boot partition on the SD card and booted from it. if you get it to boot, and can connect to the web page of the controller, then the problem may have been a connection to one of the currently-removed boards. you have to put them back in, but there's a good chance that shutting the system off "hot" will botch the SD image, so you have to ssh into it and shut it down gracefully... shutdown -h now wait for it to do so, then power off. keep us posted. Wow cheers, I managed to get it going again with your advice. I guess I had to be a little more persistent. Since I've turned it back on I've got a whole lot of --x--x---- on 2 of the blades. So I only have 7 functioning 100%, 2 @ about 70% and 1 not 0%. I'm still waiting for a reply from Bitmain for a support query last week on the reason why a blade is running much cooler and literally not hashing. I've tried rebooting machine to clear the ---x--- but they dont seem to clear. Is there a default login and password to SSH into the machine?.. I'm using putty. Well managed to get going for about 5 days however after 2 days one of the blades malfunctioned again, I don't why but the only evidence shows that the blade cools down and stops hashing. I guess it shows when the avg hash starts dropping. This was my original problem other than the rest of the problems I am experiencing. Today I had to relocate the machine which required me to switch off, unfortunately every time I have to switch off I have to image the SD card and spend about 10min pushing it in and out waiting for the device to get read card and get the machine going again. Definitely not a user friendly nor a reliable device. Really this machine should go back to Bitmain but the opportunity cost of sending it back for replacement is losing at least 2 week hashing time when they decide to pull finger and something about it. Yeah it just took me 3 hours to start it back up again, and when i did a different blade has a lot xxxxx of in the ASIC status... Forever plagued with problems. |
|
|
|
This is an ongoing issue with Bitmain in general. I too was just hit with a failed part, and the turn around on failed product WILL result in serious loss in mining payouts. There is an advantage to going with Bitmain for mining hardware, however due to their support on hardware with issues, you need to factor in as serious losses in revenue .
Yeah I've accepted that I will probably never reach ROI, and its very frustrating/depressing watching your investment go from bad to worse. Bad to worse => to worser.... Got the blue screen of death.... S2 turns on but only getting a blank blue LCD display on the S2. I've re-imaged SD card but did nothing. Waiting for a Bitmain to reply for a RMA request. Don't give up yet. i've had the same thing. try removing all the boards (power off first, of course), then power on. watch the controller board for blue lights. they mean the controller has found a usable boot partition on the SD card and booted from it. if you get it to boot, and can connect to the web page of the controller, then the problem may have been a connection to one of the currently-removed boards. you have to put them back in, but there's a good chance that shutting the system off "hot" will botch the SD image, so you have to ssh into it and shut it down gracefully... shutdown -h now wait for it to do so, then power off. keep us posted. Wow cheers, I managed to get it going again with your advice. I guess I had to be a little more persistent. Since I've turned it back on I've got a whole lot of --x--x---- on 2 of the blades. So I only have 7 functioning 100%, 2 @ about 70% and 1 not 0%. I'm still waiting for a reply from Bitmain for a support query last week on the reason why a blade is running much cooler and literally not hashing. I've tried rebooting machine to clear the ---x--- but they dont seem to clear. Is there a default login and password to SSH into the machine?.. I'm using putty. |
|
|
|
This is an ongoing issue with Bitmain in general. I too was just hit with a failed part, and the turn around on failed product WILL result in serious loss in mining payouts. There is an advantage to going with Bitmain for mining hardware, however due to their support on hardware with issues, you need to factor in as serious losses in revenue .
Yeah I've accepted that I will probably never reach ROI, and its very frustrating/depressing watching your investment go from bad to worse. Bad to worse => to worser.... Got the blue screen of death.... S2 turns on but only getting a blank blue LCD display on the S2. I've re-imaged SD card but did nothing. Waiting for a Bitmain to reply for a RMA request. |
|
|
|
Did you ever get this figured out?
My S2 was working great for a week, had to power down to move some cables. Then when I turned it on, all I get is fans going and the blue screen. No connection to my network or anything.
Im having the exact same problem, Red lights on the BB Board and IO. LCD screen is blank. Tried to get Bitmain involved but they seem to disappear when it comes time for a resolution. Tried SD recover but it made no difference. I will post something if I find a resolution. |
|
|
|
OK the S2 now has been running for 16hrs and the (avg) has dropped down to 903gh/s. I've emailed Bitmain about getting a replacement but haven't heard back yet. Has anyone had any experience with Bitmain when it comes to warranty issues, or how supportive they are in resolving these types of issues?
Are you sure all blades working well?
As tzortz said above, are you sure all blades are working well? Do you see green lights flashing on all of them? You might just have a faulty board or 2. Try by taking them out: take one out, boot up and see if it runs at 900 Gh/s or 800Gh/s. If it runs at 800, then put that board back in and take out another one and try again... that way you can narrow it down to which boards are faulty and send those ones instead of sending the whole machine... that way you can still mine at 800-900 Gh/s while you wait. I emailed Bitmain about my faulty machine, it took 2 days to reply, but they sent all the necessary details to RMA, with postage at their cost. Thanks for the advice, I wasn't quite sure what to do but that is a pretty sound solution there. I was fearing that Bitmain would just ignore me and I'll be stuck with a faulty rig.  I'll post some results in a couple of days as it takes a few hours for the hashing speed to start falling. Test so far was restarting it about 6.5hrs ago and its already fallen down to 958.14(avg). Sounds like you might only have 1 board that's faulty, just pull them out one by one (obviously power down in-between) and wait till you see it stable at 900Gh/s, then the board that's out is faulty. Also check the boards carefully, one of mine was missing one of these little yellow pieces from between the chips and it still worked, but wasn't very stable. I just put it back in place and painted the ends with silver conductive paint and the board seems fine now: I left it running over night and check the speed in the morning, the speed reduced down to about 850(avg). I've removed a suspicious blade that was running about 15-20 degrees cooler than the others. Its only been running for about 15min so I'll have to wait for the results to come in, but at a glance the speeds is holding at approx 900GH(avg). If it maintains that speed after about 6 hours then I will remove another card and put it into the empty slot to determine if the fault is on the backplane or the blade.
This is an ongoing issue with Bitmain in general. I too was just hit with a failed part, and the turn around on failed product WILL result in serious loss in mining payouts. There is an advantage to going with Bitmain for mining hardware, however due to their support on hardware with issues, you need to factor in as serious losses in revenue .
Yeah I've accepted that I will probably never reach ROI, and its very frustrating/depressing watching your investment go from bad to worse. |
|
|
|
OK the S2 now has been running for 16hrs and the (avg) has dropped down to 903gh/s. I've emailed Bitmain about getting a replacement but haven't heard back yet. Has anyone had any experience with Bitmain when it comes to warranty issues, or how supportive they are in resolving these types of issues?
Are you sure all blades working well?
As tzortz said above, are you sure all blades are working well? Do you see green lights flashing on all of them? You might just have a faulty board or 2. Try by taking them out: take one out, boot up and see if it runs at 900 Gh/s or 800Gh/s. If it runs at 800, then put that board back in and take out another one and try again... that way you can narrow it down to which boards are faulty and send those ones instead of sending the whole machine... that way you can still mine at 800-900 Gh/s while you wait. I emailed Bitmain about my faulty machine, it took 2 days to reply, but they sent all the necessary details to RMA, with postage at their cost. Thanks for the advice, I wasn't quite sure what to do but that is a pretty sound solution there. I was fearing that Bitmain would just ignore me and I'll be stuck with a faulty rig. I'll post some results in a couple of days as it takes a few hours for the hashing speed to start falling. Test so far was restarting it about 6.5hrs ago and its already fallen down to 958.14(avg). |
|
|
|
I must have been one of the last purchasers from Batch 3, I feel a little hard done by when they announce a 4th batch $600 lessor in price when they hadn't even dispatched my order yet... Anyway moving along, I don't if this has been raised but I'm curious about the Quality Assurance standards are with Bitmain. I just received my S2 and its been running for 8hrs now and I've been monitoring it for the last couple of hours and the hash rate has been falling about 10gh an hour for the last 3 hours and its now sitting @ 935GH/S (avg). What this the tolerance of hitting the target? Because >-5% doesn't seem acceptable.
Could be temperature related. What are the temps on the 10 Chains? Theyre all sitting between 47-53 with the exception of one @ 31. OK the S2 now has been running for 16hrs and the (avg) has dropped down to 903gh/s. I've emailed Bitmain about getting a replacement but haven't heard back yet. Has anyone had any experience with Bitmain when it comes to warranty issues, or how supportive they are in resolving these types of issues? |
|
|
|
I must have been one of the last purchasers from Batch 3, I feel a little hard done by when they announce a 4th batch $600 lessor in price when they hadn't even dispatched my order yet... Anyway moving along, I don't if this has been raised but I'm curious about the Quality Assurance standards are with Bitmain. I just received my S2 and its been running for 8hrs now and I've been monitoring it for the last couple of hours and the hash rate has been falling about 10gh an hour for the last 3 hours and its now sitting @ 935GH/S (avg). What this the tolerance of hitting the target? Because >-5% doesn't seem acceptable.
Could be temperature related. What are the temps on the 10 Chains? Theyre all sitting between 47-53 with the exception of one @ 31. |
|
|
|
|
I must have been one of the last purchasers from Batch 3, I feel a little hard done by when they announce a 4th batch $600 lessor in price when they hadn't even dispatched my order yet... Anyway moving along, I don't if this has been raised but I'm curious about the Quality Assurance standards are with Bitmain. I just received my S2 and its been running for 8hrs now and I've been monitoring it for the last couple of hours and the hash rate has been falling about 10gh an hour for the last 3 hours and its now sitting @ 935GH/S (avg). What this the tolerance of hitting the target? Because >-5% doesn't seem acceptable.
|
|
|
|
|
