hi guys

thanks for the information.  this is what i was looking for and it was right under my nose lol

thank you all for your feedback

Mars

hi guys

Dont know if i am asking a question that has been asked before.

Is there a website that reports which BTC address won the block reward?

Thanks
Mars

hi guys

I am looking for 3rd party firmware to see if i can upgrade on my T1's and T9's respectively.  I saw some old posts that were talking about using BrainsOs on the T1's and read that people were having issues with this. 

The T9's I have are not the pluses (T9+) and this firmware has bricked a couple of my units. 

I found some 3rd party websites but they are asking for BTC donations; more likely a scam site. 

open to any ideas

Thanks

Mikey


I appreciate the assistance; after 5 different fans, i have come to the conclusion that i need to try the SD card method.  I will attempt this and post my results.  I do appreciate the advice!

John

here is a part of the log....




main.c:13992: log_level = 4
main.c:14019: This is XILINX board. Totalram:       1039691776
main.c:14025: Detect 1GB control board of XILINX
driver-bitmain.c:1776: mmap axi_fpga_addr = 0xb6f18000
driver-bitmain.c:1781: axi_fpga_addr data = 0xc725
driver-bitmain.c:1797: mmap fpga_mem_addr = 0xb5d11000
driver-bitmain.c:994: forceFreq=-1 forceFlag=0
driver-bitmain.c:1696: min work minertest[0]:912


main.c:8570: DETECT HW version=8000c725
main.c:14064: miner ID : 815c6c2870258854
main.c:14097: Miner Type = T9+
main.c:14101: AsicType = 1387
main.c:14104: real AsicNum = 18
main.c:14197: use critical mode to search freq...
driver-bitmain.c:1876: get PLUG ON=0x000000e0
driver-bitmain.c:1907: Find hashboard on Chain[5]
driver-bitmain.c:1907: Find hashboard on Chain[6]
driver-bitmain.c:1907: Find hashboard on Chain[7]
dsPIC33EP16GS202.c:164: dsPIC33EP16GS202_reset_pic failed on Chain[0]!
dsPIC33EP16GS202.c:164: dsPIC33EP16GS202_reset_pic failed on Chain[0]!
dsPIC33EP16GS202.c:164: dsPIC33EP16GS202_reset_pic failed on Chain[0]!
main.c:2126: chain[5] PIC jump to app
dsPIC33EP16GS202.c:117: dsPIC33EP16GS202_jump_to_app_from_loader failed on Chain[0]!
dsPIC33EP16GS202.c:117: dsPIC33EP16GS202_jump_to_app_from_loader failed on Chain[0]!
dsPIC33EP16GS202.c:117: dsPIC33EP16GS202_jump_to_app_from_loader failed on Chain[0]!
dsPIC33EP16GS202.c:61: dsPIC33EP16GS202_get_pic_sw_version failed on Chain[0]!
dsPIC33EP16GS202.c:61: dsPIC33EP16GS202_get_pic_sw_version failed on Chain[0]!
dsPIC33EP16GS202.c:61: dsPIC33EP16GS202_get_pic_sw_version failed on Chain[0]!

Thank you for the quick response.


I have the firmware in place for a t9+ but the miner doesn't hash; its as if control board doesn't send the command to the cards on the miner. 

the Miner produces chain errors in the logs. 

any advice on how i can get this miner running?

Thanks

I have an couple of antminer T9's that has been upgraded with t9+ firmware; i have attempted to revert this back to its original firmware and to my suprise, it doesn't load?  i come up with an error cannot find signature

is there an alternative firmware set that we can use to resurrect these units without getting new control boards?

thanks

I am really sorry to see that happen to you.  DM me, we want to help you with your law suit and can provide some good evidence that proves they are crooks.

Glad you got your equipment back...I know from personal experience myself what these guys were all about. 

let me know if you are looking for a hosting site. 

Karma is a bitch! 

John

Wow    - cant say I am not surprised.

IF anyone is interested in hosting; I have a source in Southern Oregon.  They are currently in the middle of a build out and already have 3 MW allocated.

Send me a private message for more information

Mars

New bitcoin mine is coming online in Southern Oregon; we can host up to 4000 units and have 3 MW at our fingertips and can easily expand to 6 MW.  Our website is still under construction and should be up in the next coming week.  We have two 10 ton crack units for cooling and a blower for moving the air out of our building.  The building is a 4000 sq ft data-center; the largest in southern Oregon.

We take security seriously have been pen tested by Dell Secure works. (https://www.secureworks.com/)

Services are as follows and included with all hosting packages

BTC End to end configuration
BTC you are on your own VLAN
BTC VPN services for remote access to your units
BTC 24/7 monitoring with email notification of your miner going down

BTCRates $79 per kw - example an S9 would host for $87 as it uses 1.4 kw

Large Quantity hosting - 100 or more - inquire within for special pricing.

Payments

Please email us at hello@marsmining.co to get setup.

I don't understand.... Why would Terence, your son, call us and threaten litigation in California and Oregon when we are only telling the truth of our experience?  We gave you ample time to respond to us and I was more than happy to discuss this offline but you failed to respond to an email we sent on the 10th of June.  

As i mentioned before, in person, you have a clause in your contract that states you can terminate a relationship in two days.  We did not bring it up in fear that we would be asked to vacate the premises.  Based on your son's reaction with threats of litigation also and "to get ready to spend some capital" with the fact that you shut us down 10 days before our term was up; i think we are spot on with our assessment of the kind of people you are and the reasons we took precautions to safeguard our investment and profitability.

We emailed you on the 10th of June and you "elected" not to respond to us; you instead wanted to "brush it under the rug" and assume that it will go away.

This is why we posted here; to see if there were others who had the same experience.  

John

PS - you still have our Power Cables

Hello BitcoinTalk forum.

I would like to put out all of the facts here with my experience with Oregon Mines.  We just finished a 1 year contract with this company and have to say that it was very painful; especially in the end.  These accusations are my opinion and i am using my 20 years of IT experience to make these assertions and determinations.  

This note is to serve as a public notice.

When we first moved our miners, 49 T9's and 1 S9, June 10th 2017 and signed a 1 year contract and every month on the 10th of the Month we would receive our hosting bill.  What they didnt know was that we had other miners at different hosting companies in addition to Oregon Mines.  This will make sense further in this read.  When we moved in, we were given a VPN to connect and manage our miners but were also told to leave the password to default so that "awesome miner" can do its monitoring.  We were given a network 10.0.28.x; a month or so later, they moved two of our units onto a different network; the two IP's were 10.0.10.112 and 113 respectively.  If you have hosted with Oregon Mines and had your miners moved to the 10.0.10.x network  and you experienced something similar please send me a direct message.  

We used Slushpool for our BTC pool and monitoring.  Each time a miner went below 7.5TH, we would receive and email notification from Slush stating that a miner would go offline and when a miner returned to normal hashing, another email would be sent indicating that the miner was back up and running.  When we look at all of the emails from June to June, the bulk of them were for outages that exceeded one hour and occurred outside of any maintenance window during our first 6 months at Oregon Mines.  Since our password change, we show nothing out of ordinary (discussed further in the post).

What we experienced

The two miners on the aforementioned network (10.0.10.x), known as 48 and 49, would go down at least once a week for a period of an hour or so in the beginning.  This would occur more frequently as time passed and as they grew more confident over time.  It became so brash that these two miners went offline for a total of 3 days and after repeated emails they finally came back online.  As time went on, we would see other units, #42 and #50, go down for the same amount of time, usually overnight and on a Friday evening and not during a maintenance period.  In December, i sent a message inquiring about an S9 going offline and as it was explained to me, "they needed to take it offline for the next 3 days to test the power supply" My next email told them not to touch anything; my spidey senses were going crazy right now and that is when I changed all the passwords to all of our units.  On December 17th, 2017, i logged into the VPN and reset all of the passwords to all of our miners.  Guess what didn't happen, our miners never went offline for a period no longer than 1 hour; unless there was a planned maintenance. For those who don't know, if you save the image of a miner and then upload a configuration file containing new pool information, one can mine using your unit as long as they have access to the unit's username and password. It proved that there were shenanigans going on.  So what do we do?  Stay put and find an alternative action which is what we did, we found a location and started our own mining farm build out.

We did not notify Oregon Mines of the change nor did we tell them of the incident until the request for renewal in May 2018. Why you ask? Because they have a clause in their contract that can terminate a relationship with a client, at will, and you would have 2 days to retrieve your equipment.  We feared that if we made any claim that we would have been thrown out in January.  We couldn't afford to do that as other hosting facilities were maxed out.  

So on May 10th, we paid our final invoice for the service to June 10th.  

Ready for the next kicker?  

On June 1st, they shut us down and packed everything up.  We were paid through June 10th, why the rush to get us out?  Was it a mistake on their part to take us offline or was it because of what we claimed?  Oregon Mines did refund us for the 10 days we were offline plus a little extra for the inconvenience; 0.25389 BTC @ $7600.  Had we remained online, we would have generated 0.39 BTC but this isn't about that; it is about the obvious blatant theft.  When they told us that they weren't placing them back online we requested to have all of our miners, power-supplies and power cables ready for pickup; Oregon Mines still has our power cables and have not responded to our last email sent on the 10th of June.

Now there was no explanation as to why our miners went offline during those 6 months and why we did not see the same miners go offline after the password change.  They claimed that it could have been an IP conflict which i know is unlikely as they hard code all of the units to their subnets and document the unit with its IP information and if it were, on the off chance, one of the conflicting interfaces would have been accessible.  They then stated that they do not guarantee 100% up-time and they are correct; no host offers up 100%.  What we established here was a pattern of outages and theft of the use of our miners.

We used three different mining hosts, all under different dba's, other than Oregon Mines; while each host is unique with their issues none of them were as egregious as Oregon Mines.

This is an excerpt of an email sent to Oregon Mines on June 10th; our last communication with them.

Timeline of events leading to our shutdown.
- May 10th 2018 - paid Invoice for Oregon Mines
- May 10th 2018 - received email notifying us of contract renewal
- May 10th 2018 - responded and explained of issue with downed miners over the course of 6 months
- May 10th 2018 - was offered "fair compensation" for downed miners and to name a price; we didn't respond and were going to wait until the end of the term on June 10th
- June 1st 2018 - We were forcibly terminated from Oregon Mines
- June 2nd 2018 - was offered fair compensation for the 10 remaining days; $1750 for remaining days to cover remaining hours we paid for at a 125% premium
- June 2nd 2018 - We requested that our machines be put back online
- June 2nd 2018 - Machines were boxed and placed into storage
- June 7th 2018 - Received 0.25 BTC from Oregon Mines
- June 8th 2018 - We picked up our machines and power supplies; we did notice that our power cables were not included as requested in email on June 2nd.

Thank you
John from Mars Mining

Dude Tell me about it!  i was trying to sell at 3.45 and they screwed me by holding my deposit.

I don't think Kraken is the problem.  I have a deposit into Bithumb sing January 4th as well.  I believe it may be the way XRP and exchanges interact.  i ahve sent my XRP off of Kraken and onto HITBTC and it didnt show up right away; i had to put in a ticket on their system and then i saw it in the morning. 

Im going to take the advice of someone who posted on here and will do 1:1 tickets specifically, requesting for my deposit.  might get lucky.....who knows. right?!?!?

This is really frustrating and do not understand why this is such a big deal?!?!

Yea, that's what i said, full of shit!


That's exactly what i am doing.  i first open a ticket and allow 24 hours to pass then i place a call to them trying to illicit more responses in order to get more information.  I also go to their twitter feed and demand to know what happened to my XRP deposited on the 4th of January.

We should get a list of people who are going through the same thing and make a unified voice.

You have got to hear this, i just got off of the phone with Bithumb Korea, they tell me that everything will be processed at the end of the month and that my XRP will go into my account then.  when i asked why they told me it is the government in KR that is holding all transactions in limbo and that the transactions need to be recorded per government approval.  I was like WTF???  Never heard such bullshit in my life.  

has anyone else heard this?

This is their response

Thank you for contacting Bithumb Customer Support.

With regard to pending XRP deposit, we sincerely apologize for such a prolonged delay.
As addressed over the phone, it is coupled with governmment announcement on clampdown on false-name base transaction. It makes us to get on with each and every transaction one by one manually, resulting in being left on invitable hold for long.

We mad sur to deliver your request on the phone along with this inquiry.


Best regards,

Bithumb Customer Support



 

Giving an update - January 15th.  no XRP.  I called their support line and the guy whom i spoke with was surprised at the amount of time (since January 4).  He placed me on hold and spoke to his manager where he told me she had sent an email to that dept.  So i dont know what is going on. 

i too have had the same excuses used with the exception of #4

i agree on the class action .... count me in!

So i just sent them a request to send my XRP back to my originating wallet.  its been 5 days and i just find this ridiculous

I have the same issue where my XRP has not showed up at Bithumb.  i received the following message to one of my tickets

Message
"안녕하세요 회원님 빗썸 고객센터입니다

문의주신 내용 확인 후 담당부서로 전달 드려 확인 요청 드렸으며 확인 후 회원님의 계정에 입금처리될 예정입니다.

다만, 확인까지는 다소 시간이 소요될 수 있으며 소요되는 정확한 시간에 대한 안내는 어려운 점 양해 부탁 드립니다.

입금이 늦어지고 있는 점 사과 말씀드리며 최대한 빠른 처리를 위하여 최선을 다하겠습니다.

이용에 불편을 드려 진심으로 죄송합니다.

더 궁금하신 사항은 빗썸고객센터(1661-5566)로 문의 부탁드립니다.

감사합니다."

Translated - "Hello, member, Bitsum Customer Center

After confirming the contents of your inquiry, we will forward it to your department and we will send it to you.

However, it may take some time to confirm, and it is difficult to know the exact time required.

We apologize for the late payment and we will do our best to make it as quick as possible.

We apologize for any inconvenience you may have experienced.

For more information, please contact the Bitsum Customer Center (1661-5566).

Thank you."



is the issue Kraken? or is it Bithumb?