This discussion is locked
Cornelius Qualley

Q: Volume mounting, but missing from Server app

After reconfiguring my MDC (which had something screwed up in OD), I'm having an issue with my Xsan volume listing in Server app. It shows that Xsan is up and running, but the volumes window is blank. I was able to successfully add a backup MDC and they both are able to find each other without issue, however neither the MDC or backup MDC show the volume in the window. They do, however, both mount the volume without issue.

 

There is one issue, that I know of, that I'm pretty sure this is causing an issue for. Whenever I add the profile to a new client machine the volume does not mount without forcing a mount using "xsanctl mount Media". Once mounted, there are no problems that I can tell, however I haven't used it with this issue long enough to tell. Essentially it seems like it can find the volume, it just doesn't know that it's available without telling it to look for it. I've searched for a long time to try to find a config file that may control this behavior, but I can't identify anything yet. If anyone knows what file controls the display of the volumes or how to fix this issue I would appreciate the help. Also, I already have 25TB on this volume so destroying/recreating it is not really an option I would like to explore.

Posted on Jan 21, 2015 8:53 AM

Close

Q: Volume mounting, but missing from Server app

  • All replies
  • Helpful answers

  • by Claudio Sanchez1,Solvedanswer

    Claudio Sanchez1 Claudio Sanchez1 Jan 23, 2015 9:15 PM in response to Cornelius Qualley
    Level 1 (65 points)
    Jan 23, 2015 9:15 PM in response to Cornelius Qualley

    It would seem that the Xsan configuration stored in LDAP does not include your volume. You could try these steps to resync the configuration files stored in /Library/Preferences/Xsan and the configuration in LDAP:

    1. Important: Make a backup copy of the /Library/Preferences/Xsan directory on each MDC.

      If I'm right about LDAP not including your volume, the secondary won't have any .cfgp file in its /Library/Preferences/Xsan directory--unless you put it there.

    2. Remove the secondary MDC from the SAN.

    3. On the primary MDC:

      1. Check that your volume name appears in /Library/Preferences/Xsan/fsmlist. See the fsmlist(4) man page for details. You will have to use the full path to that man page, e.g. "man /System/Library/Filesystems/acfs.fs/Contents/man/man4/fsmlist.4".

      2. Update the LDAP configuration with: "sudo xsanctl pushConfigUpdate". See the xsanctl(8) man page for more information. ("man xsanctl")

        Your existing volumes should reappear in Server app when you do this. You may need to do command-R to refresh the view. If you don't see your volume, review the output of "xsanctl pushConfigUpdate" to see if it explains what failed.

    4. Add the secondary MDC back to the SAN.

      Assuming pushConfigUpdate worked, the secondary MDC should automatically mount your volume when you add it. The same should happen for any additional clients you add to the SAN.

  • by Cornelius Qualley,

    Cornelius Qualley Cornelius Qualley Jan 24, 2015 7:23 AM in response to Claudio Sanchez1
    Level 2 (300 points)
    Jan 24, 2015 7:23 AM in response to Claudio Sanchez1

    Thanks for the help, I really appreciate it! I'll give that a try shortly and report back the results.

  • by Cornelius Qualley,

    Cornelius Qualley Cornelius Qualley Jan 27, 2015 7:59 AM in response to Claudio Sanchez1
    Level 2 (300 points)
    Jan 27, 2015 7:59 AM in response to Claudio Sanchez1

    That solved my issue! I really appreciate the help, it saved me a bunch of time and now everything is working like normal! THANKS!