Removing NFS mounts after upgrade

In Tiger, I had set up a number of static NFS mounts to a Linux server using NetInfo. After upgrading to Leopard, these static links are no longer working, but the newly created automounts using Directory Utility work fine. I've been trying to remove the old entries using dscl without success. I have a number of entries in /Local/Default/Mounts, eg:
$ dscl localhost -read /Local/Default/Mounts/doobage:\/home\/michael
dsAttrTypeNative:type: nfs
AppleMetaNodeLocation: /Local/Default
GeneratedUID: B719E4FA-33F7-449A-AD63-0452515F0FF2
RecordName: doobage:/home/michael
RecordType: dsRecTypeStandard:Mounts
VFSLinkDir: /server/michael
I've tried deleting these using the dscl -delete command, eg:
$ sudo dscl localhost -delete /Local/Default/Mounts/doobage:\/home\/michael
Password:
delete: Invalid Path
<dscl_cmd> DS Error: -14009 (eDSUnknownNodeName)
I suspect that I'm simply using the wrong key name, however, there aren't any examples of deletion in the dscl man page. Can someone please point out where I'm going wrong?
Thanks,
-Michael

Try to escape the Slash with a double backslash.
Message was edited by: sica187

Similar Messages

  • External Hard Drive will not mount after upgrading to Yosemite

    After upgrading to Yosemite, my external 3TB hard drive will not mount... can't see in Finder, but does appear in Disk Utility.  Follow steps to Repair disk, but get a message that D.U. cannot repair disk.

    See mount section.
    Disk Unmount Using Terminal
    Disk Utility – Force Mount Disk

  • IDisk won't mount after upgrade to 10.5.3

    I can't access my iDisk after upgrading to 10.5.3. I can sync calendar, address book, etc., but cannot access the iDisk.
    The error I get tells me that my *"Member name or password maybe invalid"* and also "*An unexpected error occurred (error code -8056)"*
    My member name and password are valid because I can sync and access iDisk via the web. I just can't get the iDisk to mount in the Finder after upgrading to 10.5.3.
    Any clues??

    I think I have identified the problem, and have a work-around:
    With 10.5.3 the System Preferences have changed for the .Mac settings. In order to get the iDisk to mount, you need to disable the automatic login for .Mac in System Preferences. Once you have "Singed Out" of .Mac in the System Preferences you will then be able to go the menu bar under "Go" and mount the iDisk. The iDisk will not mount in the Finder icon called "iDisk" but will mount as an icon with your .Mac username.
    Here's how to do it:
    Open System Preferences
    Click .Mac
    Click "Account" tab
    Click "Sign Out" button and acknowledge
    Go to Apple Menu Bar: Go>iDisk>My iDisk and sign-in as usual
    +Finder will launch but iDisk will mount under your .Mac username NOT under iDisk icon+

  • Remove NFS mount

    Dears,
    2 problems:
    1. I used NFS to mount a share drive from a testing machine. Whenever the testing machine reboot, all
    servers who mounted to there will receive a shutdown warning message, how to get rid of this?
    2. When I remove a NFS mount from a system, the "df -k" command will still hang until NFS server timeout, is that anyway to fix other than reboot the
    server?
    thanks.
    Sony

    Dears,
    2 problems:
    1. I used NFS to mount a share drive from a testing machine. Whenever the testing machine reboot, all
    servers who mounted to there will receive a shutdown warning message, how to get rid of this?
    2. When I remove a NFS mount from a system, the "df -k" command will still hang until NFS server timeout, is that anyway to fix other than reboot the
    server?
    thanks.
    Sony

  • Time Capsule won't mount after upgrade to iTunes 9

    See my full post in the Time Capsule support section ("Help! Time Capsule won't mount after installing iTunes 9"). My music library is on my Time Capsule, but after installing iTunes 9, it won't mount on my iMac G5. I can use the internet, but the disk won't mount. My Powerbook hasn't been updated yet and the Time Capsule mounts fine.

    To make it easier, here's the post:
    "My music library is on my 500 Gb Time Capsule. I just installed iTunes 9 on my iMac. It updated my library and synced my iPhone. Now, the TC won't mount. I still have internet connectivity, but I can't access my media or print to my printer connected to the TC. I can use the computer and everything, but if I hover my mouse over the TC disks menu bar icon, I get the spinning beach ball there. If I try to connect using my Network icon in the sidebar, it allows me to log in and get to the screen to select the volume I want to mount, then stops responding. In the Activity Monitor, AFP Client & AirPort Base Station Agent are not responding. I also have a Powerbook G4 w/Leopard (10.5.8) which hasn't been updated to iTunes 9 yet. The Time Capsule mounted fine on it."

  • External hard drives won't mount after upgrading to Tiger 10.4.9. Help!

    Hi, I've just got the latest iMac. Very excited! I did all the software updates, connected my Western Digital extended hard drive so that I could copy some files over onto my new Mac. It was fine at first. Then when I wanted to open up the external hard drive icon on my desktop again and double clicked on it, everything disappeared from the screen for a few seconds, then reappeared but my external hard drive simply opened the window to my personal hard drive on the Mac. The WD links to my computer via Firewire. I then connected my USB external hard drive stick and it was the same story.
    I used Disk Utility to test everything and everything was fine.
    I then reinstalled Mac OSX 10.4.8 and plugged in my external hard drives. Everything worked perfectly. After copying over documents and a couple of programs, and downloading a few more programs, I ran my software updates again, upgrading the operating system to Tiger 10.4.9. I attached my external hard drive and it was the same problem all over again.
    I the read up the online discussions and also chatted to an Apple dealer, and their advice was to download the Intel Combo and reinstall the operating system. I have just done this and my external hard drives will still not mount properly. Their icons appear on screen but double click them and everything disappears.
    Please help. This is really frustrating as I have a backlog of work to do and I seem to be wasting hours on this. Not only that, this is a brand new machine which I rightly expect to work straight away.
    I look forward to your response. Thank you in advance.

    Hi, try to put your HDD in other Mac and look if appear the same, also you can try to repair permission.

  • External USB drive partition not mounting after upgrade to 10.6.6

    Hello,
    I have a Mac Mini and have an external HDD (Seagate GoFlex Desk) setup with two partitions with "Mac OS Extended (Journaled)" format. After the recent OS upgrade, only one partition mounts. I have tried to verify/repair from DiskUtility and it shows all green over there. It just fails to mount. Any help would be appreciated.
    Thanks

    Hi,
    I have the same symptoms : external HD with 2 partitions. Only one mounts.
    I can mount the other one in disk utility and access files in terminal. But the partition doesn't show in Finder or any apps.
    I've tried to disable journal and enable it again but nothing changes.
    Only message I get in the console is when I eject the disk using disk utility :
    2/20/11 7:20:15 PM kernel hfs: disabling journaling for mount @ 0xac60520
    2/20/11 7:20:35 PM com.apple.notifyd[12] EV_DELETE failed for file watcher 97
    2/20/11 7:20:35 PM com.apple.notifyd[12] EV_DELETE failed for file watcher 93
    2/20/11 7:20:35 PM com.apple.notifyd[12] EV_DELETE failed for file watcher 92
    2/20/11 7:20:35 PM com.apple.notifyd[12] EV_DELETE failed for file watcher 91
    2/20/11 7:20:35 PM com.apple.notifyd[12] EV_DELETE failed for file watcher 89
    2/20/11 7:20:35 PM com.apple.notifyd[12] EV_DELETE failed for file watcher 96
    2/20/11 7:20:35 PM com.apple.notifyd[12] EV_DELETE failed for file watcher 90
    2/20/11 7:20:35 PM com.apple.notifyd[12] EV_DELETE failed for file watcher 95
    2/20/11 7:21:04 PM kernel mdworker (map: 0x8cea99c) triggered DYLD shared region unnest for map: 0x8cea99c, region 0x7fff87000000->0x7fff87200000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
    2/20/11 7:21:37 PM kernel hfs: Initializing the journal (joffset 0x1f82e02 sz 0x2000000)...
    2/20/11 7:21:55 PM com.apple.notifyd[12] EV_DELETE failed for file watcher 115
    2/20/11 7:21:55 PM com.apple.notifyd[12] EV_DELETE failed for file watcher 111
    2/20/11 7:21:55 PM com.apple.notifyd[12] EV_DELETE failed for file watcher 110
    2/20/11 7:21:55 PM com.apple.notifyd[12] EV_DELETE failed for file watcher 109
    2/20/11 7:21:55 PM com.apple.notifyd[12] EV_DELETE failed for file watcher 107
    2/20/11 7:21:55 PM com.apple.notifyd[12] EV_DELETE failed for file watcher 114
    2/20/11 7:21:55 PM com.apple.notifyd[12] EV_DELETE failed for file watcher 108
    2/20/11 7:21:55 PM com.apple.notifyd[12] EV_DELETE failed for file watcher 113
    2/20/11 7:22:09 PM kernel mdworker (map: 0xbdb13d8) triggered DYLD shared region unnest for map: 0xbdb13d8, region 0x7fff87000000->0x7fff87200000. While not abnormal for debuggers, this increases system memory footprint until the target exits.

  • USB devices won't mount after upgrade to 10.6

    Hello,
    I recently upgraded to 10.6 and ever since my USB devices (flash drives, and external hard drives) will not mount when the computer is safe mode. The device show up in disk utility but are unmounted. When I press mount it says that the disc needs first aid, I perform the first aid and nothing changes. My computer is always in safe mode, the devices will mount in a normal boot but my computer is not stable in a normal boot. Also, it seems that iPods and cameras work fine.
    Thanks for any help!

    Well, the problem is that - as outlined in one of the articles I linked to - some USB devices will not work in Safe Mode; that may have to do with the fact the Safe Mode is only meant to be a troubleshooting tool, not a regular way of booting up. Did you have the USB devices attached while upgrading to 10.6? That would also be a problem - I unplug everything except keyboard and mouse.And, did you repair permissions after the upgrade? If not, do it now.
    And, the other problem is the fact that you wait 1 - 2 years before addressing the issue; when you had it in for the last repair and it still exhibited the same problems afterwards, you should would have taken it back, possibly with some screenshots, exact notes of how/when/error messages, etc. and insisted on having it fixed or replaced.
    So, I'd run the Apple Hardware Test (after you make sure that you have a complete backup) - instructions here:
    http://support.apple.com/kb/HT1509
    Report back with whatever messages you wind up with.

  • Remove old OHOME after upgrade

    Oracle GI 11.2.0.1/11.2.0.3 - standalone ASM, no RAC
    Oracle db 11.2.0.1
    Oracle Linux 5.6 x86-64
    This last weekend I upgraded my GI from 11.2.0.1 to 11.2.0.2.0
    Old home was /u01/app/oracle/product/11.2.0/grid
    New home is /u01/app/oracle/product/11.2.0.2/grid
    database home is /u01/app/oracle/product/11.2.0/db_1
    Now I would like to clean up by deleting the old GI home, and am testing on a sandbox under VBox. Same system as I used to test the upgrade procedure, and it looks as close to the live box as I can get it.
    Of course, with 11g, the OUI doesn't do installs any more, and the supplied deinstall file also has issues.
    Found MOS note 883743.1, downloaded linux.x64_11203_deinstall.zip and unzipped it, then ran that deinstall.
    The deinstall failed, and the really surprising thing is it complained that a whole bunch of files in the old home are still in use ..
    oracle:vbdwprd$
    oracle:vbdwprd$ ./deinstall -home /u01/app/oracle/product/11.2.0/grid
    Location of logs /u01/app/oraInventory/logs/
    ############ ORACLE DEINSTALL & DECONFIG TOOL START ############
    ######################### CHECK OPERATION START #########################
    ## [START] Install check configuration ##
    Checking for existence of the Oracle home location /u01/app/oracle/product/11.2.0/grid
    Oracle Home type selected for deinstall is: Oracle Grid Infrastructure for a Standalone Server
    Oracle Base selected for deinstall is: /u01/app/oracle
    Checking for existence of central inventory location /u01/app/oraInventory
    Checking for existence of the Oracle Grid Infrastructure home /u01/app/oracle/product/11.2.0.2/grid
    Checking for sufficient temp space availability on node(s) : 'vbdwprod.vbdomain'
    ## [END] Install check configuration ##
    Traces log file: /u01/app/oraInventory/logs//crsdc.log
    Network Configuration check config START
    Network de-configuration trace file location: /u01/app/oraInventory/logs/netdc_check2013-02-05_11-25-55-AM.log
    Network Configuration check config END
    Asm Check Configuration START
    ASM de-configuration trace file location: /u01/app/oraInventory/logs/asmcadc_check2013-02-05_11-25-57-AM.log
    ASM was not detected in the Oracle Home
    ######################### CHECK OPERATION END #########################
    ####################### CHECK OPERATION SUMMARY #######################
    Oracle Grid Infrastructure Home is: /u01/app/oracle/product/11.2.0.2/grid
    The cluster node(s) on which the Oracle home deinstallation will be performed are:null
    Oracle Home selected for deinstall is: /u01/app/oracle/product/11.2.0/grid
    Inventory Location where the Oracle home registered is: /u01/app/oraInventory
    The home being deconfigured is NOT a configured Grid Infrastructure home (/u01/app/oracle/product/11.2.0.2/grid)
    ASM was not detected in the Oracle Home
    Do you want to continue (y - yes, n - no)? [n]: y
    A log of this session will be written to: '/u01/app/oraInventory/logs/deinstall_deconfig2013-02-05_11-25-47-AM.out'
    Any error messages from this session will be written to: '/u01/app/oraInventory/logs/deinstall_deconfig2013-02-05_11-25-47-AM.err'
    ######################## CLEAN OPERATION START ########################
    ASM de-configuration trace file location: /u01/app/oraInventory/logs/asmcadc_clean2013-02-05_11-26-02-AM.log
    ASM Clean Configuration END
    Network Configuration clean config START
    Network de-configuration trace file location: /u01/app/oraInventory/logs/netdc_clean2013-02-05_11-26-02-AM.log
    De-configuring Listener configuration file...
    Listener configuration file de-configured successfully.
    De-configuring Naming Methods configuration file...
    Naming Methods configuration file de-configured successfully.
    De-configuring Local Net Service Names configuration file...
    Local Net Service Names configuration file de-configured successfully.
    De-configuring backup files...
    Backup files de-configured successfully.
    The network configuration has been cleaned up successfully.
    Network Configuration clean config END
    Setting the force flag to false
    Setting the force flag to cleanup the Oracle Base
    Oracle Universal Installer clean START
    Detach Oracle home '/u01/app/oracle/product/11.2.0/grid' from the central inventory on the local node : Done
    Failed to delete the directory '/u01/app/oracle/product/11.2.0/grid/auth/crs/vbdwprod'. The directory is in use.
    Failed to delete the directory '/u01/app/oracle/product/11.2.0/grid/auth/crs'. The directory is not empty.and so on .. to end with
    Failed to delete the directory '/u01/app/oracle/product/11.2.0/grid/ctss'. The directory is not empty.
    Failed to delete the directory '/u01/app/oracle/product/11.2.0/grid'. The directory is not empty.
    Delete directory '/u01/app/oracle/product/11.2.0/grid' on the local node : Failed <<<<
    The Oracle Base directory '/u01/app/oracle' will not be removed on local node. The directory is in use by Oracle Home '/u01/app/oracle/product/11.2.0/dwprd'.
    Oracle Universal Installer cleanup was successful.
    Oracle Universal Installer clean END
    ## [START] Oracle install clean ##
    Clean install operation removing temporary directory '/tmp/deinstall2013-02-05_11-25-45AM' on node 'vbdwprod'
    ## [END] Oracle install clean ##
    ######################### CLEAN OPERATION END #########################
    ####################### CLEAN OPERATION SUMMARY #######################
    The home being deconfigured is NOT a configured Grid Infrastructure home (/u01/app/oracle/product/11.2.0.2/grid)
    Successfully detached Oracle home '/u01/app/oracle/product/11.2.0/grid' from the central inventory on the local node.
    Failed to delete directory '/u01/app/oracle/product/11.2.0/grid' on the local node.
    Oracle Universal Installer cleanup was successful.
    Oracle deinstall tool successfully cleaned up temporary directories.
    ############# ORACLE DEINSTALL & DECONFIG TOOL END #############So where do I go from here?

    Sebastian Solbach (DBA Community) wrote:
    Hi,
    This is a known issue (listed in Readme)
    http://docs.oracle.com/cd/E11882_01/readmes.112/e22488/toc.htm#CHDDJCFH
    Where did you find that particular document?
    I just now double checked the 'readme' docs that came with the 11.2.0.2 media I had downloaded and was working with. The download comprised of 3 (of 7) zip files. The first 2 for the database, and #3 for GI. Of course the 2 db files unzip to a common 'database' directory, and the GI unzips to its own 'grid' directory. Each unzipped directory has its own readme, and neither matches the part number of what you cited. (readme from Database is p/n E15732-03; from Grid is p/n E15732-03). Nor could I find anything about that issue in either of the readmes I have.
    You can either use the workaround stated there.
    However checking for notes in MOS you find:
    How to Deinstall Old Clusterware Home Once Upgrade to Newer Version is Complete (Doc ID 1346305.1)
    How to Proceed from Failed Upgrade to 11gR2 Grid Infrastructure on Linux/Unix (Doc ID 969254.1)
    So you don't deinstall the old home, but you "simply" delete it.
    Ok. Just as I used a vm to practice the upgrade, I've been using it to practice the cleanup. After reviewing my work some more, I see that it reported a 'detach' on the inventory. So I double checked the inventory.xml and see that it now lists the old 11.2.0 home as "removed". Also see this note in the MOS doc I was working from (note 883743.1), stating " Check if Oracle Home folder is deleted or not. If not then you have to remove it manually."
    Still leaves me wondering why the desinstaller reported that it couldn't delete files/directories. Here's a sampling of the messages. Note the variety
    Failed to delete the directory '/u01/app/oracle/product/11.2.0/grid/auth/crs/vbdwprod'. The directory is in use.
    Failed to delete the directory '/u01/app/oracle/product/11.2.0/grid/auth/crs'. The directory is not empty.
    Failed to delete the file '/u01/app/oracle/product/11.2.0/grid/crs/init/ohasd'. The file is in use.
    Failed to delete the file '/u01/app/oracle/product/11.2.0/grid/crs/template/appvip.type'. The file is in use.Note especially that last one .. a file in the 'samples' directory is in use?!?!?! there were a total of 18 files in this samples directory that were reported "in use". And yet when I ran that list against fuser and lsof, they both returned nothing.
    At least I now have a working solution.
    Thanks to you and Pierre for your assistance.
    Please make sure you moved all files... I had custom failover scripts build, which I had placed under $GI_HOME/crs/public.
    These are not copied during the upgrade, so after I deleted the old home, I had to recreate the scripts and to reregister the resources...
    Regards
    Sebastian
    Regards
    Sebastian

  • How do you remove AppleSoftwareUpdate.msi after upgrading to windows7

    Uninstalled itunes before upgrading to windows7 from vista, now unable to re-install due to it being unable to find asu.msi

    now unable to re-install due to it being unable to find asu.msi
    Unfortunately, this sort of trouble has gotten more complicated to deal with ever since Microsoft pulled the Windows Installer CleanUp utility from their Download Center on June 25. First we have to find a copy of the utility.
    Let's try Googling. (Best not to use Bing, I think.) Look for a working download site for at least version 3.0 of the Windows Installer CleanUp utility. After downloading the utility installer file (msicuu2.exe), scan the file for malware, just in case. (I use the free version of Malwarebytes AntiMalware to do single-file scans for that.)
    If the file is clean, to install the utility, doubleclick the msicuu2.exe file you've downloaded.
    Now run the utility ("Start > All Programs > Windows Install Clean Up"). In the list of programs that appears in CleanUp, select any Apple Software Update entries and click "Remove".
    Quit out of CleanUp, restart the PC and try installing iTunes again. Does the install go through properly now?
    (If you do find a clean download site for the correct version of CleanUp, please don't tell me where it is. Without wishing to sound paranoid (although I grant it does sound paranoid), there is a non-zero chance that posting links to download locations for the utility here at Discussions leads to that download location being shut down.)

  • Canon HF20 won't mount after upgrade to Snow Leopard

    Since upgrading to Snow Leopard, my Canon HF20 will no longer connect via USB. This is a basically a USB hard drive as far as the OS is concerned, and I've typically mounted the camera and copied my AVCHD files to an external drive for editing. No special drivers or software was required for this on Leopard. Has anyone else seen this, had it work, etc...?
    Thanks!

    Hello,
    Is your camera still working, and did you do anything special to get it to work? My HF200 doesn't connect properly since I upgraded.

  • Encrypted .dmg won't mount after upgrade to Snow Leopard

    Just upgraded to Snow Leopard and having trouble mounting an encrypted disk image that I use for my confidential files. I have tried mounting using both DiskImageMounter.app and the Disk Utility but both give error 60008, unable to attach.
    Anyone else having similar problems or have suggestions for alternative ways of mounting?
    Best,
    Jon.

    My encrypted disk image with confidential files was created under Leopard using Disk Utility. I just upgraded to Snow Leopard and when I try to mount the image, the password box comes up (as before the upgrade). But, I enter my password, and the disk image does not mount, it just keeps asking for the password again. I also have the latest MacBook Air and I also have an encrypted disk image there too with the same problem when I try to mount it. In addition, I have a LaCie 1TB External Harddrive that contains an encrypted disk image. When I try to mount this disk image, which normally appears on the desk top, I get the same repeating password box. Entering the password does nothing--other than causing the password box to reappear. All three encrypted disk images worked fine without any issues before the upgrade. So, based on the number of views that this post has had, this appears to be an issue that needs a resolution. Any suggestions or others with similar problems?

  • External Hard Drives not mounting after upgrading to Lion

    The disks orked without issue before then I upgarde and nothing.  I see that others have had the same problem but I haven't seen and answer.  Can anyone help?  My iomega drive can be seen in DU but can't be highlighted and is running two red lights.  My Lacie brick disk has completely vanished.
    I'd happily go back to snow lepord if it's a simple fix.

    The disks orked without issue before then I upgarde and nothing.  I see that others have had the same problem but I haven't seen and answer.  Can anyone help?  My iomega drive can be seen in DU but can't be highlighted and is running two red lights.  My Lacie brick disk has completely vanished.
    I'd happily go back to snow lepord if it's a simple fix.

  • NFS mount on boot failing after systemd upgrade

    Hello,
    after upgrading systemd (208-2 --> 208-3), nfs mount on boot will fail. Tested multiple times. After downgrading  back to 208-2, all worked fine.
    Output of journalctl --reverse:
    Dependency failed for Remote File Systems.
    Dependency failed for /mnt/demeter.
    Dependency failed for File System Check on /192.168.20.70:/data.
    Timed out waiting for device 192.168.20.70:-data.device.
    /etc/fstab, the nfs line:
    192.168.20.70:/data/ /mnt/demeter nfs4 defaults 0 5
    uname -a:
    Linux eros 3.12.5-1-ARCH #1 SMP PREEMPT Thu Dec 12 12:57:31 CET 2013 x86_64 GNU/Linux
    I'm using the latest packages (expect grub, it's the version before the current, because of huge ugrade problems, too).
    Greetings,
    Sebastian

    Ah, big thanks. I thought the last column is the mount order, because it's called "pass". I changed it to zero, and now it works.
    Greetings,
    Sebastian

  • After upgrading to osx 10.9.3, my external hard drive was not able to mount, but it can be mounted without issue in osx 10.6, how do I solve it? it was formatted by disk utility.

    Hi
    After upgrading to osx 10.9.3, my external hard drive was not able to mount, but it can be mounted without issue in osx 10.6, how do I solve it? it was formatted by disk utility.
    Thanks
    PT

    From the menu bar, select
     ▹ System Preferences ▹ Energy Saver ▹ Power Adapter  
    and uncheck the box labeled Put the hard disk(s) to sleep when possible, if it's checked.
    If the drive has more than one interface (USB, FireWire, Thunderbolt, eSATA), try one of the other interfaces.
    Check that the data cable is securely inserted at both ends.
    Try a different cable.
    If you're connecting the drive through a hub, connect it directly to a built-in port on the Mac.
    If you're connecting it directly, try a different port.
    Disconnect all other devices on the bus, or as many as possible.
    Test the drive with another Mac. Test another drive with this Mac.
    If the drive is bus-powered, but has an AC adapter, connect the adapter.
    Start up in Recovery mode and launch Disk Utility. Is the drive recognized?
    Start up in Safe Mode and test.
    Reset the NVRAM.
    Reset the System Management Controller.
    If the drive doesn't work under any of the above conditions, and if another drive does work with the same Mac, then the drive has failed. You may be able to salvage the mechanism by removing it from the enclosure and installing it in another one, or in a drive dock.

Maybe you are looking for