Indeed. Thanks for the backup advice. My mix of problems was different and an interesting object lesson.
It started with an SSD seeming to fail, and I ordered a new one, but before it arrived, magically the old one started up again, and I carelessly assumed that my backup was working, so when it failed permanently, I would pop in the new SSD and restore from backup. So when the day came, and I put in the new SSD, I was not able to reinstall the operating system (Linux Mint), and it took me a while to figure out with help of usergroup feedback to identify that I probably needed a Mobo bios upgrade. ASUS promptly gave me the wrong instructions, and I bricked my mobo. I am in an RMA process with them now (no, don't ask how well that is doing), and by that time, I ordered a new computer, for I was working with a meagre Surface tablet as a backup, which was tiresome, and there was no end in sight. When the new system arrived, I quickly found out there were holes in my backups (I had two going), in part because of configuration errors, but in part also for as yet unexplained mysteries. In any case, by this time it was necessary to send in my old SSD for data recovery, which worked, but it was a painful exercise all by itself. It took them 6 weeks for unclear reasons, but eventually I was able to restore everything. Now I am working on a new, and hopefully more robust backup strategy, while also doing a synching exercise, so I can work remorely. On Fri, Sep 15, 2023 at 11:06 AM Michael or Penny Novack < stepbystepf...@comcast.net> wrote: > On 9/14/2023 8:25 PM, Rogier F. van Vlissingen wrote: > > I had a disastrous disk crash, and on top of that a backup that appeared > to > > have holes in it, so I was up a creek without the infamous paddle. > > > > Now recovering, and I feel like a stranger in my own house. Just looking > at > > my GNUCash files (I have one company for three years in Gnucash, I simply > > do not know by which file to open GNUCash and could not find guidance in > > the Help file. > > > > Any ideas? > > But you presumably have a much larger problem than recovering just > gnucash. I am assuming that you did other things with this computer than > just gnucash. As a retired professional who once had to attempt recovery > after a house fire when backups be in the same building and the data > recovery lab couldn't recover everything I do have some suggestions. > > a) File by file recovery should be your last resort. What directories > (file folders) appear to be intact on the back-up media? If you can, you > should..... > > b) You FIRST check if your user data directory is intact. If so, you > restore that and should be done. If that has holes.... > > c) You look for directories within it that are still good. It's only > after restoring those and finding stuff you need not restored that you > go down to lower levels. > > Now this assumes that you do have FULL data back-ups. If you were using > some "file by file" back-up software for day to day recovery (I messed > up a file, give me back the previous version) you need to remember that > this sort of back-up is not really intended for recovery from a fatal > disk crash, house fire, etc. You should in addition be doing at least > periodic full data back-ups. > > That, of course might be closing the barn door advice. But keep in mind > for future. > > Michael D Novack > > > _______________________________________________ > gnucash-user mailing list > gnucash-user@gnucash.org > To update your subscription preferences or to unsubscribe: > https://lists.gnucash.org/mailman/listinfo/gnucash-user > ----- > Please remember to CC this list on all your replies. > You can do this by using Reply-To-List or Reply-All. > _______________________________________________ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user ----- Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
