---

I swapped SM0 and SM2 (the rightmost and the leftmost) and the problem moved to SM2. So unfortunately it's a hash board problem.

I've got a repair ticket from Pangolin. I'm going to send the bad hash board to be repaired.

Any recommendations for a shipping company to China?

Thanks so much for your offer to help Phil. But before you go to a lot of trouble, maybe I should do one more swap test.

If you remember what I did was swap 0 and 1. So as you look at the the miner from the front (i.e. the air intake side), I went from this:

S0  S1  S2
H0  H1  H2

To this:

S0  S1  S2
H1  H0  H2

This was based on the assumption that the slots are numbered from left to right. If I had any brains at the time, I would have rotated them entirely, moving every hash board like so:

S0  S1  S2
H2  H0  H1

This way all of the boards would have moved a slot and I wouldn't have to know which one is actually S0. If after that S0 is still bad, then clearly it's the data bridge, cable or (yikes) the controller.

Maybe I should still do this just to be on the safe side. At this stage I just have to swap the two outer hash boards to achieve the same effect as rotating.

Since the miner as running at a data center, I won't be able to try this until early this coming week.

In the meantime at least I'm running on two hash boards, which is better than nothing.

So I finally got around to swapping out the data bridge card. It took a while to get the replacements because I made the mistake of trying to communicate with them via their support system.

In case it wasn't clear, the only way you can get support is via Telegram. I should have paid attention to Phil's post about that, but I didn't have Telegram and didn't want to install it. Learn from my mistake and just use Telegram.

Anyway, I swapped out multiple new bridge data cards because they sent me several. But none of them made a difference.

But since I originally swapped hash boards and the problem stayed with the slot, not the hash board, I'm still convinced this is a data problem.

Perhaps my ribbon cable is bad? It could also be the controller, I suppose. But replacing the cable would be the first thing that I try.

Anyone know a source for replacement cable? I don't have one in my junk pile. Too bad those extra S9 data cables I have aren't 2 x 11.

Also, Phil you were asking me to snag you an extra data bridge card. I've got extras so I can do that, but it might be better to figure out where the fault really is before I send you a card that isn't tested.

Ok, I will. Maybe I'll get an extra one too.

Yes, I'm in the US. Just on the opposite coast.

Thanks Phil. That's very helpful info.

Looks like I have the same problem as you.

I swapped the SM0 and SM1 hash boards. While I was in there I added a couple of thin nylon washers under the bridge on the chance that it might prevent a short.

When I brought the miner up, the problem stayed with the SM0 slot.

Since the problem is following the slot, not the hash board, I think I have a bad bridge.

Seems like this is a common problem. They should consider reworking their data connection design. What was wrong with cables, after all?

Other than this bridge problem, the build quality seems really nice. I was impressed, especially with those beefy power bus connections.

Looks like I need to ask pangolinminer.com support for a replacement bridge. Better than a hash board, I guess.

Maybe. But I won't have physical access to the miner till later today.

Just trying to plan out the repair effort.

Thanks Phil. I'll take a look.

In the meantime the M10 has at least brought up the remaining two boards, so it's not completely dead in the water. I guess that's something.

---

Dumb question: what is the order of the board layout?

My bad board is SM0. When looking at the miner from the front, is that the leftmost or rightmost board?

I assume it's not in the middle ;-)

Well it looks like I lost a hash board this morning. I got warnings from the pool, then looked and SM0 was registering 0 frequency.

This event is visible from the mining status page:


I've rebooted it and it seems to be in a mode where CGMiner keeps restarting. It the elapsed time never goes above 1 second.

So now SM0 shows zero effective chips while SM1 and SM2 show 105 chips. But none of the boards are hashing.

