after aging tmax also rises , please help
It's pretty bad it become worst I don't know if there is a thing that it can revert back I hope that you can use the FMS tool that has an aging button because you can monitor the progress I think aging takes 20 minutes to 1hr don't reboot the unit while aging. Try to aging again don't restart the unit. If aging is done it will automatically restart itself and then set up the unit later once it's done let it hash for 30 minutes to 1 hr go back here and update the status. You can also play on this command with the aging parameter below [{"command":"ascset","parameter":"0,aging-parame- ter,60-537:562:587:612"}]
|
|
|
I just checked that on PC and I confirm that their paid service is not working. I submitted several transaction IDs with the fee rates ranging from 8 sat/vbyte to 15 sat/vbyte to their paid service and got error for all of them. It only displays a message at top of the screen saying "Error" without any explanation on what causing the error.
It appears that this paid service was simply added as a design feature or it might be temporarily disabled due to some reason. I can't find any announcement on Viabtc about this there might be a reason why it does not work. Do you have any balance or deposit coins in Viabtc?
|
|
|
Can you provide me aging fms code
You can find the aging button on the FMS tool you might have downloaded the wrong one that does not have an aging button. Try the FMS app 2020.10.29 or if you can't find it you can use this command below [{"command":"ascset", "parameter":"0,aging-set,1"}] The above log is under high performance but its hashing like normal mode not more than 40 hash
Yes, but it's weird if the hashrate didn't change. I also noticed the frequency didn't change and the first hashboard is set to low frequency(--avalon10-freq 390:408:428:448). Please try aging first it might fix your issue.
|
|
|
Well I don't think you right because they limited the account due to suspicious "login" from what they said, also the limits have been added just after I bought the crypto. Whatever is good to know, I just wanted to share my experience with you, so you can avoid risking you're crypto, they do magic, can make them vanish (also I live in Italy) There are some users here who experience the same thing they also received a response that support said there is a suspicious login but the real reason is they also violated the gambling policy they admit it. So I believe that's the reason why your account is limited. If the support tells you that there is a suspicious login why not try to request for login history and IP? So that we know if they actually pointing to suspicious login and not the violated policy. And then ask them what should you do to lift the limitation?
|
|
|
I think the reason why your Coinbase account become limited is due to their gambling policy. Look freebitco.in is a gambling site if you made some transaction using Coinbase to send or receive from freebitco.in then you've already violated their policy.
Also, coinbase is not a good place to buy coins their service is pretty strict compared to Binance based on my experience.
Anyway, how do you buy ETH did you use coins or FIAT? If you paid it with FIAT through a bank you can maybe able to dispute the transaction.
|
|
|
The temps looks fine, have you change the work mode under pool configuration? If it set to normal mode the high performance mode will not be trigger but if it set to high performamce mode it should work. I don't see any reason why it does not work would you mind to try aging you can use FMS tool to do aging. Download it on Canaan support here https://www.canaan.io/service/447
|
|
|
Take note that individual miners have no control over choosing transactions that are included in a block and you should ask mining pool operators to include your transaction.
Actually, they can, If the individual miners are mining solo and have a full node they can add a transaction they like. The only problem is if they only have a few units to mine it won't be enough to find and mine a block faster. It needs a huge mining power to be able to solve a block faster and confirm transactions. @OP the chances of finding someone here who mines solo are very slim. Most of the small miners nowadays are mining directly to a mining pool which is why you can only request to prioritize your transaction to a mining pool operator like the one mentioned above (Viabtc).
|
|
|
It was infected with a virus. I updated the firmware and changed the ip and password. Now it’s all ok. What I notice now is that the hashrate has gone from 81th to 76th. I have done the aging option but it does not pass from that
How about the temp? Have you monitored the temp? The high-performance mode will not be triggered if your miner is hot. You should cool down the miner a bit. Try to increase the fan speed of your miner at 90% to test if it can help to drop down the temp and trigger the high-performance mode.
|
|
|
If I follow the mempool.space fee recommendation in low priority it takes around 3 to 10 minutes and for medium priority sometimes it's instant or it takes 3 to 5 minutes and the high priority it is almost instant but sometimes it's around 3 minutes.
Take note any wallet with a custom fee has the same transfer time no wallet has a special feature to make a transaction faster, Like the above said it doesn't matter what wallet you use the transfer time depends on how much fee you pay and how the network congested is.
|
|
|
Yes I bought it used but it was working fine. What is strange is that it changes the login password. Usually it should be root
Most of what I heard from other users who bought used units experienced the same thing there might be something on the firmware it might loaded with modified firmware or malware that possibly has a locked pool and password so regardless of how many times you change the pool and password it would only reset back to original pool and password. If you haven't tried to flash the unit try it first it might fix the issue you can also use the upgrading tool to update the unit.
|
|
|
So it makes me wonder if those QR codes are actually my wallet, or maybe they are just the blocktrail pubkeys as third party of the 2-3 signature
I tried to search but no clues if the QR code there is yours or not. Why not try to contact the support? The pdf backup file contains email and support secret numbers you can provide it to them and ask if you can able to recover your old wallet that generated a P2PKH address.
|
|
|
So you mean you have an extra orange Pi and SD card and it works after you change the Orange Pi and SD card? Is that what you mean? Correct me if I'm wrong.
Do you know exactly how to flash this unit? There is a PROG jumper that you need to set up according to their manual have you changed the jumper position? I just want to know if flash it correctly because you said there is an activation serial for the orange Pi I don't know what exactly is this but according to the manual during flash, you need to initiate an internal firmware update for hashboards by going to menu → Service →Firmware Update on the menu press [YES] button and wait for a few minutes before you set up and run the miner. Have you done this? If not, do it first then try to test it again.
If it doesn't work, stick with the working orange Pi and SD card you mentioned earlier.
|
|
|
Did you buy this miner as a used unit?
Can you use other devices to set up your miner maybe the device you currently using is infected try to set up your miner through mobile or another PC that you know is clean.
Also, try to change the pool using another browser and incognito mode. Update here if it works or not.
|
|
|
Use the latest version
If you already using the latest one I suggest reflash it again with the file image above and try again. If still does not work it might be a hardware error. You can try to clean the unit terminals and replug all cables including the power supply because the logs show that the PSU is not communicating well. This unit is rare here on the forum the solution that I share are based on my research, experience and the logs you provided above if the solution that I provided above do not work my last thought is to try this " Bitfury b8 with Huawie power supply hash boards not hashing" and other suggestion from that topic.
|
|
|
The error you mentioned actually fixed in version 3.2.0, which was years back.
According to this bug reports it also comes up on newer version no report yet on the most recent version but other version like 4.1.5 also have this bug. - https://github.com/spesmilo/electrum/issues/6436@OP Did you get the error message after you enter the command line? Or does it also show up on the Electrum GUI? If the error came from the most recent version I suggest report this to the Electrum issue page and then let the developer release a fixed version. If you have a backup seed I suggest try to downgrade Electrum to 4.4.5 or lower and update here if it fixes your issue.
|
|
|
I forgot to tell you to put the logs inside the insert code tag to make these logs easy to read or if you have limited characters put the whole logs into pastebin.com and paste the link here. Anyway, I saw some errors from the logs it said "initializing issue" and it can't read the PSU and the hashboards. Would you mind to update it to the latest version you can download the SD card image from Bitfury support or go to this link below. - https://bitfury.com/crypto-infrastructure/support
|
|
|
Why are you trying to import the old version of the Electrum keystore to the Sparrow wallet that was just released recently. The Electrum.dat file generated from the old version of Electrum has a different structure and it might not work to import to Sparrow wallet. To fix this issue you will need to update the wallet to a new wallet structure to get the right seed or to extract the private key and import it to the Sparrow wallet. If you want to update the Electrum.dat structure you will need to import it to the latest version of Electrum it should be automatically updating to the new wallet structure which is a default_wallet file with no file extension. Once it's than you can use the console to extract private keys and then import it to Sparrow wallet. Take note before you do it make sure you have a backup copy of the old electrum.dat file in case you fail to update the wallet structure. Also, read this old thread below from pages 1 to 2 so you can maybe get some idea of how to update the wallet structure of Electrum wallet. - https://bitcointalk.org/index.php?topic=325364.0
|
|
|
The issue is overheating which is why your miner is not running in high-performance mode.
You need to find a way to cool down the miner. If your room does have a window you might need to exhaust the hot air out to cool down the miner.
Or manually set the miner's fan speed to 90% to cool down the miner.
|
|
|
What pool do you mine? If you are not mining on Viabtc would you mine try Viabtc pool or other pool listed here below? - https://miningpoolstats.stream/bitcoinIf it still does not work would you mind sharing your miner logs and post it here we can maybe find the issue under the miner's logs.
|
|
|
"Failed (Unset): Cannot parse transaction: Claimed value length too large: 32" I use trustwallet to send my Bitcoin transaction btw. That error comes up if you just pasted a transaction hash you should paste a raw/hex format as suggested above to avoid this error. Once it is successful the transaction hash will show up. I don't know if you can able to get the raw/hex code from the trust wallet but if you aren't able to get it from that wallet then try to get the raw/hex code from blockchair by accessing your transaction hash follow the instructions below this guide only works if the transaction is not yet rejected by blockchair nodes. - Go to https://blockchair.com- Paste the TX hash then enter - Scroll down you can find the "Raw TX" at the bottom and then copy the hex code - Then paste it to any PushTX sites below to rebroadcast the transaction. - https://www.viabtc.com/tools/broadcast- https://www.blockchain.com/explorer/assets/btc/broadcast-transaction- https://coinb.in/#broadcast- https://blockstream.info/tx/push
|
|
|
|