After some troubleshooting, I now doubt this is the issue, or the *only* issue I should say. I thought that because in the nssdbg.out the disk scan successfully finding the LUNs always happens just after the "new mount registered" entry (sometimes within the same second, which may mean its just a display output that is run after the mount attempt happens). At first I thought maybe the LUNs weren't being scanned by the time the mount attempt happens, triggering the failure (a long standing issue with macs, except they usually retry until successful), and that there may be something needed in order to get it to retry after all LUNs are found. Looking at the nssdbg log after booting and the volume not mounting shows nothing obviously relevant. This indicates there is nothing wrong with the profile, the volume, zoning, etc and the auto mount feature "works" if the system is already booted and I load the profile at that point.ΔΆ. When I install the profile, the expected volume mounts immediately, no others do, and everything is perfect. There is a profile loaded with both xsan and preference payloads, and onlyMount key set to auto mount one volume (out of several). The problem is only getting the volume to mount on boot, everything else is working fine. I've been having trouble with auto mount on a 10.11.2 client mac client (the only El Capitan client I've tested with Xsan MDCs) - and dug fairly deep, unsuccessfully.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |