when I formatted it there was not a "FAT32" option. there was two choices "exFAT" and "NTFS" -- I assumed that "exFAT" was just a stupid windows 10 thing.
as for SSH I cannot figure it out for the Apollo I run putty, put in the ip address and when it comes up with user name - I dont know what to enter as I dont enter a user name when i log into the Apollo - so I have tried to just hit enter and enter the Apollo's PW but Putty always tells me its the wrong password.
second edit: I tried to use command prompt, diskpart, list disk, list volume, select volume 7 (that is the jump drive), format fs=FAT32 override (tried the override command to see if it would trump the limit of 32 gb) but it states that I cannot format the drive to FAT32 because the size of the drive is too big
Here is a workaround for windows 10
https://www.howtogeek.com/316977/how-to-format-usb-drives-larger-than-32gb-with-fat32-on-windows/trying the first method on that page - it formatted it super quick and properties now show it as FAT32
copying over the "blocks" and the "chainstate" now
update:
did get it formatted as FAT32 - thanks for the link!
Created folder called Litecoin and copied my "blocks" and "chainstate" folders from my litecoin node folder over to the Litecoin folder I created on the jump drive.
shut off Apollo, plugged in the jump drive, started node - after 30 mins or so, I got the node offline message. Tried to start it again and got the message again that node is offline.
update:
it went a little further this round - gave me a "Loading block index..." but then after 15 mins showed "node is offline" so I am shutting it down, wiping the USB drive and starting over again.
update:
so while it is copying the folders over again. I tried to figure out the ssh and found the post that gave the credentials - for some reason, I thought it would be my credentials to log into the miner lol
so as asked, here is what it shows when I run "systemctl status node"
Last login: Fri Apr 24 04:23:49 2020 from 192.168.1.242
futurebit@futurebit:~$ systemctl status node
● node.service - node
Loaded: loaded (/etc/systemd/system/node.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2020-04-24 03:32:07 UTC; 54min ago
Process: 29387 ExecStop=/etc/node_stop.sh (code=exited, status=1/FAILURE)
Process: 27392 ExecStart=/etc/node_start.sh (code=exited, status=0/SUCCESS)
Main PID: 27646 (code=exited, status=0/SUCCESS)
Apr 24 03:29:30 futurebit systemd[1]: Starting node...
Apr 24 03:29:50 futurebit systemd[1]: Started node.
Apr 24 03:32:07 futurebit node_stop.sh[29387]: No screen session found.
Apr 24 03:32:07 futurebit systemd[1]: node.service: Control process exited, code=exited status=1
Apr 24 03:32:07 futurebit systemd[1]: node.service: Unit entered failed state.
Apr 24 03:32:07 futurebit systemd[1]: node.service: Failed with result 'exit-code'.
futurebit@futurebit:~$
update:
ok drive is reformatted - FAT32 confirmed, "blocks" and "chainstate" folders copied over to the "Litecoin" folder in the drives root directory. Plugged in usb drive to Apollo and hit "start" on the node menu. Let's see what happens now
update:
this time around, I got the "rewinding blocks" and "verifying blocks" messages - had not seen these before so progress right?
here is what ssh shows:
Apr 24 04:38:11 futurebit systemd[1]: Starting node...
Apr 24 04:40:41 futurebit systemd[1]: Started node.
futurebit@futurebit:~$ systemctl status node
● node.service - node
Loaded: loaded (/etc/systemd/system/node.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2020-04-24 04:40:41 UTC; 3min 23s ago
Process: 29387 ExecStop=/etc/node_stop.sh (code=exited, status=1/FAILURE)
Process: 15253 ExecStart=/etc/node_start.sh (code=exited, status=0/SUCCESS)
Main PID: 17151 (screen)
CGroup: /system.slice/node.service
├─17151 SCREEN -dmS node /opt/bin/litecoind -datadir=/media/usb/Litecoin -conf=/opt/litecoin.conf
└─17152 /opt/bin/litecoind -datadir=/media/usb/Litecoin -conf=/opt/litecoin.conf
Apr 24 04:38:11 futurebit systemd[1]: Starting node...
Apr 24 04:40:41 futurebit systemd[1]: Started node.
futurebit@futurebit:~$
update:
and success, the dashboard loaded! but I had no connections - I think the issue is that I have port 9333 forwarded for the node that runs on my PC - I had to remove that port forward from the pc's ip address and set it for the Apollo's ip address. Rebooting node and will see if that resolves it.
update:
after I shut down node, it gave me an error about displaying stats. I should have taken a screenshot and will if I see it again. I simply restarted the Apollo and once in hit start on the node - while waiting, the apollo has shut down twice - each time I have to restart the node. putty cannot get in to the miner while this is happening either. I am tired and going to bed - I get up in 4 hours for work. After I get going at work, I will revisit this again.
final update:
as you would have it, I was walking away and the Apollo shut down. So, of course I turned around and sat back down. This time the node restarted itself upon booting up - maybe that was the issue? the last two times it restarted, I was hitting start on the node instead of letting it do itself.
I have 12 connections however, my full node/wallet has only 8 (the standard outbound) due to the port forwarding issue - anyone know of a solution so I can run both nodes?
