I had a couple issues upgrading from 0.21 to 0.35.
I did the following:
- Imported my old config which seemed to work fine. I did not try running an update.
- I was replacing my parity drive with a larger one so I changed the parity path to the new drive.
- I added my old parity drive to the pool as I will eventually use it for data now. All my drives are added using a sub folder called "Protected" so this folder was empty on this new drive and had no updates or deletes. I still had my old parity data outside of the protected folder just in-case the rebuild went wrong. My plan is to delete it once the rebuild is complete.
- Clicked "Update All" and it starting running. Only the first drive's progress bar was moving which was I thought was strange but I let it run anyway. 12 hours later it was finished the first drive and working on the next drive but I noticed it was re-writing each parity file again! I could see the date modified of the first parity file (parity0.dat) was changed 10 hours after I started the update.
- I cancelled the update because it was going to take days at this point. I tried restarting the program, running the update again, reconfiguring the setting but nothing helped. It always seemed to run on a single drive.
- Next I clicked reset and tried again but it kept getting an error saying files0.dat did not exist.
- I eventually removed my old parity drive (which was empty, 0 files) from the pool and tried resetting it again, then updating it seems to be working. All drives have progress bars and it is currently building a new parity set.
I will let you know if it works once it is complete. It seems there might be a bug with a drive that has either has no files on it or a drive that is "Up to date" when rebuilding your parity data. Not sure which one it is.