To confirm I tried both enabling and disable this network.http.http3.enabled But both are working fine. What I think is your problem is related to your browser and not all are affected. What I would like to suggest is if you or someone still having this issue try to reinstall the firefox or it might be a DNS issue using VPN or changing DNS might solve this issue. |
|
|
|
According to their privacy policy here https://www.catex.io/privacyYou will need to be KYC verified so what I think is you might be suspended because you didn't follow their privacy policy. The only way to solve your case is to contact them but it seems they don't want to help you with your case since you have 200k USDT which is very huge I don't think they will help you instead they are going to run that amount. Look at their whois all details are private but there are still some other contact info that I found under about page Check this https://www.catex.com/AboutThere are some phone numbers there and try to call them and let's hope they will help you. |
|
|
|
All of the US based ads look way to shady for me. Thats why I want to send it to a bitmain repair center in the US.
Zeusbtc is a well-known site here on the forum where you can able to buy parts of any ASIC machine and partner with trusted repair companies. They have a list of US-based repair shops look at this link https://www.zeusbtc.com/RepairCenter/USA/ |
|
|
|
I don't see any issue from your logs except on Bootby and the last hashboard with low chip temp. This log BOOTBY[0x12.00000000] means low hash rate. I don't know why the 3rd hashboard is too cool but you can try to use the FMS tool and use the Aging to refresh all chips from the 3rd hashboard. Check my post under this link below to download the exact version of the FMS tool - https://bitcointalk.org/index.php?topic=5367989.msg58929271#msg58929271 |
|
|
|
|
Yes if one hashboard is failing it could affect the other 2 hashboards if you want a better analysis for this unit I suggest you post the whole kernel logs here.
I guess that hashboard have a connection issue replug all cable PSU and ribbon cable from the control board and hashboard should fix this issue.
You can also try running them one by one if you suspected the PSU just disconnect the two hashboards and run only one hashboard to test which one is running fine.
Also, check the PSU connector and test them one by one and then update here the result including logs.
|
|
|
|
Thank you, would you be so kind to tell me where I can find information on how to read the log?
Actually, it's already on Canaan support under the manual tab with the name "Log description" You can go to this link https://canaan.io/service/447 and the manual tab look for Log Description and download it I also suggest downloading the troubleshooting guide to help you on how to read the logs. |
|
|
|
|
I agree and maybe the wallet mining they talking about is staking not the same as Bitcoin.
Staking needs coins to hold to earn from staking while holding your coins at the wallet.
Anyway, the site seems dead it shows "This account has been suspended" and it means he didn't follow the terms from the free trial on directadmin.com which is obvious it was made for scam purposes.
|
|
|
|
I would like also suggest is to try to replug this miner from the wall outlet and replug the Ethernet cable after you do reset. You can also try to do a hard reset I don't know what this miner looks like but I search and it looks like an Antminer s17 miner. Can you try to hold the reset button or the IP report button for 15 seconds then release then replug the miner? You can also try to upgrade the firmware I found someone here who posted a firmware for this unit check the link below - https://bitcointalk.org/index.php?topic=5206886.msg54490620#msg54490620 |
|
|
|
|
That's very cool if you have below 60c temp and others have 70+ high with low fan speed but your TMAX is high it means there are still fluctuate on temp.
Watch this at the end of your logs WORKMODE[1] it means it's running at high-performance mode.
Well, you said it's running fine now after the aging process, so keep monitoring the miner for 24hrs and let's hope it will run stable at that speed.
|
|
|
|
|
What I see here is manipulation you are already being scammed according to your post but after 6 months akminer contacted you for a refund.
You sent them with BTC but they are going to send you USDC which is not acceptable. Look at the price of BTC when you sent them before and now the price of that BTC is a bit higher. For me, I don't accept this if I only have a BTC address and no other crypto wallet they should only send back the exact amount of BTC to me.
The other thing is like the above said why buyback?
You already have bad experience ordering miners from them and you are still planning to buy back to them?
Sorry, but for me, all I see here is manipulation period.
|
|
|
|
~snip~
I'm not so familiar with MacBooks but according to research Mac has pre-installed Python. Can you check what is the python version of your Mac? According to pywallet GitHub page here https://github.com/jackjack-jj/pywalletYou will need to install Macports and install python again through "sudo port install" and better read the guide from that link before you use the command that I suggested above. |
|
|
|
So you want to backup your system and data through TWRP you can only install it if your PadFone is fully rooted and it must be bootloader unlocked if it has a bootloader locked. Rooting a phone or this tab is risky there is sometimes the system becomes corrupted and ends up wiping the whole data to recover your Tabfone. I do not recommend this but if you still want I search a bit and it seems there is a guide for this unit. Check this link https://tweakdroid.com/root/asus-the-new-padfone-infinity-a86-padfone-t004-a86/My suggestion is if you have crypto apps and wallets there that you want to backup I think it would be better if you transfer or send them to a new wallet for safety. Or for safety backup you can try to backup apps and data through the ADB command you can enable the developer option under about and backup them through PC with ADB command. Check this link on how to do it https://www.youtube.com/watch?v=AEyIWHLL2Is |
|
|
|
|
You didn't follow what I suggested in my previous post as I said try to run the miner at higher fan speed. Because I notice TMAX reach higher temp.
Also, keep updating the API logs here so that we can analyze your issue well.
And normally you can't force this unit to run at high-performance mode but you can prefer to switch work mode to performance mode. You can find it under configuration on Web UI. This unit is not running stable at high-performance mode it automatically switches if they detect high ASIC temp. Look at your previous logs TMAX it shouldn't reach above 85c as a recommended chip temp.
|
|
|
|
Does anyone know off hand which would be the best PC based software to clone a phone drive so it can be virtually hosted later. I know PC allows this but phones are more picky and obviously its a different operating system. Something I should already know, Im searching now just thought I'd ask here as no doubt people repeatedly lose unique crypto related data this way unfortunately.
What exactly is the unit model of your phone and the exact problem of your phone? Maybe the issue can be repaired easily? I don't know if there is free software that you can clone phone but I know there are many tools out there that you can dump the whole data including firmware, system, and data files. Those tools are EMMC tools but you can only have these tools if you have a jtag box and tools you should have tech knowledge about this because you will need to disassemble the unit to jump connection directly to EMMC where your Nand IC and data storage are located. |
|
|
|
Not only ECHU shows error but also this HASHS[1 0 0] it means the first hashboard is bad. Dumb question, but can't find the answer, which direction do they number the boards?
Looking at the back of the machine, is #0 on the far right, or left?
Why not check the mm board physically it should have something named under the ribbon cable of each board. But my guess is if you are facing on the back the first board should start at the right and if you are facing on the front it should start from the left it just like you are reading a text beginning to the left. |
|
|
|
If you are looking for a factory firmware that could bypass ASIC check then there is no factory firmware that you can find here or even in Bitmain's support page. You can only bypass the ASIC check if you install a modified firmware try to check the BraiinsOS you can able to bypass those broken chips. You can find the official thread here https://bitcointalk.org/index.php?topic=5036844.0 |
|
|
|
No, it's not normal for Bitmains PSU since you are using a Chinese PSU I don't know how this PSU works. Usually that kind of issue it's due to leak or maybe have broken capacitor if you have a multitester that could read capacitor from your PSU you can check those broken capacitors. The multimeter that I use looks like this  You can replace that broken capacitor with the same value. |
|
|
|
Sometimes the wallet.dat is corrupted if you copy the wallet.dat while the Bitcoin core is running on the background and maybe you made a backup copy while the Bitcoin core is open. I have experienced having a corrupted wallet.dat the size of the file that I copy is different from the original. I'm lucky that I didn't remove or delete the wallet file under bitcoin core data folder. So your problem is you have a corrupted wallet.dat file I'd like to suggest you to try dumping the private key from your backup through pywallet.py check this guide below If that doesn't work, you'll be down to the very last resort... which is the process that this guy used: https://bitcointalk.org/index.php?topic=1404609.msg14257235#msg14257235It involves getting a small USB stick (preferably 1GB)... wipe it clean (delete everything off it, format it etc) and putting just your "corrupted" wallet.dat on it. Then you have to manually run the pywallet command from the commandline to get it to scan your corrupted wallet.dat and try and recover private keys. Assuming you had a 1GB USB stick and it was showing on windows as D: and you "extracted" PyWallet to "C:\PyWallet" (when running the PWI_0.0.3.exe): Step 1. you would put (a copy) of your corrupted wallet.dat on the USB stick Step 2. Start -> Run, Type cmd and press enter Step 3. cd \PyWalletStep 4. pywallet.py --recover --recov_device=D: --recov_size=1Gio --recov_outputdir=C:\PyWalletIf your USB stick is larger, change 1Gio to what Gigabytes it is... 8GB = 8Gio, 16GB = 16Gio... if you use a stick larger than 1GB, be prepared to wait a LONG time while pywallet scans it. After that finishes, it should have created a "recovered_wallet_DATESTAMP.dat" that you can attempt to load in Bitcoin Core... or use PyWallet to dump the keys  |
|
|
|
|
Show Posts
