I have been trying to do this for years without much success. I was wondering whether in the mean time a good solution has come out.
The title says it all, this is my setup:
- NTFS partition with “Drive” folder
- Win 7 with Insync 1.2.x
- Linux Mint with Insync 1.2.x
- Either Win OR Linux access drive at one time (dual boot)
What I have tried:
- Setting up each copy of Insync on the respective OS => does not work (files get downloaded twice etc.). This is expected.
- Use a symlink in Linux (in Insync config dir) to point to the “Windows” db files (“config.db” and “gd2-123456789.db”). In this way Insync only has “one configuration” and files do not get downloaded twice. This works in principle BUT:
a. When switching between OSs Insync cannot find the “root folder” and asks to locate it manually (given the different structure of Linux and Win file system a common name cannot be chosen). This is totally acceptable and not much work.
b. Once in a while another error comes up “Initialization failed!” and no further action is possible, apart from setting up the account again (which of course triggers a new download of the whole drive and requires an empty folder). Booting into the other OS and launching Insync with a backup copy of the db files usually solves the problem. It seems like the db files occasionally get corrupted, so I regularly back them up.
Do you have any suggestions? Is there an “official” way to handle dual-booting with Insync? I think this should be a rather common issue.
Also what is the content/function of the two db files? I would think config.db holds information like location of drive folder etc. This doesn’t seem to be true as only simlinking the other db file (keeping the “OS native” config.db) did not avoid the “root not found” problem.
Thanks for any help. Solving this problem would make Insync almost perfect for me