Next I power cycled it via PDU (I'm not onsite). It's still in the same state. Namely SM0 seems dead and all mining has stopped.

Any ideas what to do next?

Yeah I hope you're right. I got lost interest in hobby level mining in mid-2017 because I was fed up with Bitmain. Figured I'd just let my S9's and L3+ just run into the sunset, slowly dying one hash board at a time.

But I'm really impressed with MicroBT. I'm glad I managed to grab an M10, even if I was late to the party (should have been paying more attention and pulled the trigger earlier).

Hopefully Pangolin realizes the value proposition of being a community vetted, trusted, attractive alternative to Bitmain.

This is a cut and dried warranty problem. All you did was prove that sarcheer's problem was the PSU.

Replacing the PSU (which is the right thing to do) seems like an inexpensive way for them to cement their trust with this community. It's a no-brainer really.

I agree. This might be anecdotal, but I'm running my M10 on 208 volts and it's been consistently hashing at the expected rate since I installed it a week ago.

Very nice of Phil to help you out. I hope it works.

Thanks for looking. I've got the same firmware version. Nice to know that I'm not crazy.

Thanks. I did look there first.

I feel like an idiot, but I can't find a link or button on any page that leads to the admin page. I've tried two different browsers (Safari and Firefox).

Note that your instructions say that the login credentials are root/root. When I got my M10, it defaults to a user name of admin. I ended up guessing that the password was also admin. That was the only way that I could get in.

When I try entering root/root, it gives me an "Invalid username and/or password" error. I can only log in via admin/admin.

If there are separate root and admin users, then perhaps the fact that I can only login as admin means that I have reduced privileges. That might explain why I can't see the admin page. This assumes that the web GUI is different for different privileges, which is just a guess on my part.

Anyway, this machine is behind a firewall in a locked rack in a secure data center with no WiFi access. While I prefer to change the default password, it's unlikely to be a real security issue. So maybe I shouldn't stress over the password.

I ordered on Sunday and had the miner in hand by noon on Wednesday. I installed it Wednesday afternoon. It all went well and the miner has been running with stable temps and a hash rate of 31.2 TH/s.

Very impressed with both pangolinminer.com and the M10!

Looks like they've cleared out their stock of the M10, because it's not visible on their shop any more. Now they're offering the M20, which is 48 or 58 Th/s, shipping by May 15.

One thing I noticed about the M10 is it runs really hot. I expected that because all those watts have to go somewhere. But it pumps out hot air like crazy, and the metal sides towards the exhaust end are very hot to the touch. Too bad I didn't have my Raytek with me to take a measurement.

Originally I was thinking about 3d printing a 120mm to 4 inch hose adaptor so that I can direct the heat out of the rack more effectively. But now I'm worried that the amount of heat might warp the PLA plastic. I guess I could try PETG, which can handle higher temps.

One question: how do you change the default password on the M10?

I tried to download the manual from microbt.com, but it seems to be corrupted or it can't be downloaded correctly and won't open. The manuals on pangolinminer.com are for an older model.

Thanks Phil! Hope you’re doing well.

The one I was looking at is 12 guage, so it should be fine.

Long time no post. I've been quietly mining for the last several years on a pair of S9s and an L3+, powered by a pair of IBM 2880 PSUs.

Things are changing at our data center and we need some space. I figured I might as well upgrade at the same time. So I ordered an M10 and will be retiring the ancient miners.

I'm planning on running the M10 on 208 volts. I verified with the manufacturer that it's supposed to handle 200 - 240, so it should be fine.

Based on the original post, it looks like the PSU takes a C13 connector. I want to connect this to a C19 socket on our PDU. So I'm thinking about getting a 15 amp rated C13 to C20 cable.

That should be hefty enough right?

I'm seeing the same behavior with my miners at a data center on the west coast. It's very annoying. Woke up to a ton of alert emails this morning.

The URL I'm using is: stratum+tcp://us-east.stratum.slushpool.com:3333

Obviously this is affecting a number of us. Either they're wrong and there is a problem on their end, or maybe some sort of general routing problem between us and them.

So one of my sticks is in first place, which is great. But the other one is MIA, which is not so great.

Maybe the invisible one should sneak off and earn some dust on a non-solo pool. At $8k+ a bitcoin it might be worth it.

As others have mentioned, my miners are no longer listed. Nothing has changed on my end. My miners are still mining on the solo pool.

I've sent you a PM.

Yes.