 Show Posts
|
|
Pages: [1]
|
I received my Chain 3 back from warranty. It's been 72 Hours running and so far, so good.
Hi there, how do you managed this? Did you only send the defect asic board or the whole miner? And how did you send it to them? I have first board defect, board is know by the system but no asic’s in the kernel log. Cheers... With mine (after so much troubleshooting w/ Bitmain) it finally had 5-6 ASICs just totally dissapear on chain 3. I filled out a warranty ticket, then I just removed the chain 3 has board by itself, wrapped it in antistatic foam (you could probably just do bubble wrap) and mailed it to the warranty dept. About a week later a new hash board was mailed to me. It was my first issue and hard for me to figure out from the site. So I just went by this on the shipping and warranty repair process from Bitmain: https://shop.bitmain.com/workOrderGuide.htm Hope it helps. |
|
|
|
|
I received my Chain 3 back from warranty. It's been 72 Hours running and so far, so good.
|
|
|
|
Wow. Same symptoms. I hope to have something in from the Warranty Dept. soon regarding these disappearing ASICs. Will post what they say. Yes, I do have the Nov 02. Uploaded to uploadfile.io - https://ufile.io/2sah6 Hopefully maintains integrity. Let us know if this solves anything. |
|
|
|
|
Aye yes, I just opened one. Shipping this out tomorrow or Monday. I'm guessing it's alright to run/mine with the remaining two boards.
|
|
|
|
|
I've been experiencing firmware issues from the start. Mine was the October Batch. New Years Day Chain 3 seemed to go out. But not completely, it shows 54 of the 60 ASICs on the board. The other 6 ASICs are not there. Not represented as an X/O or even -.
|
|
|
|
I Changed mine to 437 then 444m. Hasn't voided warranty in dealing with them. I had to. It was completely unusable at the "default frequency". They are not great on backing their product warranty, because on diagnosing, two boards had HW errors but oddly when all 3 run there are absolutely 0 HW errors, but it still goes all X in 3 - 4 days, and I have to reboot. I feel like they are dragging the warranty period out, by persistently telling me, "Unless the boards run seperately and X out, I can only return, and I can only return 1 hash board". Makes no sense, not a warranty.
My rant. But I think as long as the frequency is lowered, not raised, then it should not void any warranty. They made them completely inoperable at their default frequency. I would open a repair ticket with them first though. Typical Bitmain.
I have 4 tickets open and they haven't responded to a single one. Lol So should I assume that chain #2 is done for since it doesn't even show the X's and O's? I've also noticed that the third pool doesn't register any pool? I've tried mining pool hub and nice hash and both come up as dead? 4 Tickets and no response? Yikes. On mine they take 24-48 hours. I'm not in anyway remotely an authority or experienced enough on these diagnostics, but if chain 2 is not showing X or O, I would "guess" controller board? So many issues with the D3's and I feel (have a hunch maybe?) that there are big-time firmware issues globally. I'm curious to hear if others are experiencing, would love hear the issues and what they've done in diagnosing and troubleshooting this. After 2 days running on a D3 with issues, Chain 1 just went entirely X'd. Before 4 days all chains X'd. And prior to that Chain 2 showed 3 ASICs X'd. This is puzzling and driving me bonkers. I feel like I need to diagnose each board for 2-4 days now each to see. Is that practical? What is strange to me are the temps and the fan (Chain 1 and 2 running solo/individually, the fan goes to 6k, 3 only at 4k). Temp on chain 3 solo gets gets to 77c (Scary) and yet when all run at once the fan is at 4k (Temps run: C1: 69c, C2: 63c, and C3: 70-71c). Chain 3 solo show HW errors but all three running show absolutely 0 HW errors. It's very odd. I'm lost. I'm thinking firmware? And maybe Bitmain is swamped with these issues. We, or at least the large majority of the mining community, have financed them to a monopoly and likely funded their new Sophon AI brand. I think we all just need to persist on reporting these issues, and keep opening tickets. They need to back their products. I'm not expert either - BUT I have updates for everyone. So - Chain 2 (3rd ASIC) X'd out completely a few days ago. Today everything is back to normal. These are the steps I took. Once Chain 2 X'd out - I updated the firmware to the one posted in here from amazonaws - I flashed it to the D3 and then let it run on the remaining Chains with all the problems errors on the log. VERY IMPORTANT SETTING CHANGE: In Miner Configuration > Advanced Settings > Frequency - I changed this from Default to 444M - I believe this is what fixed a lot of it along with the firmware update (reboots are only for the socket errors to go away and for it to get adjusted to the new firmware update) Ran it for a total of 2 days and 12 hours Today when I came in - I rebooted through the IP address - then a socket error showed - rebooted through the IP address 2 more times and then I went back and unplugged the machine manually. Plugged it back in and rebooted through the IP address once more. After that all the Chains were back to normal and the machine is running at 16/mhs steadily. It even gave me the error that the temp reading is off and to reboot the PIC's I have a sever suspicion that the readings on the backend are NOT accurate. Temperature and Chain readings could be off because of their firmware. It does not make sense for an ASIC to X out completely and then all of a sudden come back. If it X's out that means the controller is bad and needs to be replaced - but that means that it can't come back from the dead either. A false positive. So that leaves only the option that the firmware is bad and cannot get accurate readings of the machine as it is running. This is what I am seeing to be in my case. People might be screwing their machine more by acting on these readings and breaking something that didn't need fixing. Almost like we got D3's from the same batch. Problems are similar. I received a response, cleared to open and check the boards, saying a PCB board (Chain 3) was too high (showed 244c  ) last time all X'd out. So running on 444m, latest firmware from the last AWS link. it still bugs out. I don't think examining the boards for loose heat sinks, blown or unsoldered caps, etc is really going to solve anything. I think your right, the frequency is an issue and I personally suspect the backend readings are bad too, maybe from the firmware. I figure I'll give it a shot though. |
|
|
|
|
Bump. Ditto. Is Oregon Mines still hosting?
|
|
|
|
I Changed mine to 437 then 444m. Hasn't voided warranty in dealing with them. I had to. It was completely unusable at the "default frequency". They are not great on backing their product warranty, because on diagnosing, two boards had HW errors but oddly when all 3 run there are absolutely 0 HW errors, but it still goes all X in 3 - 4 days, and I have to reboot. I feel like they are dragging the warranty period out, by persistently telling me, "Unless the boards run seperately and X out, I can only return, and I can only return 1 hash board". Makes no sense, not a warranty.
My rant. But I think as long as the frequency is lowered, not raised, then it should not void any warranty. They made them completely inoperable at their default frequency. I would open a repair ticket with them first though. Typical Bitmain.
I have 4 tickets open and they haven't responded to a single one. Lol So should I assume that chain #2 is done for since it doesn't even show the X's and O's? I've also noticed that the third pool doesn't register any pool? I've tried mining pool hub and nice hash and both come up as dead? 4 Tickets and no response? Yikes. On mine they take 24-48 hours. I'm not in anyway remotely an authority or experienced enough on these diagnostics, but if chain 2 is not showing X or O, I would "guess" controller board? So many issues with the D3's and I feel (have a hunch maybe?) that there are big-time firmware issues globally. I'm curious to hear if others are experiencing, would love hear the issues and what they've done in diagnosing and troubleshooting this. After 2 days running on a D3 with issues, Chain 1 just went entirely X'd. Before 4 days all chains X'd. And prior to that Chain 2 showed 3 ASICs X'd. This is puzzling and driving me bonkers. I feel like I need to diagnose each board for 2-4 days now each to see. Is that practical? What is strange to me are the temps and the fan (Chain 1 and 2 running solo/individually, the fan goes to 6k, 3 only at 4k). Temp on chain 3 solo gets gets to 77c (Scary) and yet when all run at once the fan is at 4k (Temps run: C1: 69c, C2: 63c, and C3: 70-71c). Chain 3 solo show HW errors but all three running show absolutely 0 HW errors. It's very odd. I'm lost. I'm thinking firmware? And maybe Bitmain is swamped with these issues. We, or at least the large majority of the mining community, have financed them to a monopoly and likely funded their new Sophon AI brand. I think we all just need to persist on reporting these issues, and keep opening tickets. They need to back their products. |
|
|
|
|
I Changed mine to 437 then 444m. Hasn't voided warranty in dealing with them. I had to. It was completely unusable at the "default frequency". They are not great on backing their product warranty, because on diagnosing, two boards had HW errors but oddly when all 3 run there are absolutely 0 HW errors, but it still goes all X in 3 - 4 days, and I have to reboot. I feel like they are dragging the warranty period out, by persistently telling me, "Unless the boards run seperately and X out, I can only return, and I can only return 1 hash board". Makes no sense, not a warranty.
My rant. But I think as long as the frequency is lowered, not raised, then it should not void any warranty. They made them completely inoperable at their default frequency. I would open a repair ticket with them first though. Typical Bitmain.
|
|
|
|
Dear Gigawatt investors,
Like yourself I invested in the Gigawatt project believing the developers, I am aware how risky the crypto space is...
Gigawatt is an American company though and there are some countermeasures we can take as customers.
Some of you agree that gigawatt made falls claims about timeline. Excuse was unforeseen trouble although they advertise that they do this for years. After taking our money and knowing they are delays, they kept selling miners they could not deploy as advertised, second mistake.
The customer service is terrible. No updates no answers to emails, third mistake.
I believe we should do what is our right and spread the word... I ask you, and I was censored on their Telegram Chanel for this (and this from people who are in the cryptospace), but go out and spread the word:
Go on Facebook, twitter anywhere, write what happened:
1. Gigs-Watt is not reliable
2. They make false promises
3. They have a terrible customer service
Many of us will not make a cent because of the lies of gigawatt, let's save others
Before some fanboy defends them: gigawatt took a lot of money and did not deliver. On their mane internet page even after the known delays, they lied and ignored us. Time for payback. Because customers are always right! Censoring people on Telegram, claiming you believe in crypto and what it stands for shame on you!!!
This is what I'm talking about on my previous post on this thread which we should really be careful on these kind of things because theres always been a shady part on these kind of investments. Seeing on your situation,i presumed that you did put investment on that one,right? If you did then for sure its a sure loss and this would really be lesson for you and no matter how you do spread their shady behavior you cant take your money back for sure. Yes I do spread, Giga-Watt is one crypto investment. But yes again, it is better to invest in coins directly... I do not believe company is total fraud. They actually are building something. But they are acting unprofessional, and I fear this project is not going to last, so yes again, it is very likely I want even see ROI... For people interested in investing in this project (I still believe the concept is good), I would wait until the dust settles and they proof they can manage their business. They are still selling miners on their site, even though some people waiting for orders from July 2017... I think in January 2018 more will be clear P.S. Update on situation. They are still not ready and adding delays withPods. They charge you for 1200W on D3 miner with 15 000Mh/S although people who got their miners back from Giga-Watt and are mining at home say they get much better statistics... The D3 can do better than that, and Giga-Watt insists it is the D3 software that is faulty, Giga-Watt doesn't´t tune (so much for them being experts on mining...). So yet again they manage to take care of themselves.. The guy on their Telegram Chanel said to customers today: "stop acting like child for not getting your toys" Some people invested hundreds of thousands... This is so unprofessional and disgusting. And Dave Carlson? He laughs all the way to the bank. Nice person I was not on the ICO, I missed it, but kinda glad I did. I e-mailed them asking when pods would be available for non token holders. They said Dec to late Dec. and were fairly friendly. Then I checked in on them and asked if they would have any of the S9 Late Jan batches available to buy, so it could go straight into a pod. A bit harsh response (kind of rude/cocky), still no reply on the purchase inquiry. Would have wanted to get from them for the space, but now will just get from Bitmain. Feel sorry for the token holders. They don't project manage well. That's what I do. I don't think they anticipated the permits and inspections. That can be a real problem. They are running late on their own token holders, so I will have to look elsewhere in the US for a Hosting location with credibility. Have 3-5 in between now and January that need to be hosted. It seemed like it started well enough, but I guess time will tell. In the meantime, anyone know of a thread for hosting facility reviews, I would appreciate it (forum's search feature down). |
|
|
|
New Firmware released Nov 20. Specifically to fix this issue. I'll flash and test over the holidays & report whether any success.
And...No. It lasted 4 1/2 days before it X'd out again. 5 a.m. woke to fan speed at max, all basics out. I keep updating the firmware and running the dials on each chain, just results in chains 1 & 2 with oddly no HW errors, (and fan at 6k), chain 3 runs very hot with a lot of errors. I would think chain 3, or controller board. Bitmain just says unless the ASIC's X out, can't send create a warranty claim, nor will they take the entire miner back for warranty diags. So I'll try the cable unplug/reset next. And maybe I'll ramp up the frequency and diagnose the boards for much longer than the requested "20 Minutes". |
|
|
|
|
New Firmware released Nov 20. Specifically to fix this issue. I'll flash and test over the holidays & report whether any success.
|
|
|
|
|
Same problem, same issue. The last time, All ASICS went out. Same responses from Bitmain. Flashed the firmware twice. Worked for about 3 days fine. Still thinking, probably right, a bug or controller board. Maybe the firmware update didn't fix all. Maybe I do have a bad Hash or controller board. It's weird. Interested in hearing from others who've flashed the firmware but still experience.
|
|
|
|
So, I've read an article  And it says Bitcoin Cash is "more profitable" to mine a.t.m. than BTC. Curious to hear opinions on that. Also I've been looking for a Bitcoin Cash Pool recommendation. Tried bitcoin.pool, which initialy supported BCH mining, but I'm unsure as to whether it was down, it didn't reflect hash rate and stats well. Sorry if this is out of context. |
|
|
|
|
Awesome. Thanks, it's reassuring. When I had him look at the specs I was expecting him to say to up the gauge and the amp of the breakers. He basically said that the amperage draw would benefit from being on an isolated circuit each. I ended up getting one "6-20P to C13" cable rated 15 amps, but I will probably go ahead and pick up the 6-15 to IEC C13. Looking at possible surge protectors (the international type that support that C20 - C15 socket) and I'm just not sure whether it's a good idea or not.
I really appreciate it. After reading so much on the S9's and 220v I was unsure of the reliabilty or safety of single miners on single circuits.
|
|
|
|
|
Well, this looks like the thread to post for my issue. I really need some advice regarding... yes the 110-220v issue in the US. I’m moving from old SP20E’s to a single S9 and a single L3+ Antminer, both each with dedicated “Bitmain” AW3++ PSU’s (this batch shipping in August). I’ve gotten by on the SP’s but now I’d like to upgrade and learn a bit more.
I’ll do very low voltage no problem, but I don’t want to play with fire (literally) with higher voltages. I’m not an electrician.
I have a buddy/friend of the family electrician who came over, and I showed him the PSU specs from Bitmain’s site. We ran two separate 14 – 2 gauge wires to the server room. One for each miner only. He put each on it’s own 15 amp breaker, so one miner per circuit. The receptacle is a NEMA 6 – 20? It’s the one with the ground and the top two are horizontal (w/ the left socket optionally vertical).
So my concern is whether running Bitman’s AW3++ PSU on 15 amp breaker w/ 14 gauge is optimal. Mostly for safety. I can easily re-run this with 12 gauge, but will have him change the outlets and breakers if need be. Would really appreciate any advice regarding this. Also, any recommendations as to a surge protector and if I should stay with this configuration, any power cord recommendations to the AW3++ ?
Thank you.
|
|
|
|
|
