 Show Posts
|
|
Pages: [1] 2 »
|
|
Thanks for the nice picture. Had you read the post carefully, you would have seen that's it's for TWO units.
|
|
|
|
|
For Sale: Full FutureBit Apollo BTC Package - Desktop Class Controller with 1TB NVMe Drive with 200W PSU plus a Standard USB Controlled Hashboard with 200W PSU.
$1200 + shipping
DM or email to contact
|
|
|
|
|
I am selling my FutureBit miners. Is there an appropriate forum to post on this site? --Thanks
|
|
|
|
I restored my configuration from a backup. The node is up and downloading the blockchain. The miner is up, but inactive and the original pool information seems to be stuck in the settings, despite changing to my new one. Any ideas? Thanks!
Try restarting in the miner software. Seems a hard restart sometimes does not restart right That did it, thank you. I'll let it run in eco mode until the chain syncs-up. To upgrade to a larger M.2 SSD without an enclosure, I first got a second SD card and imaged it using the resources from the first post. That was more of a precaution than a necessity. Then, since my node was fully in sync on the original SSD, before I replaced the M.2 SSD I use the full node's file manager app to connect to a valid SMB file-share target on my home network and copied the node's data-files to it. It's way faster copying ~400 GB of data on your home network than it is to wait for the node to re-sync from scratch. Then I shut everything off and replaced both the SD card and the M.2 SSD. Upon bootup the OS formats the M.2 and starts to sync the node, which will take days. So, that's the time to stop the node, reconnect to the file-share and copy the data-files you backed up onto the new SSD, overwriting whatever the node just recently created with what we know to be complete data files. Then all ya have to do is re-start the node and it'll sync any changes that occurred while you were working on the full unit. That'll take minutes, as opposed to days. HTH Sorry for the late reply. Thanks for the share, but I just let the node synch on its own in ECO mode. Good to know if a drive ever lets go. --C |
|
|
|
I restored my configuration from a backup. The node is up and downloading the blockchain. The miner is up, but inactive and the original pool information seems to be stuck in the settings, despite changing to my new one. Any ideas? Thanks!
Try restarting in the miner software. Seems a hard restart sometimes does not restart right That did it, thank you. I'll let it run in eco mode until the chain syncs-up. |
|
|
|
|
I restored my configuration from a backup. The node is up and downloading the blockchain. The miner is up, but inactive and the original pool information seems to be stuck in the settings, despite changing to my new one. Any ideas? Thanks!
|
|
|
|
Literally swap them out. You can clone the data so you don't have to resync the blockchain but if you have a decent internet connection I'd just let it go redownloading everything from scratch
Hey, thanks. I have gigabit service to the house and I believe my initial sync took a few days. I can get the ssd for $89. The cloning device adds another $100 to the bill - and I only received my miner last month. I don't need to format or anything? I was under the impression that the image needed to be installed first. Just reflash the image to stock state, then put the freshly imaged SD card and new SSD and it will auto formate and set everything up. Well have a button in settings that does this instead of needed to reflash in the next update. Well, reflashed the SD with the appropriate image using Balena Etcher. Installed new SSD and re-inserted SD. Put power to the unit and it appears to have booted and the indicator light is flashing at the proper cadence. I am currently unable to access the dashboard or SSH in to the IP. Is there a considerable wait time for the dash to reappear as the new drive is being formatted? IP might have changed. Did you get IP from router? Same, or new IP? If it reports as online and active in your router, you should be able to connect it immediately. That was it. I had a static IP assigned via Wifi. I just got in via Ethernet. Thanks for the reply. |
|
|
|
Literally swap them out. You can clone the data so you don't have to resync the blockchain but if you have a decent internet connection I'd just let it go redownloading everything from scratch
Hey, thanks. I have gigabit service to the house and I believe my initial sync took a few days. I can get the ssd for $89. The cloning device adds another $100 to the bill - and I only received my miner last month. I don't need to format or anything? I was under the impression that the image needed to be installed first. Just reflash the image to stock state, then put the freshly imaged SD card and new SSD and it will auto formate and set everything up. Well have a button in settings that does this instead of needed to reflash in the next update. Well, reflashed the SD with the appropriate image using Balena Etcher. Installed new SSD and re-inserted SD. Put power to the unit and it appears to have booted and the indicator light is flashing at the proper cadence. I am currently unable to access the dashboard or SSH in to the IP. Is there a considerable wait time for the dash to reappear as the new drive is being formatted? |
|
|
|
Literally swap them out. You can clone the data so you don't have to resync the blockchain but if you have a decent internet connection I'd just let it go redownloading everything from scratch
Hey, thanks. I have gigabit service to the house and I believe my initial sync took a few days. I can get the ssd for $89. The cloning device adds another $100 to the bill - and I only received my miner last month. I don't need to format or anything? I was under the impression that the image needed to be installed first. |
|
|
|
Looks like my node needs to have its drive upgraded since I only have 12.2% remaining as the blockchain consumes 421.23 GB. Can anyone provide me with some guidance as to what drive to purchase and perhaps some instructions on how to set it up? Many thanks, -C EDIT: I found https://bitcointalk.org/index.php?topic=5340015.msg57091052#msg57091052 at the beginning of this thread. Is that all there is? I'm assuming I need to wait a bit for the blockchain to reload or use a cloner. Still a little unclear. |
|
|
|
Port forwarding is tied to specific internal IP address, if you switch to wifi youll get another IP address which will break that port forward. There are router settings that will tie your device to a specific IP address though.
BTW now that both Batch 1 and 2 are shipped open those ports up! Very few public Apollo nodes, we should be the #1 or #2 node on the network by now!
Hi John - Static IPs were assigned in both cases and the rules were modified to ensure the port allocation was tied to the appropriate IP for the machine. Apparently, for some odd reason, I no longer see the error. Perhaps it took time for the inbound/outbound assignment to stick (which is weird). Either way, the node is currently at 31/32 connections with no errors, so I'll take it. No real difference noted on the pool's (slushpool) hashrate since switching to WiFi... Perhaps a smidge lower. Thanks again! --c |
|
|
|
|
Here’s a weird one… I moved my node into another room and turned on Wi-Fi. Now, whenever my connections exceed 15-16, I receive the following error on the dashboard: Only inbound connections detected, please enable port 8333 on your router port forwarding rules for your Apollo IP address.
I’m using the same rules as what I had set when I was connected via LAN which, when connected, gave me the maximum connections.
The port is open bi-directional in my router.
Any ideas?
Thanks!
-c
|
|
|
|
1. The Temp top left is the CPU temp. The temp in the hashboard section is the hashboard temp.
2. HW Errors will fluctuate but the longer the unit is on the more stable they become. 0.4-0.9 is perfectly acceptable.
3. Running via Wifi shouldn't effect performance at all, but it all depends on signal strength and other factors which interrupt that signal. Its always best to run an ethernet cable where possible.
Hey, thanks so much for the quick reply. I appreciate the temp clarification and figured it had to be something else. Makes sense the CPU was high when I put it in turbo for about an hour during synch. Good to know about #2. As for Wifi, I want to place the unit (+new one once it arrives) into an adjacent room next to the router. If I see a degradation, it's a short cable run into it. I want to keep it in my home office, but I found the sound of the fan to be like white noise... It drowns out quiet background music and puts me to sleep.  Take care and thanks again! |
|
|
|
|
@jstefanop / anybody:
1- Can you please tell me the difference between the two temperature readings on the dashboard? (hashboard and number at top left) and;
2- Hardware errors on the dash bounce between 0.4-0.9. Why is that? Lastly;
3 - I'm currently connected via Ethernet with the entire blockchain on the node. Would running it via WiFi degrade my hashing / pooling numbers?
Thanks in advance for your help as I seek to learn more about this great little miner.
--C
|
|
|
|
Well I thought I had it but I havent. Miner restarted and now stuck at 10 connections again. I've checked the port is open with various checkers online and the IP address for the Apollo is static. Also allowed port access with my firewall (not that it should affect the router I suppose as its on my main PC). But still its stuck at 10 connections.
Did you ever solve this? I just got my device, port forwarded 8333 and cannot get above 10 connections. It's ramps right up and hit that 10 ceiling. Are you done synchronizing with the blockchain? If not, that is probably why. Let the node fully synch and see what happens. |
|
|
|
One other question: My BTC is running on turbo. The hashboard shows:
HASHBOARD #0
Hashrate 3.12 Th/s
Temp 68°c
Fan Speed 2828 rpm
Power 202 W
Voltage 8.26 v
Error 0.9%
Active ASICs 44
However, the hashrate is 3.10 Th/s and the temp is 81.67°c at the top left of the dashboard.
While I'm inclined to believe the lower number, he top number has me worried. Any guidance?
Thanks!
Are you running node? in case node sync you might see high temp SBC comp? I believe recommendation while node in sync don't run turbo. Yeah, I was running it in turbo mode for about an hour while the last tenth of a percent of the blockchain was synchronizing. Rookie mistake that could've cost me my hardware. Everything is all caught-up, I have 29/32 connections with the following stats: HASHBOARD #0 Hashrate 3.03 Th/s Temp 66°c Fan Speed 2823 rpm Power 203 W Voltage 8.31v Error 0.9% Active ASICs 44 The temp is 60.00°c at the top left of the dashboard. What is the difference between the two temperatures? Different components? |
|
|
|
|
One other question: My BTC is running on turbo. The hashboard shows:
HASHBOARD #0
Hashrate 3.12 Th/s
Temp 68°c
Fan Speed 2828 rpm
Power 202 W
Voltage 8.26 v
Error 0.9%
Active ASICs 44
However, the hashrate is 3.10 Th/s and the temp is 81.67°c at the top left of the dashboard.
While I'm inclined to believe the lower number, he top number has me worried. Any guidance?
Thanks!
|
|
|
|
Wait for the worker named '[Auto]' scoring hash rate to drop from 123.7M/hs to zero/... then tick/click the little box next to its name, should come up with the option to edit, delete worker or cancel; click delete and confirm. Hey, thanks so much. I will watch for it. :EDIT: It worked! |
|
|
|
|
