Recent Comments

  • Reply to: Xsan - Cant add clients, tried everything.   1 day 19 hours ago

    I have upgraded my servers and clients from Maverick to Yosemite, but the client no mount san volumes.
    When I load profile on client, I have this error log:

    Mar 29 12:49:44 edit4.fish.pvt mdmclient[2803]: trimming ldaps://, made 'fcs.fish.pvt:389'
    Mar 29 12:49:45 edit4.fish.pvt mdmclient[2803]: loadControllerCerts called on mdc.fish.pvt:389
    Mar 29 12:49:45 edit4.fish.pvt mdmclient[2803]: profileLoad passing in {
    sanAuthMethod = "auth_secret";
    sanConfigURLs = (
    "ldaps://mdc.fish.pvt:389",
    "ldaps://fcs.fish.pvt:389"
    );
    sanName = "My Xsan";
    sharedSecret = "********";
    }
    Mar 29 12:49:45 edit4.fish.pvt mdmclient[2803]: checkSanConfigChange passed newConfig {
    configIsNew = "";
    sanAuthMethod = "auth_secret";
    sanConfigURLs = (
    "ldaps://mdc.fish.pvt:389",
    "ldaps://fcs.fish.pvt:389"
    );
    sanName = "My Xsan";
    sharedSecret = "********";
    }
    and old config
    {
    }
    Mar 29 12:49:45 edit4.fish.pvt mdmclient[2803]: Unable to contact node ldaps://mdc.fish.pvt:389
    Mar 29 12:49:45 edit4.fish.pvt mdmclient[2803]: Unable to contact node ldaps://fcs.fish.pvt:389
    Mar 29 12:49:45 edit4.fish.pvt mdmclient[2803]: NodeChecking hated all of it
    Mar 29 12:49:45 edit4.fish.pvt mdmclient[2803]: profileLoad got cC 40
    Mar 29 12:49:45 edit4 com.apple.xpc.launchd[1] (com.apple.xsan): Unknown key for Boolean: ForceEnableHack
    Mar 29 12:49:45 edit4 com.apple.xpc.launchd[1] (com.apple.xsan): The HopefullyExitsLast key is no longer respected. Please remove it.
    Mar 29 12:49:45 edit4 com.apple.xpc.launchd[1] (com.apple.xsan): Please switch away from OnDemand to KeepAlive.
    Mar 29 12:49:45 edit4 com.apple.xpc.launchd[1] (com.apple.xsan): The ServiceIPC key is no longer respected. Please remove it.
    Mar 29 12:49:45 edit4 com.apple.xpc.launchd[1] (com.apple.xsan): The IgnoreProcessGroupAtShutdown key is not yet implemented. If you rely on this key, please file a bug.
    Mar 29 12:49:45 edit4 com.apple.xpc.launchd[1] (com.apple.xsandaily): Unknown key for Boolean: ForceEnableHack
    Mar 29 12:49:45 edit4.fish.pvt xsand[2804]: kern.coredump: 1 -> 1
    Mar 29 12:49:45 edit4.fish.pvt xsand[2804]: kern.corefile: '/cores/core.%P' -> '/cores/core.%N.%P'
    Mar 29 12:49:45 edit4.fish.pvt xsand[2804]: kern.ipc.maxsockbuf: Result too large
    Mar 29 12:49:45 edit4.fish.pvt xsand[2804]: checkSanConfigChange passed newConfig {
    }
    and old config
    {
    }
    Mar 29 12:49:45 edit4.fish.pvt mdmclient[2803]: [Daemon:0] Installed configuration profile: Xsan Configuration Profile (com.apple.xsan.112:CB8EB501-C676-415B-BCCC-0EBC1495A388) for
    Mar 29 12:49:45 edit4 kernel[0]: Xsan Revision 4.3.2 Build 546.1[30118] Branch Head Built for Darwin 14.0 x86_64 Created on Sun Nov 16 15:05:58 PST 2014
    Mar 29 12:49:45 edit4.fish.pvt xsand[2804]: xsand_setup_SpotlightServer starting
    Mar 29 12:49:45 edit4.fish.pvt xsand[2804]: xsand_setup_SpotlightServer about to ioctl. flags 0
    Mar 29 12:49:45 edit4.fish.pvt xsand[2804]: xsand_setup_SpotlightServer did ioctl.
    Mar 29 12:49:45 edit4.fish.pvt xsand[2804]: xsand_setup_SpotlightServer done
    Mar 29 12:49:45 edit4.fish.pvt xsand[2804]: No fsnameservers file; deferring MDC reachability checks

    I checked ThomasB's points and they are ok.
    The only remaining solution is to return to Maverick.

  • Reply to: Non Mac OS X version Vrak E610F?   2 weeks 5 days ago

    you may be able to do no init create arrary. Contact promise support though. That's what I would do.

  • Reply to: Non Mac OS X version Vrak E610F?   2 weeks 5 days ago

    Sir
    Please help
    PD11 was red on 6th feb , started pdm automatically it was done by 8th feb, we try login in webpampro using ip address but it doesn't go beyond administrator and password, so try login from terminal ssh and successfully login in cli.shut down all client & meta data control , after that restarted promise from cli menu and then i was able to login in webpam pro but i saw all drive in DA1 are stale, so clear all stale drive, except the PD11 which had pfa and was red. after that all stale drive became unrecognized and my DA1 was lost. and i have only DA0 & DA2 showing in promise.
    i cant mount my san volume now

    is there any option to recover the lost disk array? please help.

  • Reply to: Xsan - Cant add clients, tried everything.   2 weeks 6 days ago

    What's the version of the Xsan client?
    What's the version of the OS in the Server?
    What's the version of the OS in all the clients?
    Is the client that fails, with an old OS version?

    I can only assume it's not Yosemite, cause from Xsan4, you cannot add clients from the MDC, but from the Profiler.

    Like Thomasb said, check DNS is the first, on both public and metadata.
    Have you tried to reinitialise the client? Maybe there are some R/W permission wrong in the xsan folder.

  • Reply to: Notes on Xsan4   3 weeks 9 hours ago

    An upgrade of a MultiSAN SAN should continue working after upgrading to Xsan 4. Note: upgrading will currently require DNS on the metadata network.

    10.10.2 servers and clients will not need DNS on the metadata network after the MDCs have been "Activated."

  • Reply to: Xsan - Cant add clients, tried everything.   3 weeks 3 days ago

    Here is what you need to check.

    1. Make sure the client is not already in the Computers list in Xsan Admin (there might be an old record there).

    2. Make sure the Xsan folder is present in /Library/Preferences

    3. Make sure you ping the metadata controller metadata IP-address from the client machine.

    4. Make sure there are no duplicate metadata IP address in your SAN.

    5. Make sure the storage LUNs are visible on the client.

    6. Make sure there's only one DNS record for the public network on the client (check using nslookup client-name).

    7. Make sure the user account you are trying to authenticate with, is actually working on the client machine.

  • Reply to: Notes on Xsan4   3 weeks 4 days ago

    Apple's Xsan-StorNext compatibility matrix has been updated:

    https://support.apple.com/en-us/HT201256

  • Reply to: Notes on Xsan4   1 month 1 day ago
  • Reply to: Notes on Xsan4   1 month 1 day ago

    If I upgrade my Apple MDC's to Yosemite with Xsan 4, will my RedHat and Solaris clients running snfs 4.7.2 work without any issues?

  • Reply to: Choosing the Metadata Network on Xsan 4   1 month 1 day ago

    You can do it any time after creating a SAN or adding an MDC. It's not volume-specific. Note OS X 10.10.2 is required.

    KB article: How to select an Xsan metadata network in OS X Server (Yosemite)

  • Reply to: Problem with Xsan and PANIC error   1 month 1 day ago

    [20150212 16:46:19] 0x7fff7a341310 (**FATAL**) Server could not find any Meta-Data devices!\

    You've got a problem in fibre channel or in your RAID. The MDC can't start an fsm process for the volume if it can't see all LUNs used for metadata or journal.

  • Reply to: Choosing the Metadata Network on Xsan 4   1 month 1 day ago

    Thank you very much for the info.

    At what step of the configuration you use this command?

    Before creating the volume?

  • Reply to: Choosing the Metadata Network on Xsan 4   1 month 2 days ago

    I use this command to change it.

    sudo xsanctl changeIP oldIP newIP

  • Reply to: New SAN, can't add any clients (Failed to write conf. files)   1 month 3 days ago

    omg thank you for this! been sitting on this issue for a whole week. I'm running mavericks, and was able to add client after creating an "xsan" folder in perferences