However, when the drive is mounted again, the location should resolve. It’s possible the drive mounted with a different name, like myDrive 1, in which case, the absolute path would not be resolved. Check /Volumes.
My frustration is that we are issued the same standard warning even when the outcomes are dramatically different and the dangerous option could likely have been detected in advance.
–> This operation rebuilds your database. (rest of standard warning) Do you want to proceed?
–> The source to rebuild the database is missing or invalid. A rebuild operation will result in an empty database. Do you want to proceed?
This mounts specifically at /Volumes/Workspace as a folder inside that volume.
It does not just simply resolve. I have to index the data folder again. Only then do I get back the indexed file list.
Edit: It does not matter against the strength of my concern. It may have been accidental. It may have been ignorance. It may have been to test the fail safe of DTP before I commit (and in truth, it was somewhat this Maxwell’s demon in me).