There is a bunch of times I have opened my wallet (on win 7, 10 and my Pi) and found my wallet file has become corrupted, at least I think it is, only copying over a new wallet file seems to fix the error, I have found this to be a consistent problem during power failures of my devices. Is there a way I can stop this from happening or is there a Fix devs can do that will stop this, I have never had this problem with any other coin wallet before dispite having run thus far at least 20-30 wallets of different coins at times over the last 3-4 years... thanks guys.
There is a bunch of times I have opened my wallet (on win 7, 10 and my Pi) and found my wallet file has become corrupted, at least I think it is, only copying over a new wallet file seems to fix the error, I have found this to be a consistent problem during power failures of my devices. Is there a way I can stop this from happening or is there a Fix devs can do that will stop this, I have never had this problem with any other coin wallet before dispite having run thus far at least 20-30 wallets of different coins at times over the last 3-4 years... thanks guys.
Happen to me once, I fixed it by just using the installer and reinstall OK, restarted my comp and all was working again. (yes happened during power failure too)
For windoze: read the nice article at HowToGeek
http://www.howtogeek.com/howto/windows-vista/guide-to-using-check-disk-in-windows-vista/or
- restart in "Safe mode with command prompt only" and run
chkdsk /R /F C:
Answer with "Y" (for "Yes") at the prompt of scheduling scan at the next reboot,
- then reboot with
shutdown -r -t 0
For Linux: read the nice article at MakeTechEasyer
https://www.maketecheasier.com/check-repair-filesystem-fsck-linux/and follow your frontal cortex's lead
It would be best not to get your filesystem(s) corrupted in the first place. That can be achieved by eliminating as many causes of forced restarts and/or shutdowns: power failures, inappropriate user action, "bad" software executed with administrative privileges... and so on.
Another major cause for filesystem corruption is the media itself. Low cost HDDs can cost you more than their price tag if you store significant informations on them and forget to backup... Low cost SSDs might have bugs in controller's firmware and/or much less write cycles than regular or premium models...
Bottom line is: devs can't really do much in that regard if the user doesn't protect it's filesystem(s) properly, they can perform time-consuming checks and/or reindexing, they can force an even more time-consuming sync either from scratch or by a bootstrap (big question of trust here), but that's about all I can think of.
As far as I am concerned, this problem is PEBCAK. Oh, well, we all should use more resilient hardware and filesystems and pay only fractions of cents (if ever), right?