Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Question:

Question: Why Can't Clients Mount Xsan Volume?

The MDC runs El Capitan + the newest version of ServerOS it supports.

The client runs Sierra.


The MDC sees and mounts the volume without issue.


The current configuration profile has been installed on the client successfully, but the volume doesn't mount. When a manual mount of the volume is attempted, it appears momentarily, as a folder in /Volumes, but then disappears. Running the mount command in terminal returns no error message on screen. That said, there are some lines in the Logs that are of interest:


[20180313 21:00:35] 0x700000323000 ERR XsanPostVolumeStateChange: sending request for volume 'TighelandSAN'

[20180313 21:00:35] 0x7fff7b6bc000 (debug) PortMapper: new_input authenticating protocol type(134) pmt_type(0) FSD(127.0.0.1)...

[20180313 21:00:35] 0x7fff7b6bc000 (debug) PortMapper: Local FSD client is registered, on port 50475.

[20180313 21:00:35] 0x7fff7b6bc000 (debug) NSS: New mount registered for 'TighelandSAN'.

[20180313 21:00:35] 0x700000429000 INFO Starting Disk rescan

[20180313 21:00:35] 0x700000429000 (debug) Disk rescan delay completed

[20180313 21:00:35] 0x700000429000 INFO Disk rescan found 0 disks

[20180313 21:00:40] 0x700000429000 INFO Starting Disk rescan

[20180313 21:01:05] 0x7fff7b6bc000 (debug) Entering slow heartbeat mode.

[20180313 21:01:08] 0x7fff7b6bc000 ERR PortMapper: Utility 'TighelandSAN' (pid 1279) FSS already running.

[20180313 21:01:08] 0x7fff7b6bc000 (debug) PortMapper: 'cvfsck' type 5 for 'TighelandSAN' registered (pri=0 pid=1279)

[20180313 21:01:48] 0x700000429000 (debug) Disk rescan delay completed

[20180313 21:01:48] 0x700000429000 INFO Disk rescan found 0 disks

[20180313 21:03:20] 0x7fff7b6bc000 WARNING PortMapper: Invalid FSS 'TighelandSAN' name - will not launch (FSM config error).

[20180313 21:07:00] 0x7fff7b6bc000 ERR PortMapper: Utility 'TighelandSAN' (pid 1292) FSS already running.

[20180313 21:07:00] 0x7fff7b6bc000 (debug) PortMapper: 'cvfsck' type 5 for 'TighelandSAN' registered (pri=0 pid=1292)

[20180313 21:07:23] 0x7fff7b6bc000 (debug) PortMapper: 'cvfsck' type 5 for 'TighelandSAN' registered (pri=0 pid=1294)

[20180313 21:08:21] 0x7fff7b6bc000 ERR PortMapper: Utility 'TighelandSAN' (pid 1299) FSS already running.

[20180313 21:08:21] 0x7fff7b6bc000 (debug) PortMapper: 'cvfsck' type 5 for 'TighelandSAN' registered (pri=0 pid=1299)


Any insight would be greatly appreciated!

Mac Pro, macOS Sierra (10.12.6)

Posted on

Reply

Page content loaded

Mar 21, 2018 4:26 PM in response to Tigheland In response to Tigheland

The MDC runs El Capitan + the newest version of ServerOS it supports.

The client runs Sierra.


The MDC sees and mounts the volume without issue.


Sierra clients are incompatible with El Capitan MDCs.


Compatibility of Xsan metadata controllers (MDCs) and clients - Apple Support


You should upgrade your MDCs to High Sierra.

Mar 21, 2018 4:26 PM

Reply Helpful
User profile for user: Tigheland

Question: Why Can't Clients Mount Xsan Volume?