You are tempting me to verify with support that ‘Safely detatching’ and ‘scanning and recovering’ works as described and has for me MANY times, all but the one failure I detailed, and I bet support could have tweaked that one without restore if I was willing to wait. My last discussion with them on this, they said to look at the model migration matrix; if model migration is supported, moving a ‘safely detached’ data pool from one nas to be ‘scanned and recovered’ and attached to the different nas is supported as well.
Actual model migration of a pool flagged “(System)” (or QTS pool with volume flagged “(System)”) will prompt for firmware re-install if model and/or OS version differs from what target was initialized with.
Based on doubts you express, I’m tempted to confirm with support that your issues of concern are in fact addressed by proper use of ‘safely detachl’ and ‘scan and recover’.
While burned once with my 'DOCUMENTED" use of detach/upgrade/recover, I’ll stick with it as my whole reason for doing it was at least 5, probably more total reinitialze/restores that were forced by buggy firmware uprades and buggy upgrades to unwanted uninstallable applications in years prior to the availability of the ‘safely detach’/‘scan recover’ functionality.