Topic: Official FutureBit Apollo BTC Software/Image and Support thread - page 131. (Read 52205 times)
jstefanop, any news on standalone apollo miner? Still waiting for any support for older Raspberry Pi's. https://github.com/jstefanop/Apollo-Miner-Binaries/releases/ shows nothing new since the release, unfortunately. Thanks.
Seems like the Bitcoin block or index are a corrupt and not allowing my Apollo BTC full node to keep running past this block.
The entries from the log are below:
2021-06-22T22:28:27Z LevelDB read failure: Corruption: block checksum mismatch: /media/nvme/Bitcoin/chainstate/399540.ldb
2021-06-22T22:28:27Z Fatal LevelDB error: Corruption: block checksum mismatch: /media/nvme/Bitcoin/chainstate/399540.ldb
2021-06-22T22:28:27Z You can use -debug=leveldb to get more complete diagnostic messages
2021-06-22T22:28:27Z Error: Error reading from database, shutting down.
2021-06-22T22:28:27Z Error reading from database: Fatal LevelDB error: Corruption: block checksum mismatch: /media/nvme/Bitcoin/chainstate/399540.ldb
I have rerun the bitcoind program with the -debug option and I get the same log entries.
I was looking thru the -help contents and it seems -reindex might be the answer, but I wanted to check with the group here to see if there was a better option.
The entries from the log are below:
2021-06-22T22:28:27Z LevelDB read failure: Corruption: block checksum mismatch: /media/nvme/Bitcoin/chainstate/399540.ldb
2021-06-22T22:28:27Z Fatal LevelDB error: Corruption: block checksum mismatch: /media/nvme/Bitcoin/chainstate/399540.ldb
2021-06-22T22:28:27Z You can use -debug=leveldb to get more complete diagnostic messages
2021-06-22T22:28:27Z Error: Error reading from database, shutting down.
2021-06-22T22:28:27Z Error reading from database: Fatal LevelDB error: Corruption: block checksum mismatch: /media/nvme/Bitcoin/chainstate/399540.ldb
I have rerun the bitcoind program with the -debug option and I get the same log entries.
I was looking thru the -help contents and it seems -reindex might be the answer, but I wanted to check with the group here to see if there was a better option.
Delete that file. It will be recreated. Bitcoin Core will reindex everything itself when missing file is discovered.
Seems like the Bitcoin block or index are a corrupt and not allowing my Apollo BTC full node to keep running past this block.
The entries from the log are below:
2021-06-22T22:28:27Z LevelDB read failure: Corruption: block checksum mismatch: /media/nvme/Bitcoin/chainstate/399540.ldb
2021-06-22T22:28:27Z Fatal LevelDB error: Corruption: block checksum mismatch: /media/nvme/Bitcoin/chainstate/399540.ldb
2021-06-22T22:28:27Z You can use -debug=leveldb to get more complete diagnostic messages
2021-06-22T22:28:27Z Error: Error reading from database, shutting down.
2021-06-22T22:28:27Z Error reading from database: Fatal LevelDB error: Corruption: block checksum mismatch: /media/nvme/Bitcoin/chainstate/399540.ldb
I have rerun the bitcoind program with the -debug option and I get the same log entries.
I was looking thru the -help contents and it seems -reindex might be the answer, but I wanted to check with the group here to see if there was a better option.
The entries from the log are below:
2021-06-22T22:28:27Z LevelDB read failure: Corruption: block checksum mismatch: /media/nvme/Bitcoin/chainstate/399540.ldb
2021-06-22T22:28:27Z Fatal LevelDB error: Corruption: block checksum mismatch: /media/nvme/Bitcoin/chainstate/399540.ldb
2021-06-22T22:28:27Z You can use -debug=leveldb to get more complete diagnostic messages
2021-06-22T22:28:27Z Error: Error reading from database, shutting down.
2021-06-22T22:28:27Z Error reading from database: Fatal LevelDB error: Corruption: block checksum mismatch: /media/nvme/Bitcoin/chainstate/399540.ldb
I have rerun the bitcoind program with the -debug option and I get the same log entries.
I was looking thru the -help contents and it seems -reindex might be the answer, but I wanted to check with the group here to see if there was a better option.
...
Yes, this was the original plan, unfortunately to containerize the app was too much work to make it in time for release. This will also make it easy to install the web app on any other system so the standard units can have a nice UI as well.
I would highly suggest against this.Yes, this was the original plan, unfortunately to containerize the app was too much work to make it in time for release. This will also make it easy to install the web app on any other system so the standard units can have a nice UI as well.
'Containerized' apps require the producer of the container to regularly update the container whenever a problem is found with any software included in the container, and thus also require each person running the container to update their container when this happens.
The long term result of this is: most people running old, out of date software in their container, usually with various known security issues.
If instead the OS (like ubuntu) is allowed to update the 'system', this solves that issue for hardware that no one bothers to check.
The basic issue is that this device is expected to be directly connected to the internet, so a design leading to commonly unpatched security issues is problematic.
Can the CPU fan run from any of the 5v/GND GPIO pins? Or does it have to be run through the proprietary connector you guys have made?
Hey guys make sure if your connected to the system with the monitor you DO NOT do any system level updates (ie ubuntu asking you to update the kernel etc). Even though we tried to keep the system and 'app" as separate as possible the full node system is still really an embedded system with lots of system level tweaks to make it work. If you update the system lots of these will be will be wiped and youll be left with a bricked system until you reflash the SD card.
Mainly a suggestion for a future release:Package the "app" as a container (Docker for example) and map the necessary i/o connections directly to it. That way all the dependencies and changes needed by your own implementation can stay as you want without a risk of a system update making modifications and on the Ubuntu side the system updates and package installs (which may also pull updates as dependencies) can be used without having to worry of something getting unintentionally modified. That could also make reseting the setup back to defaults easier since it would just be a matter of discarding the container and starting a clean one.
Yes, this was the original plan, unfortunately to containerize the app was too much work to make it in time for release. This will also make it easy to install the web app on any other system so the standard units can have a nice UI as well.
Hey guys make sure if your connected to the system with the monitor you DO NOT do any system level updates (ie ubuntu asking you to update the kernel etc). Even though we tried to keep the system and 'app" as separate as possible the full node system is still really an embedded system with lots of system level tweaks to make it work. If you update the system lots of these will be will be wiped and youll be left with a bricked system until you reflash the SD card.
Mainly a suggestion for a future release:Package the "app" as a container (Docker for example) and map the necessary i/o connections directly to it. That way all the dependencies and changes needed by your own implementation can stay as you want without a risk of a system update making modifications and on the Ubuntu side the system updates and package installs (which may also pull updates as dependencies) can be used without having to worry of something getting unintentionally modified. That could also make reseting the setup back to defaults easier since it would just be a matter of discarding the container and starting a clean one.
I am getting a scoring hash rate on slush pools dash board. So are you sure I'm not getting internet?
Hey guys make sure if your connected to the system with the monitor you DO NOT do any system level updates (ie ubuntu asking you to update the kernel etc). Even though we tried to keep the system and 'app" as separate as possible the full node system is still really an embedded system with lots of system level tweaks to make it work. If you update the system lots of these will be will be wiped and youll be left with a bricked system until you reflash the SD card.
Well be issuing updates on the web UI remotely (there will be a yellow update button in the dashboard) you can install whenever they are available, but for system updates please wait until we issue updated SD card images.
Well be issuing updates on the web UI remotely (there will be a yellow update button in the dashboard) you can install whenever they are available, but for system updates please wait until we issue updated SD card images.
uh ok.. is there a step-by-step guide on how to re-flash? mine is not bricked, but it keeps disconnecting from the pool giving me the "There is a problem fetching system stats (Internal error)" error.
That error is displayed when there is no internet, so you unit is most likely losing wifi or your network is going down.
That's different to my experience. My internet and pool connection was stable and I still got the same error. Re-flash sorted it though and its been stable and running for 24 hours now. Just need a replacement fan now though which I'm in talks with support to get hopefully.
Speaking of which. Seeing as the fan is only 2pin, is it running at full 5v all the time, as I see its connected to the proprietary connector on the SBC. Would it be possible to connect a different fan to different 5v/GND GPIO pins?
Hey guys make sure if your connected to the system with the monitor you DO NOT do any system level updates (ie ubuntu asking you to update the kernel etc). Even though we tried to keep the system and 'app" as separate as possible the full node system is still really an embedded system with lots of system level tweaks to make it work. If you update the system lots of these will be will be wiped and youll be left with a bricked system until you reflash the SD card.
Well be issuing updates on the web UI remotely (there will be a yellow update button in the dashboard) you can install whenever they are available, but for system updates please wait until we issue updated SD card images.
Well be issuing updates on the web UI remotely (there will be a yellow update button in the dashboard) you can install whenever they are available, but for system updates please wait until we issue updated SD card images.
uh ok.. is there a step-by-step guide on how to re-flash? mine is not bricked, but it keeps disconnecting from the pool giving me the "There is a problem fetching system stats (Internal error)" error.
That error is displayed when there is no internet, so you unit is most likely losing wifi or your network is going down.
Hey guys make sure if your connected to the system with the monitor you DO NOT do any system level updates (ie ubuntu asking you to update the kernel etc). Even though we tried to keep the system and 'app" as separate as possible the full node system is still really an embedded system with lots of system level tweaks to make it work. If you update the system lots of these will be will be wiped and youll be left with a bricked system until you reflash the SD card.
Well be issuing updates on the web UI remotely (there will be a yellow update button in the dashboard) you can install whenever they are available, but for system updates please wait until we issue updated SD card images.
Well be issuing updates on the web UI remotely (there will be a yellow update button in the dashboard) you can install whenever they are available, but for system updates please wait until we issue updated SD card images.
uh ok.. is there a step-by-step guide on how to re-flash? mine is not bricked, but it keeps disconnecting from the pool giving me the "There is a problem fetching system stats (Internal error)" error.
Does anyones dashboard on their apollo say this error:
There is a problem fetching system stats (Internal error)
There is a problem fetching system stats (Internal error)
Yea I had that when it was connected to a monitor and keyboard. Re-flash the SD Card and set the miner up again. Should be fine after that.
Ive flashed mine three times to get it to be stable enough to stay in for more than a day.
Does anyones dashboard on their apollo say this error:
There is a problem fetching system stats (Internal error)
There is a problem fetching system stats (Internal error)
I just started my 2 FutureBit miners up. One was the full package the other is plugged in via usb. I got slushpool working then one of my nodes stopped. I’ve tried restarting the proper way and even rebooting the proper way. It’s very frustrating. Now both nodes are not wanting to mine. I am also being patient waiting 15-20mins until the system responds and puts me on the dashboard. I’m at a loss.
Could use some help or if there is a easy mode for updating the Bitcoin miners with out screwing up the proprietary software please let me know. If I don’t hear back, I’ll spend a few days going through the forums.
Update*
Okay I got ckpool Mining but I had to use the whole address. Got the miners cooled off and keeping the temp stable about 50-60. Would like a screenshot of where the web UI update button is. Anyone know if they released a new OS update?
Could use some help or if there is a easy mode for updating the Bitcoin miners with out screwing up the proprietary software please let me know. If I don’t hear back, I’ll spend a few days going through the forums.
Update*
Okay I got ckpool Mining but I had to use the whole address. Got the miners cooled off and keeping the temp stable about 50-60. Would like a screenshot of where the web UI update button is. Anyone know if they released a new OS update?
Anyone with the fan issue just send an email, we have plenty in stock and well send out replacements. Its just a hit or miss with these fans, some die right away and others last years.
Whats the support email address? I tried emailing through the website about the Front LED (which I've subsequently fixed now) but haven't had a reply yet.
I've taken the CPU fan off for now. Not that I'm happy about it but it runs passively at about 60-65c on Balanced mode with a room temp of 18c.
I cannot get the second miner to work. (2x standard units, run by hackintosh running latest ubuntu)
Running start_all produces "Started" but my second miner does not begin to run. Red light continues to flash.
Could this be a worker issue with the pool I'm connecting to? Do I need to differentiate the workers somehow with regards to the pool?
Also, when I try to run "screen" the system tells me there are no screens to display. None of the screen commands yield anything.
Running start_all produces "Started" but my second miner does not begin to run. Red light continues to flash.
Could this be a worker issue with the pool I'm connecting to? Do I need to differentiate the workers somehow with regards to the pool?
Also, when I try to run "screen" the system tells me there are no screens to display. None of the screen commands yield anything.
Hey guys make sure if your connected to the system with the monitor you DO NOT do any system level updates (ie ubuntu asking you to update the kernel etc). Even though we tried to keep the system and 'app" as separate as possible the full node system is still really an embedded system with lots of system level tweaks to make it work. If you update the system lots of these will be will be wiped and youll be left with a bricked system until you reflash the SD card.
Well be issuing updates on the web UI remotely (there will be a yellow update button in the dashboard) you can install whenever they are available, but for system updates please wait until we issue updated SD card images.
Well be issuing updates on the web UI remotely (there will be a yellow update button in the dashboard) you can install whenever they are available, but for system updates please wait until we issue updated SD card images.
Tootall68, my front led doesnt work either. The led has not been soldered properly or been knocked off. Its so small to try and solder on. Ive ordered new iron tips which are smaller and also messaged furturebit asking for the specs for the LED so I can try and replace it.
Did see a couple others mentioned same thing.
Having frustration fun.
The monitor issue was my biggest problem - nothing I have would work until I got the $150 portable 1080p. Weird.
Also, others have reported being unable to "find" or "see" the ipaddress - outside of the dashboard where it shows plain as day. Also Weird.
Yea its all Batch 1 fun. Hopefully a good software update will sort most things. I plugged it straight into my asus 27” monitor (only a year old) and worked fine. Will only come up as 1080p so looks kinda odd compared to my 1440p main pc but still it worked atraight away. IP scanner detected the unit aswell, although it came up as an HTTP address unlike anything else on my network. Once i expanded the option it was designated as futurebit.
EDIT:-
managed to file down a solder tip and resolder the Front LED. Turns out I had it on backwards the first time *facepalm*.
Now unfortunately the CPU fan is making a terrible racket. Tightened it up as Phillipma1957 did with his but its made no difference. Would it be because its a sleeve bearing and being run upside down??
Now getting "internal stats error" even when connected to a monitor and keyboard. A reboot hasnt sorted it. Don't really want to flash the SD Card again if I can help it.
Yep it's the tiny fan on the SBC. I took mine out the other day and bathed it in WD40. Helped somewhat but it's back now albeit intermittent. Like you said; batch 1 issues
Anyone with the fan issue just send an email, we have plenty in stock and well send out replacements. Its just a hit or miss with these fans, some die right away and others last years.
I see these NVMe Internal SSD on sale for prime day
https://www.amazon.com/gp/product/B07YFFX5MD/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1
https://www.amazon.com/gp/product/B07YFFX5MD/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1
Yea we were looking at these WD drives or the crucial. These are great as well and thats a really good price. This is why we didn't want to buy the 1TB drives initially, these would have cost us (and you) 140 to buy back in January.
I see these NVMe Internal SSD on sale for prime day
https://www.amazon.com/gp/product/B07YFFX5MD/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1
And I see an ever better deal at bestbuy
https://www.bestbuy.com/site/crucial-p2-1tb-internal-pcie-gen-3-x4-solid-state-drive-m-2/6432875.p?ref=8575135&loc=86b672fad2ae11eba8729ae98ab22c260INT&acampID=86b672fad2ae11eba8729ae98ab22c260INT&skuId=6432875
https://www.amazon.com/gp/product/B07YFFX5MD/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1
And I see an ever better deal at bestbuy
https://www.bestbuy.com/site/crucial-p2-1tb-internal-pcie-gen-3-x4-solid-state-drive-m-2/6432875.p?ref=8575135&loc=86b672fad2ae11eba8729ae98ab22c260INT&acampID=86b672fad2ae11eba8729ae98ab22c260INT&skuId=6432875
Jump to: