Quote from: jstefanop on September 29, 2022, 04:36:59 PM

Quote from: crypto_curious on September 29, 2022, 06:49:19 AM

Quote from: nyxmercer on September 29, 2022, 01:14:57 AM

Quote from: crypto_curious on September 28, 2022, 03:05:23 PM

Quote from: nyxmercer on September 28, 2022, 02:06:12 PM

Quote from: crypto_curious on September 27, 2022, 09:17:34 PM

Quote from: nyxmercer on September 27, 2022, 06:29:40 PM

Node has stopped running. Appears to be due to storage filling up since it's only a 500gb drive. If I'm not mistaken, the solution is to simply obtain a larger capacity sd card and insert into the bottom of the node unit, yes?

Simplest solution is to enable bitcoind pruning (which is limiting number of blocks to certain value, basically discarding old blocks, so hard drive don't overspill). But Futurebit has not got around to support their users properly - this is nowhere to be found in the settings. They knew the day is coming but did nothing, now all early batch users with 512GB drives running with crashed bitcoin nodes, not providing any benefit to Bitcoin blockchain p2p network, which was heavily advertised during sales.
You are left out, you either have to configure pruning yourself in bitcoind config files inside Apollo, or purchase 1TB NVMe drive, brand new for around 70 USD (in the UK where I live) last time I checked.

So I:

1. Swap the internal drive, which is more annoyance than I'd prefer to deal with..
2. Attempt to modify the software, which is more annoyance than I'd prefer to deal with..
or
3. Ignore the situation and lose out on the money and purpose for buying a node unit to begin with?

Yes, exactly, that's all options you have. As Sledge0001 mentioned, buying new 1TB NVMe drive may be easiest option, but it costs money. Second great alternative option would be Futurebit adding pruning, so you can lose out 20GB of old blocks and still serve 490GB of newer blocks. This interferes with planned in the future Lightning Node support, but LN support is nowhere at the moment.
But unfortunately, because Futurebit did nothing to prevent this, we now arrived at option no. 3, where ALL nodes from 512GB users just crashed and no one is serving any blocks to Bitcoin network, and no one (apart from few here in this thread) even knows why, because there was no announcement or warning to users, no newsletter, mailing, nothing. Every node just dead.

Edit: Before someone mentions this issue, to my knowledge pruned node are seeding blocks, and they are considered as "full nodes": https://bitcoin.stackexchange.com/questions/72617/how-can-a-pruned-node-be-classed-a-full-node-without-the-full-blockchain says:

Quote

Since, they don't keep older block data, only thing that they can't do is to return older block data to other nodes. They still keep latest block data for reogranization, which they can share with other nodes

Amused. Just got an email from FutureBit perfectly explaining how to upgrade the drive.

At your own cost, of course. No pruning in sight.
And I received no e-mail whatsoever, so I assume it was you who contacted them, and another thousand of users get nothing.

Everyone that ordered a Batch 1 or 2 should have received the email. I will not advocate or push an update for pruned nodes, a pruned node is the same as a dead node in my eyes.

As has been discussed extensively since the beginning, we purposely chose a 500GB drive knowing people would have to swap the drive out in 1-2 years because we knew prices would be a fraction of what we would have had to charge for Batch 1-2 devices with a 1TB drive and that was the right choice then and is the right choice now. We would have had to charge an extra 150 at the time for the 1TB drive, 1TB drives are now 75 and will end up costing you less than 50 if you sell your 500GB drive. I think this is the better decision all around, and swapping out the drive and setting it up takes 5 minutes.

You made the right choice. I appreciated the cost saving for less than an hour of my time buying then swapping the drive and setting it up again