Here's an example: https://github.com/ethereum/go-ethereum/issues/16237
,,Seems like it does indeed proceed but very slowly. After 12 days on the 96gig ram machine I am finally at block 4732597... I will report back how long it takes to finish.''
You can run a full node that verifies everything on an ongoing basis without doing a full sync from the genesis block - just start it in fast sync, let the chain catch up, and then run it again in full mode. Unless you believe the Ethereum blockchain has already been compromised, there's no reason why your personal node has to verify everything from the genesis block.
Geth CLI options: https://github.com/ethereum/go-ethereum/wiki/Command-Line-Op...
Understand the differences between syncing, validating, and pruning, then it becomes simpler... https://github.com/ethereum/go-ethereum/pull/1889 https://github.com/ethereum/go-ethereum/wiki/Tracing:-Introd...
The SSD vs. hard disk distinction is key. I ran into the "it will literally never complete" issue trying to sync to an external HD on my home MBP - I ran it for about a week and it didn't work. Tried parity as well, same result. Once I decided I'd just rent a big SSD from Amazon I had no problem.