- completely deinstall dphys-swapfile - one could only deactivate it, but after rebooting swapping would be active again.
Swapping is a bad idea, at least on an SD-card, because when your memory gets exhausted and the card starts swapping data, it only furthers the slowdown until at a certain point your wallet cannot stay synced and either shuts down or gets unresponsive and you need to kill the process. It could also get worse and your hole system gets unresponsive and you need to pull the power-plug to shut it down and reboot.
So if you would need to swap on your SBC, because memory gets exhausted, you better use a SBC with more accessible memory instead of using a swapfile.
-I use a minimal installation (Raspbian minimal for the RPi) and compile the daemon, not the qt-wallet.
Lesser processes means lesser read/write cycles.
-When starting the daemon, I use '-printtoconsole > /dev/zero'. There is ofcourse no log at all, but that is exactly what I want anyways.
Really excellent points. I agree 100%. Tried to use '-printtoconsole > /dev/zero', but I need those logs, so turned them back eventually.
Then again, Sandisk cards are the best cards on the market, period. We didn't test all brands for sure, but have tested many and Sandisk is unmatched. You will run Sandisk much longer than any other brand, before it gets corrupted.
One question though - it looks like you run only one staking wallet on that SBC - that may be the reason why your card is still working after a year. I tend to run as many wallets as RAM/Storage allow - at least 4 per device, and that could contribute to the SD card damage.
In any case, my conclusion after several tests is the following: if someone runs many staking wallets, the most economical and safe way is to run many SBC's connected to a switch, where you also have one SBC with relatively big HDD connected and shared via NFS. You will run just a single HDD (power consumption is pretty low for a single HDD, or moreover SSD), but can run as many staking wallets as you want.