how much you want for these 150 extra Cointerra Terraminer IV units?
Do they still hash, im looking to create an old vintage mining garage for the kicks of it (must hash though)
Let me know
Topic: Cointerra Terraminer IV Unboxing and Setup (Read 19182 times)
If you can find somebody that will buy them, I've got 150 more for him.
i know bitcoin is asic or whatever but i know theres some newer altcoins that are on the same like algorithum or whatever bitcoin was. IS there anyone good currencies yall would recommend 4 mining with a used one of these from a couple years ago. Or should i just sell it?
The efficiency is just not there. Sell it.
i know bitcoin is asic or whatever but i know theres some newer altcoins that are on the same like algorithum or whatever bitcoin was. IS there anyone good currencies yall would recommend 4 mining with a used one of these from a couple years ago. Or should i just sell it?
how mach this machine and from wher can i order and how many bitcoin i get per month and what the propitiates use in lap to good support to this machin
However, just switched to P2Pool, and hash has dropped to around 1.2TH. Any special config options I need to look at? Rejects are reasonable... ~4.5%...
The newest firmware (0.7.6) has poor p2pool performance for some reason. I have not yet heard an explanation, but there are a few confirmed reports of this issue. Mining on big pools (e.g. Eligius) works fine. If you want to mine on p2pool, downgrade to 0.6.48.
it's also AWESOME on p2pool, lowest stale rate I've seen from any mining hardware.
We've only just received our unit... March batch so at least it arrived in March. Started mining on Eligius, was getting arounf 1.6TH out of the box, so not too bad considering. However, just switched to P2Pool, and hash has dropped to around 1.2TH. Any special config options I need to look at? Rejects are reasonable... ~4.5%...
... and one is at 113C.
That's mental, something is wrong. Only mil-spec or special analog chips are designed to operate that high. Someone didn't put your waterblock on right, the temperature sensor is wrong, or it skipped QA altogether. I'm not saying you're wrong, I'm just worried for your sake.
It is more than one. If I could open the machine, I expect I could fix it. I cannot without voiding the warranty. I will RMA, but it is hashing well. Some have one board at 60-70C and the other at these temps. Likely bad pumps which is strange since the waterblock company surely does not have this kind of reject rate. Or a pinched tube etc.
... and one is at 113C.
That's mental, something is wrong. Only mil-spec or special analog chips are designed to operate that high. Someone didn't put your waterblock on right, the temperature sensor is wrong, or it skipped QA altogether. I'm not saying you're wrong, I'm just worried for your sake.
It has the ventilation hole but no fan to circulate the air.
The power supply has a fan, it's just not visible. It *does* ventilate the air though rather poorly (the pictured end is the exhaust). The PSU is rated for something like 105C, so I wouldn't worry too much about *it* getting hot. Although some heat is radiated from the PSU to the heat exchangers / water radiators, it isn't a huge deal. If your cores are hitting 95C (the safety cutoff) than your ambient air temperature is too high, or your air circulation is poor.
There is a lot of variability in performance and temp among the units. I am pumping 50F air into the machines right now and some chips are at 60C and one is at 113C. Some chips within the same unit have a spread of 30C so I would not assume his problem is just his ambient air/airflow
It has the ventilation hole but no fan to circulate the air.
The power supply has a fan, it's just not visible. It *does* ventilate the air though rather poorly (the pictured end is the exhaust). The PSU is rated for something like 105C, so I wouldn't worry too much about *it* getting hot. Although some heat is radiated from the PSU to the heat exchangers / water radiators, it isn't a huge deal. If your cores are hitting 95C (the safety cutoff) than your ambient air temperature is too high, or your air circulation is poor.
So, when CTA0 shuts down and CTA1 is still mining how do I reboot the miner? Just reboot CGMiner in the web interface? Have you figured this out yet?
The fans really blow the heat a long way don't they?
I'm not sure when you would ever encounter this scenario, they basically mine as one unit, you don't direct one board to one pool or anything like that, all the hashrate is directed at whatever pool you point it at. You can SSH in and reboot it that way and it seems to reboot everything.The fans really blow the heat a long way don't they?
I had this exact scenario this morning. Woke up to CTA0 offline, but CTA1 still going strong. I ssh'd into the unit and rebooted it, which seemws to bring everything back online (for now).
It happened whit me as well. I think my case is that the board that is next to the Power Source heats more.
I had to open my box to cool the terminal in the power source.
It has the ventilation hole but no fan to circulate the air. So the miner heats more and wen it gets to 95ºC it throttle down the miner.
CoreTemp2 is the one that gets to 95ºC
EDIT: Was probing the Terraminer and found the FTP port open.
So, when CTA0 shuts down and CTA1 is still mining how do I reboot the miner? Just reboot CGMiner in the web interface? Have you figured this out yet?
The fans really blow the heat a long way don't they?
I'm not sure when you would ever encounter this scenario, they basically mine as one unit, you don't direct one board to one pool or anything like that, all the hashrate is directed at whatever pool you point it at. You can SSH in and reboot it that way and it seems to reboot everything.The fans really blow the heat a long way don't they?
I had this exact scenario this morning. Woke up to CTA0 offline, but CTA1 still going strong. I ssh'd into the unit and rebooted it, which seemws to bring everything back online (for now).
I am still running into the problem where one of the "cores" will sometimes stop hashing and total hash rate will drops by about 100 GH both locally and on Eligus. Manifests like this in the stats.
[image snip]
ASIC1Core1 obviously the one not hashing.
[image snip]
ASIC1Core1 obviously the one not hashing.
Same problem, and same core for me. CoinTerra support noted their releasing new firmware soon that should help with this, but we'll see. It's bad enough I paid for 2TH/s but am only seeing 1.2.
I'm really curious why some people see the same hashrate locally and on the pool despite us all using the same firmware and the same pools...the pools seem to show the same share submissions as the local panel so I'm really at a loss as to how there are such hugely different hash rates being calculated. How are some people seeing 1.6 locally and 1.6 on the pool when I get these:
http://eligius.st/~wizkid057/newstats/userstats.php/1MwayhowetdFh7gQHVmKv3LYWUjfwsZ2B3 (my better December unit that claims over 1.6Thash locally...about 1.45Thash on Eligius, noticeably worse on btcguild)
http://eligius.st/~wizkid057/newstats/userstats.php/1MiHnbJ5Kiab9SskUGm5quyhx4aJGYRBYu (my January unit that likes to randomly drop one of the boards and definitely has weird connectivity or mining issues...if you're wondering it claims it's mining at 1.5Thash locally but Eligius sees 1.35Thash or so).
http://eligius.st/~wizkid057/newstats/userstats.php/1MwayhowetdFh7gQHVmKv3LYWUjfwsZ2B3 (my better December unit that claims over 1.6Thash locally...about 1.45Thash on Eligius, noticeably worse on btcguild)
http://eligius.st/~wizkid057/newstats/userstats.php/1MiHnbJ5Kiab9SskUGm5quyhx4aJGYRBYu (my January unit that likes to randomly drop one of the boards and definitely has weird connectivity or mining issues...if you're wondering it claims it's mining at 1.5Thash locally but Eligius sees 1.35Thash or so).
Unfortunately I haven't had any problem with a reported-vs-actual hashrate, so my doing this is probably useless.
I have not bothered to change the hashmeter in the code yet since I can't even test it on a real device any more to see if I've changed the code correctly. I don't have a device and I don't even have remote access to one any more... 
byte1, perhaps I was a little unclear. Try this:
# cd /Angstrom/Cointerra/
# echo 'admin:' > ./lighttpd.password
# cd /Angstrom/Cointerra/
# echo 'admin:' > ./lighttpd.password
JoseSan, That worked. Thank you!
I'm not sure what the question is. Cgminer should compile on the BBB the same as a PC since it's just running linux. The distributed firmware+cgminer on the beaglebone is just older than the code in master cgminer.
Ok, in that case I'll just change out the binary at /opt/cgminer. Earlier in the thread you mentioned hooking up the units to a PC directly, and I was wondering why this was necessary. Re-reading things, I guess the reason was to isolate a potential problem with the BeagleBone itself, as well as to switch from the more liberal hashrate estimation method.
Unfortunately I haven't had any problem with a reported-vs-actual hashrate, so my doing this is probably useless.
byte1, perhaps I was a little unclear. Try this:
# cd /Angstrom/Cointerra/
# echo 'admin:' > ./lighttpd.password
ckolivas, what must be done on a PC that can't be done on the Angstrom Linux/BeagleBone? If need be we could build a version of cgminer and plunk it into a running system.
I'm not sure what the question is. Cgminer should compile on the BBB the same as a PC since it's just running linux. The distributed firmware+cgminer on the beaglebone is just older than the code in master cgminer.
JoseSan: I tried this, and it did not help.
# sudo su root ./lighttpd.password defaults
# sudo su root ./lighttpd.password defaults
Just to further the investigation, I'm also seeing this sort of thing happen. Here's a snippet of the stats page:
http://imgur.com/RCFFu6V.png
http://imgur.com/G3573bo.png
Restarting seems to fix it for about 8 hours.
http://imgur.com/RCFFu6V.png
http://imgur.com/G3573bo.png
Restarting seems to fix it for about 8 hours.
Interesting to point out is that these same cores that eventually stop working after a few hours are also responsible for errors while in full operation.
http://imgur.com/2g64nws.png
I plan to capture the output from /tmp/cgminer.log next time it stops hashing correctly. Currently this is what it looks like:
https://dl.dropboxusercontent.com/u/2009/cgminer.log
ckolivas, what must be done on a PC that can't be done on the Angstrom Linux/BeagleBone? If need be we could build a version of cgminer and plunk it into a running system.
byte1: /Angstrom/Cointerra/lighttpd.password defaults to the following on a fresh box:
Quote
admin:
I can't check at the moment if this changing this actually works.
Jump to: