Error Mounting ACFS volume onto another ACFS Volume

We have Oracle 11gr2 running on a two node cluster with OS of Solaris 10.
I have setup a few ACFS mounts that work great between the nodes, but I need to mount a ACFS volume onto another ACFS mounted filesystem. Can that be done?
Example:
First ACFS Mount - /opt/test
Second ACFS Mount - /opt/test/samba
I'm using the following commands:
# /sbin/mount -F acfs /dev/asm/opttest-121 /opt/test
# /sbin/mount -F acfs /dev/asm/optsamba-356 /opt/test/samba
mount: CLSU-00100: Operating System function: mount (/dev/asm/optsamba-356) failed with error data: 16
mount: CLSU-00101: Operating System error message: Device busy
mount: CLSU-00103: error location: SM_0
mount: ACFS-02110: Unable to mount /dev/asm/optsamba-356 on /opt/test/samba.
If I mount the /dev/asm/optsamba-356 volume to /opt/samba it works. In this case /opt is a directory off of / (root).
Thanks.
Brian

Hi Brian,
can't you simply mount it elsewhere and create a symbolic link?
Even if this would work, I have some doubts about it, since there is no internal mount order for the ACFS filesystems.
So what would happen if /opt/test/samba would be mounted before /opt/test?
Sebastian

Similar Messages

  • When I try to print my book I receive the following error message:  One or more of the images in your book are not presently available at full resolution. Please reconnect to these files by mounting the volume(s) containing the original images.

    When I try to print my book, I receive the following error message:  One or more of the images in your book are not presently available at full resolution. Please reconnect to these files by mounting the volume(s) containing the original images.  I don't understand what this means since all the photos are in the book.  Can someone please clarify?

    When you look at the images in the browser, do you see any arrow icons on your thumbnails? Like these:
    When you import your images from a folder on your system drive, you have two ways to import:
    Managed: Import and store the images in the library
    Or referenced: Leave the images in the folder outside the Aperture library.
    This is controlled by the "Store Files" settings in the Import panel:
    If you did not set "Store files" to "In the Aperture Library", the originals will stay in the folder outside.
    The error message you get, suggests that Aperture assumes the original files are in a folder outside the library.
    Select one of your images in the Browser and use the command "File > Show in Finder" - is this command available or dimmed out?

  • No longer mount NFS volumes with 2010.q1 release:

    Has anyone else seen this? I can no longer mount any of my NFS volumes with root squash since upgrading to 2010.q1. I have a ticket open with Sun (72644622), but everyone is apparently off/away.
    Before they all went off, Sun Eng. suggested setting max supported NFS version to 3, but this of course did not work. Hosts trying to mount the volumes error out with:
    call_verify: server HOST_IP_HERE requires stronger authentication.
    I have double checked that the atuh is set to sys (not krb), but it looks like the nfsd is not respecting this.
    Of course this has knocked all our VMware mounts offline as well, and using krb for these is out of the question....
    Had to update to support the new FC card...which works great...but me needs me nfs shares....
    Fishworks doods, stop yelling at drives and help a brother out ;)

    I wish I could tell you, but it seems we lost a CIM card. Worse yet, this failure was completely SILENT. Not a single "problem" listed in the logs. However, when attaching another J4400, I noticed an alarm LED on the failed CIM and verified that the storage was only seen by 1 path. Kind of disconcerting that availability could be reduced significantly without so much as an email.
    I'll let you know if we can get to the new release later this week.
    Charles

  • Backup Controller cannot mount XSAN Volume

    Hi Guys,
    I've really have a big problem regarding the XSAN that I've just setup: There are 3 Xserves connected to the SAN - one for the main controller, one for backup and another one for fileserver. After a fresh install of the Leopard Server 10.5.6 on all servers and fresh install of Xsan 2.0 updated to 2.1.1, I tried creating an SAN from the main controller, I added first the main and backup controllers, authenticated them properly and was successful adding them to the SAN. After this, I created the volume and it mounted properly on the main controller. What I don't understand is that whenever I try to mount the volume to the backup controller, it is saying unable to mount and even I tried forcing it to mount in terminal using the command xsanctl mount VOLNAME, its giving me an error saying
    "unable to mount volume, Cannot mount XSAN volume error code: 5"
    What is that error message? When I tried typing cvadmin to the main controller, it only gave me this message:
    Main Controller:
    File System Services (* indicates service is in control of FS)
    1>*XSAN[0] located on 10.0.0.101:49930 (pid 317)
    Select FSM "XSAN"
    When I type the same cvadmin to the backup controller, it gave me this message:
    Backup Controller:
    File System Service (* indicates service is in control of FS)
    1> XSAN[1] located on 10.0.0.102:50384 (pid 331)
    No FSSs are active
    Select FSM "none"
    What is happening? both servers are having a DNS name. Before I created the SAN, from the authenticate window, the server name is just the IP address of the Ethernet 0 (first ethernet port). Now whenever I fire up Xsan Admin, both controllers are now offline and if you authenticate them, the server name info suddenly changed from IP address to a DNS Name (e.g. from 194.170.34.12, changed to hct-mdc.ad.hct.ac.ae) which even if I type my admin username and password cannot authenticate saying "server not found in network"
    I really don't know now what to do and they need to fix the issue asap.
    I would really appreciate your help guys!
    Thanks.
    jantoniophi

    Hi,
    I am accessing this WS via ARD, so public LAN is definitely there. I have not connected the "Xsan" network (but it should be no problems communicating the Xsan traffic over this single LAN connection).
    With the firewall, the situation is more strange. When I try to open the Firewall settings on Sharing, there is a dialog "Other firewall software is running on this computer." I googled this and it seems that this was a common problem on 10.3. They suggest to delete com.apple.sharing.firewall.plist file but it is not there on 10.4.
    "sudo ipfw list" shows this:
    00001 allow udp from any 626 to any dst-port 626
    65535 allow ip from any to any
    Any ideas on how to make Firewall behave as expected? I will try to reinstall if I don't receive a reply.
    Thanks.

  • Time Machine Error - No Backup Volume Has Been Selected

    Just got the time capsule. Successfully had it replace old Airport Extreme setting. Successfully hooked it up via Ethernet to my iMac and completed a backup. Now I have it hooked up via Ethernet to my MBP. But I can't get it to backup
    The Time Capsule disk mounts and I can see the files in it from my iMac backup. I'm connected to the Airport network.
    In Time Machine preferences, it asks me to choose a backup disk. I select the time capsule. I turn the switch to on. And nothing happens. With the iMac, the backup started immediately.
    After a minute, I get this error message:
    Time Machine Error
    No backup volume has been selected.
    To select a backup volume, open System Preferences and choose Time Machine.
    Obviously, I have done this, but the Time Machine never turns on.
    I have spent thirty minutes messing with this.
    And suddenly, as I writing the post, and the error message comes up again, and I click Preferences, it switches to Preferences and suddenly, the backup starts.
    Go figure.

    I had the same problem, though I have a non-conventional setup. My Time Machine volume is on a linux box shared with netatalk. Looking in the system log I was receiving, "System Preferences[295]: FSMountServerVolumeSync received error: -36". It turned out that the problem was with Little Snitch. Another post I found stated that Little Snitch was interfering with Time Machine's authentication when it was mounting the TM volume. Turning off Little Snitch fixed the problem. Seemed that simply rebuilding the Little Snitch rule list fixed the problems I experienced.

  • A better way to make Automator mount a volume?

    I made an Automator application, using the Record function, to mount a volume on a drive connected to my Mini. I also made a similar one to eject it. I use them as Calendar-triggered events as part of my backup scheme.
    They work well ... until I restart the Mini, when occasionally my two connected drives will mount in a different order. What happens then is that the sequence of mouse clicks recorded in Automator don’t find the correct volume.
    I wonder if there’s a better way to automate the mounting of a currently ejected disc (and later its ejection). Automator, as far as I can see, does not have the actions I need. It has Ask For/Connect to/Get specified Servers, but they seem only to be for network-connected stuff.
    Anyone know a better way?

    Welcome to Unix. 
    The key part of that shell script code is the test for the existence of the mount point (if [ -e /Volumes/dbamp ]), followed by a conditional block that — in the "else" section involved when the mount point wasn't found — creates it, and then mounts an AFP file system on that mount point.  Most of the rest of the baggage in that script is used to get the mysqldump database dumps over onto the target disk, once it's been mounted.
    Here's a very quick overview of the basics of scripting , Apple's introduction to the command line manual, there's a generic bash intro (which is good, but doesn't line up exactly with how bash is implemented on OS X) and O'Reilly has some reasonable books on bash and bash scripting.  Once you know and are comfortable with the basics, there are advanced bash guides available.

  • CHKDSK run on WD ext HDD - hang at Correcting errors in the Volume Bitmap - does it take very long?

    Hi
    As a background, my WD extHDD ( 1.5T) was working fine until today. When connect to PC, it cannot be reach but the drive letter  (G:) appears and after awhile show CRC errors. The HDD cannot be access. After looking at some hep pages instructions, I
    run the following at the CMD window : chkdsk G: /f /r.      The CHKDSK runs through and did fixed some bad sectors .. and it when through stage 5 completed and after that it has the following message :
    Free space verification is complete.
    Adding 10 bad clusters to the Bad Clusters File.
    CHKDSK discovered free space marked as allocated in the volume bitmap.
    Correcting errors in the Volume Bitmap.
    It is still "running" for over 12 hours now..  I am not sure if I need to stop it ( reboot?)  or continue to wait for a status change ?!!
    Please help !!!
    st99my
    The complete details of the CHKDSK run is below : 
    Microsoft Windows [Version 6.3.9600]
    (c) 2013 Microsoft Corporation. All rights reserved.
    C:\Users\test888>chkdisk G: /f /r
    'chkdisk' is not recognized as an internal or external command,
    operable program or batch file.
    C:\Users\test888>chkdsk G: /f /r
    The type of the file system is NTFS.
    Volume label is Elements.
    Stage 1: Examining basic file system structure ...
      50432 file records processed.
    File verification completed.
      0 large file records processed.
      0 bad file records processed.
    Stage 2: Examining file name linkage ...
      58276 index entries processed.
    Index verification completed.
      0 unindexed files scanned.
      0 unindexed files recovered.
    Stage 3: Examining security descriptors ...
    Security descriptor verification completed.
      3923 data files processed.
    CHKDSK is verifying Usn Journal...
      10905608 USN bytes processed.
    Usn Journal verification completed.
    Stage 4: Looking for bad clusters in user file data ...
    Windows replaced bad clusters in file 43621
    of name \PERSON~1\audio\PCSTUD~1.ZIP.
    Windows replaced bad clusters in file 43773
    of name \PERSON~1\audio\AUDIO-~1\JACKTR~3.MP3.
    Windows replaced bad clusters in file 43783
    of name \PERSON~1\audio\AUDIO-~1\JE4C19~1.MP3.
    Windows replaced bad clusters in file 43785
    of name \PERSON~1\audio\AUDIO-~1\JE4BE5~1.MP3.
    Windows replaced bad clusters in file 43788
    of name \PERSON~1\audio\AUDIO-~1\JEC96B~1.MP3.
    Windows replaced bad clusters in file 43953
    of name \PERSON~1\audio\AUDIO-~1\NY1477~1.MP3.
    Windows replaced bad clusters in file 44981
    of name \PERSON~1\audio\THRUTH~1.VER\NEWTES~1\40_MAT~1\40096M~1.MP3.
    Windows replaced bad clusters in file 45777
    of name \PERSON~1\audio\THRUTH~1.VER\NEWTES~1\46_1CO~1\460291~1.MP3.
    Windows replaced bad clusters in file 45866
    of name \PERSON~1\audio\THRUTH~1.VER\NEWTES~1\47_2CO~1\470172~1.MP3.
      50416 files processed.
    File data verification completed.
    Stage 5: Looking for bad, free clusters ...
      419430987 free clusters processed.
    Free space verification is complete.
    Adding 10 bad clusters to the Bad Clusters File.
    CHKDSK discovered free space marked as allocated in the volume bitmap.
    Correcting errors in the Volume Bitmap.

    1. Backup most important files to another device or cloud
    2. Use diagnostics tool(s) from WD
    http://support.wdc.com/product/download.asp
    3. Send log to WD support and consider replacement of external HDD. If warrancy applies send HDD to WD directly.
    Rgds
    Milos
    PS: Reseller and vendor warracies may differ (5 to 2 years in my case)

  • Kextcache error while updating /Volumes/Seagate CCC

    Hi, my external seagate drive (2Tb partitioned into 2 * 1Tb's I've been using for Carbon Copy Cloner has a problem with kextcache, I will not pretend to know what kextcache is but the errors I am getting relate to an invalid signature, it tries 26 times before giving up.
    I expect this explains why the drive is not bootable, any suggestioins as to how to fix the problem, can it be fixed?
    Regards
    Ian
    08/02/2014 22:11:31.000 kernel[0]: USBMSC Identifier (non-unique): 0x00000000 0xbc2 0x3320 0x100, 3
    08/02/2014 22:11:32.000 kernel[0]: CoreStorage: fsck_cs has finished for group "E4E85C17-019A-41E7-AC85-6F3FFEAB9ABF" with status 0x00
    08/02/2014 22:11:32.508 com.apple.kextd[12]: LVG changed
    08/02/2014 22:11:32.000 kernel[0]: CoreStorageFamily::unlockVEKs() failed to unwrap the vek, status = e00002bc
    08/02/2014 22:11:32.626 com.apple.kextd[12]: LVG changed
    08/02/2014 22:11:32.000 kernel[0]: hfs: mounted Seagate MAC on device disk5s4
    08/02/2014 22:11:33.000 kernel[0]: hfs: mounted Seagate CCC on device disk6
    08/02/2014 22:11:33.503 diskmanagementd[2676]: mount blocked by dissenter PID=0 (unknown) status=0xf8da0002 log=kDAReturnBusy message=(null)
    08/02/2014 22:11:34.587 com.apple.kextcache[2960]: rebuilding /System/Library/Caches/com.apple.kext.caches/Startup/kernelcache
    08/02/2014 22:11:38.942 com.apple.kextcache[2963]: WARNING - Invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext "/Volumes/Seagate CCC/System/Library/Extensions/System.kext/PlugIns/Unsupported.kext"
    08/02/2014 22:11:38.944 com.apple.kextcache[2963]: WARNING - Invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext "/Volumes/Seagate CCC/System/Library/Extensions/System.kext/PlugIns/Private.kext"
    08/02/2014 22:11:38.946 com.apple.kextcache[2963]: WARNING - Invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext "/Volumes/Seagate CCC/System/Library/Extensions/System.kext/PlugIns/Mach.kext"
    08/02/2014 22:11:38.947 com.apple.kextcache[2963]: WARNING - Invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext "/Volumes/Seagate CCC/System/Library/Extensions/System.kext/PlugIns/MACFramework.kext"
    08/02/2014 22:11:38.949 com.apple.kextcache[2963]: WARNING - Invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext "/Volumes/Seagate CCC/System/Library/Extensions/System.kext/PlugIns/Libkern.kext"
    08/02/2014 22:11:38.958 com.apple.kextcache[2963]: WARNING - Invalid signature -67030 0xFFFFFFFFFFFEFA2A for kext "/Volumes/Seagate CCC/System/Library/Extensions/System.kext/PlugIns/IOSystemManagement.kext"
    08/02/2014 22:11:38.966 com.apple.kextcache[2963]: WARNING - Invalid signature -67030 0xFFFFFFFFFFFEFA2A for kext "/Volumes/Seagate CCC/System/Library/Extensions/System.kext/PlugIns/IONVRAMFamily.kext"
    08/02/2014 22:11:38.967 com.apple.kextcache[2963]: WARNING - Invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext "/Volumes/Seagate CCC/System/Library/Extensions/System.kext/PlugIns/IOKit.kext"
    08/02/2014 22:11:38.969 com.apple.kextcache[2963]: WARNING - Invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext "/Volumes/Seagate CCC/System/Library/Extensions/System.kext/PlugIns/BSDKernel.kext"
    08/02/2014 22:11:38.978 com.apple.kextcache[2963]: WARNING - Invalid signature -67030 0xFFFFFFFFFFFEFA2A for kext "/Volumes/Seagate CCC/System/Library/Extensions/System.kext/PlugIns/ApplePlatformFamily.kext"
    08/02/2014 22:11:38.990 com.apple.kextcache[2963]: WARNING - Invalid signature -67030 0xFFFFFFFFFFFEFA2A for kext "/Volumes/Seagate CCC/System/Library/Extensions/System.kext/PlugIns/AppleNMI.kext"
    08/02/2014 22:11:38.998 com.apple.kextcache[2963]: WARNING - Invalid signature -67030 0xFFFFFFFFFFFEFA2A for kext "/Volumes/Seagate CCC/System/Library/Extensions/System.kext"
    08/02/2014 22:11:39.118 com.apple.kextcache[2963]: kext com.jmicron.JMicronATA  101069000 is in exception list, allowing to load
    08/02/2014 22:11:39.313 com.apple.kextcache[2963]: WARNING - Invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext "/Volumes/Seagate CCC/System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/IOUSBUserClient .kext"
    08/02/2014 22:11:39.410 com.apple.kextcache[2963]: WARNING - Invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext "/Volumes/Seagate CCC/System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/IOUSBHIDDriver. kext"
    08/02/2014 22:11:39.442 com.apple.kextcache[2963]: WARNING - Invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext "/Volumes/Seagate CCC/System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/IOUSBCompositeD river.kext"
    08/02/2014 22:11:39.483 com.apple.kextcache[2963]: WARNING - Invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext "/Volumes/Seagate CCC/System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/AppleUSBXHCI.ke xt"
    08/02/2014 22:11:39.628 com.apple.kextcache[2963]: WARNING - Invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext "/Volumes/Seagate CCC/System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/AppleUSBUHCI.ke xt"
    08/02/2014 22:11:39.658 com.apple.kextcache[2963]: WARNING - Invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext "/Volumes/Seagate CCC/System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/AppleUSBOHCI.ke xt"
    08/02/2014 22:11:39.689 com.apple.kextcache[2963]: WARNING - Invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext "/Volumes/Seagate CCC/System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/AppleUSBMergeNu b.kext"
    08/02/2014 22:11:39.713 com.apple.kextcache[2963]: WARNING - Invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext "/Volumes/Seagate CCC/System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/AppleUSBHub.kex t"
    08/02/2014 22:11:39.766 com.apple.kextcache[2963]: WARNING - Invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext "/Volumes/Seagate CCC/System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/AppleUSBEHCI.ke xt"
    08/02/2014 22:11:39.767 com.apple.kextcache[2963]: WARNING - Invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext "/Volumes/Seagate CCC/System/Library/Extensions/IOUSBFamily.kext"
    08/02/2014 22:11:41.127 com.apple.kextcache[2963]: kext com.ATTO.driver.ATTOExpressSASRAID  307029000 is in exception list, allowing to load
    08/02/2014 22:11:41.144 com.apple.kextcache[2963]: kext com.ATTO.driver.ATTOExpressSASHBA3  100059000 is in exception list, allowing to load
    08/02/2014 22:11:41.161 com.apple.kextcache[2963]: kext com.ATTO.driver.ATTOExpressSASHBA  200009000 is in exception list, allowing to load
    08/02/2014 22:11:41.173 com.apple.kextcache[2963]: kext com.ATTO.driver.ATTOExpressPCIUl4  404029000 is in exception list, allowing to load
    08/02/2014 22:11:41.200 com.apple.kextcache[2963]: kext com.ATTO.driver.ATTOCelerityFC  304089000 is in exception list, allowing to load
    08/02/2014 22:11:43.037 com.apple.kextcache[2964]: /Volumes/Seagate CCC locked; waiting for lock.
    08/02/2014 22:11:43.253 com.apple.kextcache[2963]: kext com.Accusys.driver.Acxxx  300029000 is in exception list, allowing to load
    08/02/2014 22:11:46.534 com.apple.kextcache[2963]: kxld[com.apple.iokit.IOStorageFamily]: The super class vtable 'vtable for IOService' for vtable 'vtable for IOMediaBSDClient' is out of date. Make sure your kext has been built against the correct headers.
    08/02/2014 22:11:46.534 com.apple.kextcache[2963]: kxld[com.apple.iokit.IOStorageFamily]: The super class vtable 'vtable for IOService' for vtable 'vtable for IOBlockStorageDevice' is out of date. Make sure your kext has been built against the correct headers.
    08/02/2014 22:11:46.534 com.apple.kextcache[2963]: kxld[com.apple.iokit.IOStorageFamily]: The super class vtable 'vtable for IOService' for vtable 'vtable for IOStorage' is out of date. Make sure your kext has been built against the correct headers.
    08/02/2014 22:11:46.534 com.apple.kextcache[2963]: kxld[com.apple.iokit.IOStorageFamily]: The super class vtable 'vtable for IOService' for vtable 'vtable for IOMediaBSDClient' is out of date. Make sure your kext has been built against the correct headers.
    08/02/2014 22:11:46.534 com.apple.kextcache[2963]: kxld[com.apple.iokit.IOStorageFamily]: The super class vtable 'vtable for IOService' for vtable 'vtable for IOBlockStorageDevice' is out of date. Make sure your kext has been built against the correct headers.
    08/02/2014 22:11:46.534 com.apple.kextcache[2963]: kxld[com.apple.iokit.IOStorageFamily]: The super class vtable 'vtable for IOService' for vtable 'vtable for IOStorage' is out of date. Make sure your kext has been built against the correct headers.
    08/02/2014 22:11:46.534 com.apple.kextcache[2963]: kxld[com.apple.iokit.IOStorageFamily]: The vtable for IOFilterScheme was not patched because its parent, the vtable for IOStorage, was not patchable.
    08/02/2014 22:11:46.534 com.apple.kextcache[2963]: kxld[com.apple.iokit.IOStorageFamily]: The vtable for IOPartitionScheme was not patched because its parent, the vtable for IOStorage, was not patchable.
    08/02/2014 22:11:46.534 com.apple.kextcache[2963]: kxld[com.apple.iokit.IOStorageFamily]: The vtable for IOAppleLabelScheme was not patched because its parent, the vtable for IOFilterScheme, was not patchable.
    08/02/2014 22:11:46.535 com.apple.kextcache[2963]: kxld[com.apple.iokit.IOStorageFamily]: The vtable for IOBlockStorageDriver was not patched because its parent, the vtable for IOStorage, was not patchable.
    08/02/2014 22:11:46.535 com.apple.kextcache[2963]: kxld[com.apple.iokit.IOStorageFamily]: The vtable for IOGUIDPartitionScheme was not patched because its parent, the vtable for IOPartitionScheme, was not patchable.
    08/02/2014 22:11:46.535 com.apple.kextcache[2963]: kxld[com.apple.iokit.IOStorageFamily]: The vtable for IOApplePartitionScheme was not patched because its parent, the vtable for IOPartitionScheme, was not patchable.
    08/02/2014 22:11:46.535 com.apple.kextcache[2963]: kxld[com.apple.iokit.IOStorageFamily]: The vtable for IOFDiskPartitionScheme was not patched because its parent, the vtable for IOPartitionScheme, was not patchable.
    08/02/2014 22:11:46.535 com.apple.kextcache[2963]: kxld[com.apple.iokit.IOStorageFamily]: The vtable for IOMedia was not patched because its parent, the vtable for IOStorage, was not patchable.
    08/02/2014 22:11:46.536 com.apple.kextcache[2963]: Link failed (error code 5).
    08/02/2014 22:11:46.536 com.apple.kextcache[2963]: Prelink failed for com.apple.iokit.IOStorageFamily; omitting from prelinked kernel.
    08/02/2014 22:11:46.536 com.apple.kextcache[2963]: Can't use IOStorageFamily.kext - not linked.
    08/02/2014 22:11:46.536 com.apple.kextcache[2963]: Prelink failed for com.softraid.driver.SoftRAID; omitting from prelinked kernel.
    08/02/2014 22:11:46.564 com.apple.kextcache[2963]: kxld[com.apple.iokit.IOSCSIArchitectureModelFamily]: The super class vtable 'vtable for IOService' for vtable 'vtable for IOSCSIProtocolInterface' is out of date. Make sure your kext has been built against the correct headers.
    08/02/2014 22:11:46.564 com.apple.kextcache[2963]: kxld[com.apple.iokit.IOSCSIArchitectureModelFamily]: The super class vtable 'vtable for IOService' for vtable 'vtable for AppleSCSISubsystemGlobals' is out of date. Make sure your kext has been built against the correct headers.
    08/02/2014 22:11:46.564 com.apple.kextcache[2963]: kxld[com.apple.iokit.IOSCSIArchitectureModelFamily]: The super class vtable 'vtable for IOService' for vtable 'vtable for IOSCSIProtocolInterface' is out of date. Make sure your kext has been built against the correct headers.
    08/02/2014 22:11:46.565 com.apple.kextcache[2963]: kxld[com.apple.iokit.IOSCSIArchitectureModelFamily]: The super class vtable 'vtable for IOService' for vtable 'vtable for AppleSCSISubsystemGlobals' is out of date. Make sure your kext has been built against the correct headers.
    08/02/2014 22:11:46.565 com.apple.kextcache[2963]: kxld[com.apple.iokit.IOSCSIArchitectureModelFamily]: The vtable for IOSCSITargetDevice was not patched because its parent, the vtable for IOSCSIPrimaryCommandsDevice, was not patchable.
    08/02/2014 22:11:46.565 com.apple.kextcache[2963]: kxld[com.apple.iokit.IOSCSIArchitectureModelFamily]: The vtable for IOSCSILogicalUnitNub was not patched because its parent, the vtable for IOSCSIPeripheralDeviceNub, was not patchable.
    08/02/2014 22:11:46.565 com.apple.kextcache[2963]: kxld[com.apple.iokit.IOSCSIArchitectureModelFamily]: The vtable for IOSCSIProtocolServices was not patched because its parent, the vtable for IOSCSIProtocolInterface, was not patchable.
    08/02/2014 22:11:46.565 com.apple.kextcache[2963]: kxld[com.apple.iokit.IOSCSIArchitectureModelFamily]: The vtable for IOSCSIPeripheralDeviceNub was not patched because its parent, the vtable for IOSCSIProtocolServices, was not patchable.
    08/02/2014 22:11:46.565 com.apple.kextcache[2963]: kxld[com.apple.iokit.IOSCSIArchitectureModelFamily]: The vtable for IOSCSIPrimaryCommandsDevice was not patched because its parent, the vtable for IOSCSIProtocolInterface, was not patchable.
    08/02/2014 22:11:46.565 com.apple.kextcache[2963]: kxld[com.apple.iokit.IOSCSIArchitectureModelFamily]: The vtable for IOSCSIMultipathedLogicalUnit was not patched because its parent, the vtable for IOSCSIPeripheralDeviceNub, was not patchable.
    08/02/2014 22:11:46.565 com.apple.kextcache[2963]: kxld[com.apple.iokit.IOSCSIArchitectureModelFamily]: The vtable for IOSCSIHierarchicalLogicalUnit was not patched because its parent, the vtable for IOSCSIPeripheralDeviceNub, was not patchable.
    08/02/2014 22:11:46.566 com.apple.kextcache[2963]: Link failed (error code 5).
    08/02/2014 22:11:46.566 com.apple.kextcache[2963]: Prelink failed for com.apple.iokit.IOSCSIArchitectureModelFamily; omitting from prelinked kernel.
    08/02/2014 22:11:46.566 com.apple.kextcache[2963]: Can't use IOSCSIArchitectureModelFamily.kext - not linked.
    08/02/2014 22:11:46.566 com.apple.kextcache[2963]: Prelink failed for com.apple.iokit.IOSCSIParallelFamily; aborting prelink.
    08/02/2014 22:11:46.566 com.apple.kextcache[2963]: Failed to generate prelinked kernel.
    08/02/2014 22:11:46.570 com.apple.kextcache[2960]: Child process /usr/sbin/kextcache[2963] exited with status 71.
    08/02/2014 22:11:46.571 com.apple.kextcache[2960]: Error 107 rebuilding /System/Library/Caches/com.apple.kext.caches/Startup/kernelcache.
    08/02/2014 22:11:46.571 com.apple.kextd[12]: kextcache error while updating /Volumes/Seagate CCC (error count: 1)
    08/02/2014 22:11:46.876 com.apple.kextcache[2964]: Lock acquired; proceeding.
    08/02/2014 22:11:46.876 com.apple.kextd[12]: async child pid 2960 exited with status 71
    08/02/2014 22:11:46.876 com.apple.kextcache[2964]: rebuilding /System/Library/Caches/com.apple.kext.caches/Startup/kernelcache

    Hi,
    interesting: I have the same issue, however, I don't have any software from Freecom installed.
    Here is my situation, which - to me - is quite bizarre.
    Some weeks ago, I installed an SSD as the boot disk, moving my "old" HDD to the Superdrive bay.
    This worked quite well. I then upgraded to Mavericks (from ML).
    It's tough to say for certain, but my impression is that since I upgraded, things have gone quite awry.
    I'm seeing these Error 107 messages from kextcache as well, repeating over and over periodically. What is very odd is this: the cache is trying to update on the HDD! I checked; there is a Library and a System directory in the HHD's root.
    I figured I had forgotten to clear those out when I changed the HDD to be a data-only drive, and that Mavericks was using the System directory on the HDD because - well - it was there. So I deleted both the Library and System directories and rebooted.
    This fixed Pathfinder's lockup error (after updating), but - much to my surprise - the System directory is back!
    All it contains is a Library directory and that only has a Caches directory in it, which - no surprise - contains the com.apple.kext.caches directory. This subtree belongs to root with group wheel, so that should be ok.
    So:
    1) why on earth is Mavericks putting this directory on the HDD, and not on the SSD which contains the "real" system directory?
    2) why am I getting 107 errors?
    Here is the relevant part of my log:
    Apparently, I'm not the only one, I just found this discussion on what seems to be a similar subject:
    https://discussions.apple.com/thread/5490448
    Thanks!

  • Unable to mount XSAN volume on client workstation

    We just reimaged one of our machines and we are now unable to mount the xsan volume. Originally when the machine hooked up the IP was wrong and the XSAN couldn't see it. This has been fixed and the XSAN sees it now and it is authenticated, but when we try to mount the volume we get this error
    Jan 26 13:54:48 *** Xsan Admin[23616]: ERROR: Error reading computer properties: kOfflineError (0)
    Jan 26 13:55:37 *** Xsan Admin[23616]: ERROR: Error mounting volume…: Server returned a non-zero status code (100007)
    Jan 26 13:55:48 *** Xsan Admin[23616]: The temporary directory at "/private/var/folders/Eu/Euvo7L8cHAmWwo7ntmj8ak+TI/TemporaryItems/(A Document Being Saved By Xsan Admin 33)" could not be deleted.
    The *'s was the name of the machine, apple has been little to no help. We have tried removing the machine form the XSAN and then adding it back in, same issue. Tried reinstallingt eh client, same issue. Any ideas?

    This is the error on server
    ERROR: Error mounting volume…: Server returned a non-zero status code (100007)

  • File sharing wont mount all volumes

    Hello,
    I've been going crazy trying to figure this one out. I'm trying to share my Mac Pro files and have enabled file sharing from the networking system preferences, up until a month ago this was working fine. Now whenever I connect to my Mac pro as admin from my Macbook pro I only get my home folder and public folder to mount, the volumes on my mac pro wont show up on any computer I connect with. It was working fine for years and then one day just stopped. As a test, I just tried connecting to my Macbook pro from my Mac Pro and it lists all the volumes on my computer, So I don't think its my router or anything, but nothing has changed anyway. Any help would be great, thanks!
    Message was edited by: teeck2000

    I'm having the same problem. I tried your suggestion and it worked on one of my two external usb drives but I'm still having problems on my other external.
    It shows up on the shared list but when I click on it I get the message: The operation cannot be completed because the original item for "NamedDisk" cannot be found.
    I've tried deleting all my network preferences, plist files etc. and running disk warrior on the nameddisk to no avail.
    This problem just started a few days ago. Not sure what could have changed. I've had 10.5.7 running on this computer for a few weeks. I get the same error from any computer on my network trying to access this disk.

  • Auto-mounting AFS volumes

    I've read there are two 'ways' of doing it, 'dynamically', and 'statically'. Which way do I want to do it, the following, and how do I do it, exacly?
    I've got GNU Linux servers tarfu, snafu and fubar. Each server is sharing at least 1 volume via netatalk. I have had to mount these volumes after I login since I set up the system about a year ago. I noticed that the "connect at startup" (or whatever it was called) checkbox present from OS ~ through OS 9 was missing, and figured, "oh well. I'll live without it", well, Now I am done living without it.
    I want to mount shares at a) boot time or b) login time.
    How?
    I have scoured google for decent instructions, but all I came up with was this: http://www.bombich.com/mactips/automount.html
    Not very helpful. There are no Auth options, which I require, and the instructions just aren't written very well.
    Does anyone have any instructions, a blow-by-blow document telling me just how to do what I want to do?

    What about applescript ??
    I set up an applescript for a client yesterday, that i made into an application... which i told to load on login... would that help ??
    My script is below (you'll need to copy into 'Script Editor') and save as an application after cutomising it:
    COPY FROM HERE:
    tell application "Finder"
    if (exists disk "sharename") then
    set volumemounted to true
    display dialog "'sharename' is already mounted on the Desktop" buttons {"OK"}
    if volumemounted = "true" then
    quit
    end if
    else
    try
    mount volume ("afp://username:[email protected]/sharename")
    display dialog "'sharename' was mounted on your desktop." & return & return & "Happy Sharing!" buttons {"OK"}
    on error
    display dialog "There was an error mounting the 'sharename' Disk. Check the disk is connected to its computer and turned on." buttons {"OK"}
    end try
    set volumemounted to true
    end if
    end tell
    COPY TO HERE
    You'll need to customise the parts in bold...
    Ask if you need further clarification...
    Cheers.
    Macbook 17" Duo2   Mac OS X (10.4.8)  

  • What to do about Backup failed with error: The target volume is read-only

    This is a weird story. My wife has a PowerBook G4/1.33 GHz that she uses in clamshell mode with a 20" Cinema Display. One day under OS X 10.5.6, her Time Machine backups (to a networked 500 GB Time Capsule) failed with the error: Backup failed with error: The target volume is read-only. So I upgraded her to 10.5.7 and erased the sparseimage file, starting a new Time Machine backup. And it just happened again. Any idea how this sort of problem arises? My wife was doing something at her computer when the Time Machine error occurred.
    Please don't advise us to upgrade to 10.5.8, because her PowerBook freezes not infrequently with any OS later than 10.5.6, and I was just about to downgrade her from 10.5.7 to 10.5.6.

    Pondini wrote:
    odysseus wrote:
    This is a weird story. My wife has a PowerBook G4/1.33 GHz that she uses in clamshell mode with a 20" Cinema Display. One day under OS X 10.5.6, her Time Machine backups (to a networked 500 GB Time Capsule) failed with the error: Backup failed with error: The target volume is read-only. So I upgraded her to 10.5.7 and erased the sparseimage file, starting a new Time Machine backup. And it just happened again.
    Try repairing the sparse bundle, per #A5 of the Time Machine - Troubleshooting *User Tip,* also at the top of this forum.
    I've tried this before, but it can't be repaired, because it can't be mounted.
    Any idea how this sort of problem arises? My wife was doing something at her computer when the Time Machine error occurred.
    One possibility is, the HD in the Time Capsule is beginning to fail (all HDs fail, sooner or later).
    I'm backing up to my own sparseimage bundle just fine.
    Please don't advise us to upgrade to 10.5.8, because her PowerBook freezes not infrequently with any OS later than 10.5.6, and I was just about to downgrade her from 10.5.7 to 10.5.6.
    Those two things may be related. Whatever's going wrong may very well be what's corrupting the backups.
    I'd recommend finding out what's wrong with the Powerbook. It's impossible to tell, of course, but that may be the root of the problem.
    There's a problem with PowerBooks and Cinema Displays. I've posted a lot about this. Even after a motherboard replacement, my PowerBook G4/1.67 GHz had freezes, and eventually Apple gave me a MacBook Pro, but I think there's a failure involving hardware/software design.
    If you haven't yet, I'd start by dong a +*Verify Disk+* on it's internal HD (also per #A5);
    That checks out fine.
    if there are no errors, or they're fixed and the problem continues, run the +Apple Hardware Test+ from the disc that came with the Mac. (One of the discs should have that, and instructions for running it, printed in tiny type on the label).
    If still no help, I'd be inclined to do an +Archive & Install, preserving users & settings,+ of Leopard, then download & install the appropriate "combo" update. That's a combination (thus the clever name) of all the updates to Leopard since it was first released, so installing it should fix anything that's gone wrong since then, such as with one of the normal "point" updates. Info and download available at: http://support.apple.com/downloads/MacOS_X_10_5_8_ComboUpdate (change the last "8" to the desired number). Be sure to do a +Repair Permissions+ via Disk Utility (in your Applications/Utilities folder) afterwards.

  • MCX Login Items: Mounting Server Volumes

    I noticed that when you set up a policy for a user,group or computer to mount a remote volue at login, you will get a Finder error if the volume can't be mounted for some reason (i.e.; the server is down, the volume is not available etc. This can be handy for troubleshooting.
    Is there a way to surpress the error, so my mobile users dont get an error when the remote volumes are unavailable?
    Example: A lot of my Mac users will have laptops, and thus sometimes they will be away from our LAN. I want they to still be bound to OD and have cached MCX settings when they are on the road. However, I dont want the users to get "Volume could not be found" errors.
    Message was edited by: Daniel Stranathan

    I think you should be able to use AppleScript to mount the volume, put that code inside a "try" construct, and leave the "on error" blank. Like this:
    try
    tell "Finder"
    mount volume "afp://[user]:[passwd]@[server hostname or IP]:/[sharepoint]"
    end tell
    on error
    -- do nothing
    end try
    I haven't tried this, but thought it might work.

  • In Mavericks, any "diskutil mount" also mounts EFI volume

    Here's a diskutil command and output:
    $ diskutil list disk1
    /dev/disk1
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:      GUID_partition_scheme                        *1.0 TB     disk1
       1:                        EFI EFI                     209.7 MB   disk1s1
       2:                  Apple_HFS Pocket                  724.2 GB   disk1s2
       3:                  Apple_HFS free2                   274.2 GB   disk1s3
       4:                 Apple_Boot Recovery HD             784.2 MB   disk1s4
    So if I want to mount Pocket, I use "diskutil mount disk1s2"
    Result:
    Volume(s) mounted successfully
    But now I also see a volume named "EFI" on my desktop. It wasn't there before. Apparently, "diskutil mount disk1s2" made it show up also. It doesn't show up along with Pocket and free2 when I connect the disk to the Mac.
    Why does the volume named EFI (disk1s1) also appear on my desktop after using that terminal command?
    Thanks.

    Anyway, here's the AppleScript I wrote to toggle local volumes. It's similar to MERGING two Scripts to Unmount disks... but it's primarily an update for this item a Mac OS X Hints. The AppleScript attempts to unmount any currently mounted local volumes. If no volumes other than the boot volume are mounted when it runs, then all available volumes are mounted, and you're offered the option of re-mounting unmounted volumes if any volume can't be politely unmounted.
    set alldisks to paragraphs of (do shell script ¬
                        "diskutil list|grep -v 'EFI EFI'|grep -v 'Recovery HD'|grep -o 'disk[0-9][a-z][0-9]*'")
              set all_non_boot_disks to paragraphs of (do shell script "df -hlg | awk -F/ '/disk*/ {print $5}'")
              set nonbootnumber to (count of alldisks)
              if (count of all_non_boot_disks) > 0 then
                        try
                                  set all_non_boot_disks to items 2 thru nonbootnumber of alldisks
                        on error
                                  set all_non_boot_disks to {}
                        end try
      activate
                        repeat with the_Item in alldisks
                                  try
                                            set the_ID to (do shell script "df -hlg | grep -m 1" & space & ¬
                                                      quoted form of the_Item & space & "| grep -o 'disk[0-9][a-z][0-9]*'")
                                            do shell script "diskutil unmount" & space & the_ID
                                  on error the error_message number the error_number
                                            if the error_message does not contain ":" then
                                            else
                                                      if button returned of (display dialog "A disk couldn't be unmounted.
                                            Would you like to re-mount those already unmounted?" buttons ¬
                                                                {"Cancel", "Re-mount"} default button 2) is "Re-mount" then
                                                                my mountAll(alldisks)
                                                      end if
                                            end if
                                  end try
                        end repeat
              else
                        my mountAll(alldisks)
    end if
    on mountAll(alldisks)
              set actiondisks to {}
              repeat with i in alldisks
                        if i is not in actiondisks then
                                  set actiondisks to actiondisks & i
                        end if
              end repeat
              repeat with myitem in actiondisks
                        try
                                  do shell script "diskutil mount" & space & myitem
                        end try
              end repeat
    end mountAll

  • Unknown error: 118 on /Volumes

    Last time I installed Leopard Server I got "Unknown error: 118" when trying to access /Volumes in any way through Terminal. Disk Utility says it's ok, but it's not. Repairing permissions gets the same error in the log, but it doesn't seem to care. I can't use /Volumes at all, so mounting dmg:s won't work for instance ("no mountable file systems"). I gave up and did an Erase and Install. Once set up again (10.5.1, OD, mail, DNS etc.), I just noticed that the problem is back! I have installed Firefox, so mounting dmgs did work for a while.
    $ ls -l /Volumes/
    ls: : Unknown error: 118
    $ cd /Volumes/
    -bash: cd: /Volumes/: Unknown error: 118
    $
    This isn't fun anymore.

    Mac - my absence was because after encountering quite a few bugs and wierdnesses with leopard I decided to scrap the migration project until 10.5.2 or so. Now, here's 10.5.2, and no solution to this problem in sight.
    I'm working with a clean install of OS X 10.5.2 Client (intel Imac mid-2007)
    and OS X Server 10.4.11 (Xserve G5).
    OS X Server is OD Master, but has no management in place for this client, it is not in any computer lists. To reproduce issue:
    On leopard client, open Directory Utility, add my 10.4.11 OD Master. It is that simple.
    Immediately, cannot mount any volumes nor navigate to or access /Volumes directory
    on cd into /Volumes:
    cd: /Volumes: Unknown error: 118.
    Interestingly, ls -l on / shows permissions have changed on /Volumes to
    dr-xr-xr-x (which explains why I cannot mount anything, since there is no write access to /volumes directory) (before connecting to server I believe permissions read drwxrwxr-t)
    however, chmod u+w /volumes (to give write access and enable mounting there) results in same Unknown error: 118
    Since adding the OD server broke this, I remove the server in Directory Utility and voila, immediately I can navigate into /volumes and mount any volume to my heart's content
    permissions on /volumes are restored to:
    drwxrwxr-t@
    (just to confirm I re-added the server, and the problem was back)
    Racking the brains here but I'm afraid I have no solution to add. Could this be a result in a differing OD schema between 10.4 and 10.5? This isn't an applied policy issue for me as I have no mgmt of this client in place, nor record of it anywhere. I connected to my testbed 10.5.2 Server OD Master just for kicks and the problem is not reproduced, only on the Tiger server..
    I will keep hitting at this and post again if I discover a solution (or at least a clearer understanding of the problem).

Maybe you are looking for