If you can’t activate Xsan on a primary MDC after you migrate to a new Mac
Check to see if the Universally Unique Identifiers (UUIDs) from your Xsan and hardware match. If they don’t, correct the Xsan UUID.
To activate Xsan on the primary metadata controller (MDC) after migrating to a new Mac:
Launch Server app and turn on Xsan.
Select “Restore a previous SAN configuration” and click Next.
If you click Next and the restore process doesn't start, try the steps below.
Check the UUID values
1. Enter this Terminal command:
/usr/libexec/PlistBuddy -c "print primaryController" /Library/Preferences/Xsan/config.plist
If you see a UUID, continue to step 2.
If you see this output, or don’t see any output, this article doesn’t apply to your Xsan:
Print: Entry, "primaryController", Does Not Exist
2. Enter this Terminal command:
system_profiler SPHardwareDataType
3. Check to see if the UUID values from both commands match.
If the UUID values match, this article doesn’t apply to your Xsan.
If the UUIDs don’t match, you should be able to correct your Xsan UUID by creating a new UUID file.
Create a UUID file
1. Enter this Terminal command:
sudo sh -c "printf `/usr/libexec/PlistBuddy -c "print primaryController" /Library/Preferences/Xsan/config.plist` > /Library/Preferences/Xsan/uuid"
2. Activate your Xsan.
If you used different steps to create your UUID file, make sure that it doesn't end in a new line character. Some text editing tools add a new line character at the end of a file.