Productive night of troubleshooting... Thanks to everyone for all their pointers and advice in this thread.  Dayummm, that's sexy. I can get 520 Gh out of one, but I have a couple bad boards on the other and it can only get up to 422 Gh.  In the interest of full disclosure, that number is not my Bitfury gear exclusively. Have one rig running near 520 more-or-less stable, and another rig with 3 bad h-cards (2 DOA and 1 with a malfunctioning pot that won't volt above 0.127V and hashes at <2GHs) is stable at near 400. Have an RMA pending for the 3 bad cards after doing extensive testing last night. Will be doing more troubleshooting and tuning this weekend when I move the rigs out of their test environments. |
|
|
|
Productive night of troubleshooting... Thanks to everyone for all their pointers and advice in this thread. |
|
|
|
Did you adjust your Difficulty for the pool for one running at half on the pool?
The only pools I've tried... Eligius and Slush don't have adjustable difficulty I don't think. Maybe I should try one where I can.. Ghash.io is super spiffy that way, and btcguild is really good at automatically setting your diff to handle your hash rate, in my experience. |
|
|
|
|
Hope to do some troubleshooting of the second rig tonight after picking up some proper tools at Frys earlier.
Is it safe to assume that turning the pot all the way left should be most stable, and turn all the way to the right at your peril ?
Also, thanks Frys dude for selling me a Netgear WNDR3400v3 and stupid me trusting him that it works with Dd-wrt for use as a wireless bridge...
|
|
|
|
Is it ffa or team deathmatch?  Lopsided TDM staff vs Goat, but Goat is running a good pattern on the red armor, rail gun and quad damage, and owning pretty hard. I was just going to ask the score  9 to -4 favoring Goat, frag limit 15. Theymos is negative frags dying while attempting trick rocket jumps, and Raoul, davout and croppo were splash-damaged into lava as a result. |
|
|
|
Ok, message sent to Badbear.
Badbear don't care. |
|
|
|
Is it ffa or team deathmatch? Lopsided TDM staff vs Goat, but Goat is running a good pattern on the red armor, rail gun and quad damage, and owning pretty hard. |
|
|
|
try to run only test on bad hboad alone if hboard isnt working that meant bad.
Going to get the second rig up tonight and start testing. Need to hit Frys to pick up another beefy power supply and some micro-sized screwdrivers. Was playing musical h-cards last night, moving faster cards to the front and slower cards to the back, and got one rig running along near 440gh overnight with one card going to 0gh. Will probably ask Dave to order an additional MBoard. More troubleshooting tonight... Thanks for all the tips ! |
|
|
|
but putting in one night of work and calling it Bad is sortof shortsighted...
To be absolutely clear, I'm not calling anything bad. Just a bit surprised that we seem to collectively be having some trouble getting these v3 rigs humming along, stably. Eagerly awaiting updates and info on how to get our babies nice and happy. |
|
|
|
After spending several hours trying random things suggested all over, I've still had no luck. One rig starts off good at about 450 Gh, but slowly goes down to 250-350 Gh. I have to hit start/stop every 5 minutes to keep it above 400 Gh. I am now switching out H cards in different slots to try and see if I can come up with a card configuration that will run more stable. I read putting bad cards in the last slot of every bank helps.
Ditto here; seeing the exact same thing  Have to keep restarting it every 5 minutes to maintain hash-rate. I tried swapping all sorts of combos of H-Cards in different slots with no discernible effect. I feel your pain, bro. |
|
|
|
I'm done troubleshooting for the evening Shot a "Product Return" email to the MBP folks detailing the issues I've had this evening and hope to get a response about how to proceed. - Received 32 H-Cards and 2 M-Boards. - Identified 2 H-Cards as DOA - M-Board that I thought was DOA I got hashing after further troubleshooting - Consistent behavior with slots 2 and 3 across both M-Boards throttling down towards 0 (with slots 6 and 8 following shortly after) - As per the Mining Support thread, I created a best.cnf with aIfDSo 53 set for all 256 entries -- No difference. Boards eventually throttle to 0 and never recover Help |
|
|
|
reading the last few pages makes me feel not so bad.  I'm happy for you, HashFast shill. |
|
|
|
Ah ha! Now I know why random cards have dropped out. It's always happened when I've moved a fan or slightly adjusted the position of the M board, etc.
Sometimes I could get them in the right position and they'd run for hours and then randomly crap out. Here was my fix (just cut slits with a miter saw): https://i.imgur.com/SfpNAa2l.jpg That is madness. I've removed the fans that were blowing on them, causing any movement, and hooked up fans onto the headers, and have fans resting on top of the H-Cards, blowing down and giving them more support... in theory... Cards in the same few slots still creeping towards 0. Looking for some guidance from Dave and crew, 'cause something isn't right with this batch EDIT: I give up... speed:13568 noncerate[GH/s]:136.723 (0.534/chip) hashrate[GH/s]:144.709 good:9550 errors:462 spi-err:3 miso-err:0 duplicates:0 jobs:289 cores:16% good:256 bad:0 off:0 (best[GH/s]:0.000) Tue Nov 12 03:18:20 2013
board-2 speed nrate hrate good errors spi-err miso-er duplic good bad off per chip good cores
0: 848 34.847 36.021 2434 50 1 0 0 16 0 0 (2.178/chip) 32%
1: 848 0.000 0.000 0 0 0 0 0 16 0 0 (0.000/chip) 7% speed down
2: 848 0.000 0.000 0 0 0 0 0 16 0 0 (0.000/chip) 8%
3: 848 0.000 0.000 0 0 0 0 0 16 0 0 (0.000/chip) 13%
4: 848 0.000 0.000 0 0 0 0 0 16 0 0 (0.000/chip) 9%
5: 848 31.955 34.394 2232 140 0 0 0 16 0 0 (1.997/chip) 31%
6: 848 35.262 37.438 2463 135 0 0 0 16 0 0 (2.204/chip) 33%
7: 848 0.000 0.000 0 0 0 0 0 16 0 0 (0.000/chip) 6%
8: 848 34.660 36.856 2421 137 2 0 0 16 0 0 (2.166/chip) 32%
9: 848 0.000 0.000 0 0 0 0 0 16 0 0 (0.000/chip) 15%
A: 848 0.000 0.000 0 0 0 0 0 16 0 0 (0.000/chip) 12%
B: 848 0.000 0.000 0 0 0 0 0 16 0 0 (0.000/chip) 17%
C: 848 0.000 0.000 0 0 0 0 0 16 0 0 (0.000/chip) 14%
D: 848 0.000 0.000 0 0 0 0 0 16 0 0 (0.000/chip) 13%
E: 848 0.000 0.000 0 0 0 0 0 16 0 0 (0.000/chip) 7%
F: 848 0.000 0.000 0 0 0 0 0 16 0 0 (0.000/chip) 13%
|
|
|
|
Something definitely seems amiss with these kits. I received 32 H-Cards, and 2 M-Boards. 1 M-Board is DOA and have filled an RMA request with MBP. I've swapped out several H-Cards in slots that had their hash-rate go from full to zero, and even new sealed H-Cards start slowing down and approach 0 GHs in the same slots. Best I can tell, at least 2 H-Cards are completely DOA, and having sad-times getting a full M-Board hashing steady above 500. Fuck Will let it run for a few hours and see how things look a bit later... EDIT: Well, that went to zero quickly... Fuck. Eg: Swapped slot 1 and 2 for new H-Cards... speed:13568 noncerate[GH/s]:351.042 (1.371/chip) hashrate[GH/s]:367.538 good:24520 errors:8994 spi-err:60 miso-err:125 duplicates:111 jobs:262 cores:24% good:256 bad:0 off:0 (best[GH/s]:0.000) Tue Nov 12 02:52:05 2013
board-2 speed nrate hrate good errors spi-err miso-er duplic good bad off per chip good cores
0: 848 34.245 35.863 2392 120 0 0 0 16 0 0 (2.140/chip) 31%
1: 848 0.000 0.000 0 0 0 0 0 16 0 0 (0.000/chip) 8% speed down
2: 848 0.000 0.000 0 0 0 0 0 16 0 0 (0.000/chip) 8%
3: 848 35.391 36.687 2472 3 1 0 0 16 0 0 (2.212/chip) 33%
4: 848 0.000 0.000 0 0 0 0 0 16 0 0 (0.000/chip) 13%
5: 848 32.556 34.499 2274 124 0 0 0 16 0 0 (2.035/chip) 31%
6: 848 34.961 37.417 2442 138 1 0 0 16 0 0 (2.185/chip) 32%
7: 848 0.000 0.000 0 0 0 0 0 16 0 0 (0.000/chip) 10%
8: 848 34.145 36.846 2385 124 0 0 0 16 0 0 (2.134/chip) 31%
9: 848 34.474 35.937 2408 67 1 0 0 16 0 0 (2.155/chip) 32%
A: 848 35.290 36.613 2465 47 1 0 0 16 0 0 (2.206/chip) 33%
B: 848 37.767 36.656 2638 9 2 0 0 16 0 0 (2.360/chip) 34%
C: 848 34.832 35.683 2433 14 0 0 0 16 0 0 (2.177/chip) 33%
D: 848 35.691 36.201 2493 3 0 0 0 16 0 0 (2.231/chip) 33%
E: 848 0.000 0.803 0 7788 0 0 6 16 0 0 (0.000/chip) 11%
F: 848 1.689 4.334 118 557 54 125 105 16 0 0 (0.106/chip) 7% |
|
|
|
Good job to the dumbass misguided helper who chose the smaller than atomic particle Potentiometers (something just a little bit bigger that wouldve been easier to catch with a screwdriver would have made all the difference to me) that are too small for anything. Smallest screwdriver I could find in frys barely seems to catch them most of the time. Extremely frustrating when trying to undervolt the cards for the sake of keeping them on.
No kidding Having a helluva time with the smallest screwdriver I could find from Fry's... Not even sure if I'm getting any movement. |
|
|
|
What's the login and the password?
user: pi pass: raspberry |
|
|
|
Xian, turn down the voltage by turning the trimpots to the left on those cards
I'll try that. Thanks ! |
|
|
|
Your errors overkill more than 50% and if you are not going to run 850W with 2 full kits.
Swapped out the PSU for a Corsair AX1200. Chainminer runs fine for a little bit, then a few boards start dropping down to 0GH/s. BFGMiner is a fail spamming all sorts of nastiness. *sigh* Very frustrating These guys are finicky Have some big-ass fans keeping them cool, so I can't imagine they are overheating Room is 76C. Below you can see the few boards that are starting to reach 0GH after starting strong. speed:13568 noncerate[GH/s]:452.817 (1.769/chip) hashrate[GH/s]:478.766 good:25514 errors:3816 spi-err:8 miso-err:10 duplicates:505 jobs:230 cores:12% good:256 bad:0 off:0 (best[GH/s]:0.000) Tue Nov 12 01:47:09 2013
board-2 speed nrate hrate good errors spi-err miso-er duplic good bad off per chip good cores
0: 848 33.987 35.587 1915 35 0 1 0 16 0 0 (2.124/chip) 15%
1: 848 10.737 10.941 605 352 0 2 25 16 0 0 (0.671/chip) 5%
2: 848 12.051 14.112 679 139 0 1 16 16 0 0 (0.753/chip) 5%
3: 848 35.212 36.216 1984 220 2 0 39 16 0 0 (2.201/chip) 15%
4: 848 19.398 19.969 1093 255 0 2 77 16 0 0 (1.212/chip) 9%
5: 848 31.343 33.884 1766 100 0 0 2 16 0 0 (1.959/chip) 13%
6: 848 32.745 36.754 1845 128 0 0 1 16 0 0 (2.047/chip) 14%
7: 848 19.540 19.864 1101 327 0 1 55 16 0 0 (1.221/chip) 9%
8: 848 34.395 36.531 1938 119 0 0 0 16 0 0 (2.150/chip) 15%
9: 848 33.827 35.627 1906 43 1 0 0 16 0 0 (2.114/chip) 15%
A: 848 34.697 36.334 1955 50 1 0 0 16 0 0 (2.169/chip) 15%
B: 848 35.229 36.334 1985 4 0 0 0 16 0 0 (2.202/chip) 15%
C: 848 34.910 35.456 1967 13 1 0 0 16 0 0 (2.182/chip) 15%
D: 848 31.343 33.674 1766 905 1 1 177 16 0 0 (1.959/chip) 14%
E: 848 32.017 35.365 1804 148 1 0 0 16 0 0 (2.001/chip) 14%
F: 848 21.386 22.118 1205 978 1 2 113 16 0 0 (1.337/chip) 10% |
|
|
|
How I can take output log like this one ?
If it's running, then; cat /run/shm/.stat.log Looks like my second M-board no workie. Fuck. Troubleshooting continues... |
|
|
|
|
Show Posts
