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

Similar Messages

  • Un-mounting network volumes with command line

    Does anyone know how to unmount a network volume from the command line in OSX. Using umount deletes the mount but not the mount point. I can't get diskutil or disktool to do it.

    I don't use smb much, but it does look like there's something funny going on. On my system, smb shares mounted from the "Finder" are unmounted normally (mountpoint deleted, "Finder" icon gone) using: 'umount', or eg.<pre>osascript -e 'tell application "Finder" to eject disk "volumename (not mountpoint name)"</pre>But shares mounted using 'mount_smbfs' behave as you describe with respect to the "Finder". But I couldn't reproduce the ".autodiskmounted" file issue in my limited testing involving "normal" use. Sorry, I don't have much more to add - maybe someone more familiar with smb can comment...

  • Why can I no longer mount shared volumes?

    I've got a couple macs that I've been sharing content on for a long time and suddenly I can't see all the volumes on one of the computers. Computer A connects to Computer B via afp. I log in as Admin user and I used to be able to see the 2 internal hard drives but now when I connect, I only see the system drive and my user folder. I need to be able to connect to the 2 internal hard drives. I've even manually dropped one of the drives in the "shared" folder of sys prefs and it still doesn't show up. Any ideas why?
    I've recently checked the "ignore permissions" on this volume check box because I was having all kinds of issues with the shared drive. Could that be it? Why would ignoring permissions keep it from showing as shared?

    any ideas?

  • Mounting NFS Volumes

    Hey,
    I've just got my self a NAS box and setup a couple of NFS shares on it....
    What i'm looking for is advice on how to mount these share on my macs?
    I'd like to be able to use one to use timemachine for backup if this is possible?
    Thanks
    Denis

    I am having the same issue. I can see the nfs mounted shares through the terminal but the finder does not see them.
    I think in 10.3 you could specify which files were visible by the finder creating a .hidden file.

  • Can see drive, but not volume with AEBS

    Perhaps an odd question: I've been using my airport extreme base station as an NAS drive with my Seagate FreeAgent 380Gb drive for some time now, but after moving and setting up a new network (same settings and whatnot, but different geographical location), I can no longer mount the volume through the finder. I can see the drive using the Airport Utility, but not the volume that I want to mount. The volume shows up fine when I plug directly to my computer.
    Oh, and it's mounted NFS+ and Disk Utility doesn't see any problems that need repairs on it.
    Does anybody have any insight into this issue? Anybody else had the same problem?

    is this only while using the remote app on the iPhone? if you just use the regular appleTV remote can you click on an play streamed (i.e. unsynced) content?
    I have all the latest updates and don't have this problem at all but i don't have an iPhone to use as remote...

  • Mounting Remote Shares with the Same Name

    I am accessing shares on remote servers and can mount volumes with no problems initially, using command+k and setting the Server Address to smb://ServerNameOrIP/SharePoint. This mounts a volume with the name of the share point. The problem I've run into is at work I need to mount 2 volumes on 2 different servers with the same share point name. These are shared servers, and for unrelated reasons the folder names on either server can not be changed. This doesn't work well for me. It creates the first volume with the name "Share" and a second one that in finder appears to be called "Share" as well, but if I use "Get Info" or in Terminal run ls /Volumes I can see that it actually gets mounted as "Share-1".
    Is it possible to change the name of one (or both) of these mounts? Mostly so I can see which one I'm on when browsing though Finder. I changed some settings in Finder so that the title bar allows me to see whether I'm on "Share" or "Share-1" but that doesn't actually tell me what server I'm on. Any ideas?

    I just discovered this after trying frivolously to get 2 shares of the same name from 2 different NAS drives to auto mount ....
    limitation with autofs or something ? it should really be painless, as it is in windows. but it seems on the mac side, OS X won't allow shares with the same name to auto mount ....

  • Launching xcode from nfs share (Ensure that Xcode.app is installed on a volume with ownership enabled)

    Hi!
    We have mac mini (Yosemite) and NFS server under Ubnuntu 14.04.
    Also we have xcode resides on NFS share that mounted to mac.
    Problem: When I try launch xcode from nfs share I got error message:
    NSLocalizedRecoverySuggestion=Ensure that Xcode.app is installed on a volume with ownership enabled
    You can see full error here:
    https://gist.github.com/keferoff/fcfd3ea6c13f6ba481fa
    The question is:
    How I can launch xcode from nfs share? For some reasons I can't use xcode-select or store several xcodes locally.
    Thanks in advance!

    It's cool answer but I need solution how to accomplish my task. Maybe I can use iSCSI device or NBD device ot maybe there we have some NFS mount options?

  • AppleRAID Volume no longer mounting

    i applied the "itunes 7.7.1" and "security update 2008-005" updates this morning, which required a reboot.
    after rebooting, my concatenated AppleRAID volume no longer mounts!
    if i run a "diskutil listRAID", it returns:
    RAID SETS
    ===============================================================================
    Name: JINGORAID
    Unique ID: F585E2F9-1ECA-4B8B-942D-9DD156007871
    Type: Concat
    Status: Online
    Size: 1398869557248 B
    Apple RAID Version: 2
    # Device Node UUID Status
    0 disk1s2 EB9F670B-9BDD-4F97-9DA2-CF81597EC1C2 Online
    1 disk3s2 9488CE07-B8CE-4FCC-9987-CF9780D59049 Online
    2 disk4s2 114E4753-E461-49BF-B0C7-EDCD308B628C Online
    ===============================================================================
    in the console log, there is the following info relating to this (filtered only "JINGORAID" entries):
    Aug 14 08:35:29 imac mds[33]: (/Volumes/JINGORAID/.Spotlight-V100/Store-V1/Stores/A00BA05E-2636-4606-ABEF-959 2FA8E4526)(Error) IndexCI in openPayload:open err: 2, live.0.shadowIndexTermIds
    Aug 14 09:05:09 imac kernel[0]: AppleRAID::completeRAIDRequest - error 0xe00002d9 detected for set "JINGORAID" (F585E2F9-1ECA-4B8B-942D-9DD156007871), member EB9F670B-9BDD-4F97-9DA2-CF81597EC1C2, set byte offset = 3285610496.
    Aug 14 09:05:09 imac kernel[0]: AppleRAID::completeRAIDRequest - error 0xe00002d9 detected for set "JINGORAID" (F585E2F9-1ECA-4B8B-942D-9DD156007871), member EB9F670B-9BDD-4F97-9DA2-CF81597EC1C2, set byte offset = 4578750464.
    Aug 14 09:05:09 imac kernel[0]: AppleRAID::recover() member EB9F670B-9BDD-4F97-9DA2-CF81597EC1C2 from set "JINGORAID" (F585E2F9-1ECA-4B8B-942D-9DD156007871) has been marked offline.
    Aug 14 09:05:09 imac kernel[0]: AppleRAID::recover() member 9488CE07-B8CE-4FCC-9987-CF9780D59049 from set "JINGORAID" (F585E2F9-1ECA-4B8B-942D-9DD156007871) has been marked offline.
    Aug 14 09:05:09 imac kernel[0]: AppleRAID::recover() member 114E4753-E461-49BF-B0C7-EDCD308B628C from set "JINGORAID" (F585E2F9-1ECA-4B8B-942D-9DD156007871) has been marked offline.
    Aug 14 09:05:09 imac kernel[0]: AppleRAID::restartSet - restarting set "JINGORAID" (F585E2F9-1ECA-4B8B-942D-9DD156007871).
    Aug 14 09:06:09 imac shutdown[737]: reboot by jingo_man:
    Aug 14 10:35:01 imac fsck_hfs[121]: fsck_hfs(121) malloc: * error for object 0x401380: Non-aligned pointer being freed (2)\n* set a breakpoint in mallocerrorbreak to debug
    Aug 14 10:35:16 imac ReportCrash[315]: Formulating crash report for process fsck_hfs[121]
    Aug 14 10:35:16 imac ReportCrash[315]: Saved crashreport to /Library/Logs/CrashReporter/fsckhfs_2008-08-14-103516imac.crash using uid: 0 gid: 0, euid: 0 egid: 0
    Aug 14 10:35:17 imac diskarbitrationd[44]: unable to repair /dev/disk5 (status code 0x0000000B).
    Aug 14 10:35:17 imac mds[34]: (/Volumes/JINGORAID/.Spotlight-V100/Store-V1/Stores/A00BA05E-2636-4606-ABEF-959 2FA8E4526)(Error) IndexCI in ContentIndexOpenBulk:Could not open /Volumes/JINGORAID/.Spotlight-V100/Store-V1/Stores/A00BA05E-2636-4606-ABEF-9592 FA8E4526/live.1.; needs recovery
    Aug 14 10:35:17 imac mds[34]: (/Volumes/JINGORAID/.Spotlight-V100/Store-V1/Stores/A00BA05E-2636-4606-ABEF-959 2FA8E4526)(Error) IndexCI in openPayload:open err: 2, live.0.shadowIndexTermIds
    just as i was writing this, a pop-up came on screen saying there is imminent failures or something, and has mounted the drive (think this is the last entry in the system.log, above). timing, huh
    what is the cause of this issue?

    Please read this whole message before doing anything.
    This procedure is a diagnostic test. It won’t solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.
    The purpose of this test is to determine whether the problem is localized to your user account. Enable guest logins* and log in as Guest. Don't use the Safari-only “Guest User” login created by “Find My Mac.”
    While logged in as Guest, you won’t have access to any of your documents or settings. Applications will behave as if you were running them for the first time. Don’t be alarmed by this behavior; it’s normal. If you need any passwords or other personal data in order to complete the test, memorize, print, or write them down before you begin.
    Test while logged in as Guest. Same problem?
    After testing, log out of the guest account and, in your own account, disable it if you wish. Any files you created in the guest account will be deleted automatically when you log out of it.
    *Note: If you’ve activated “Find My Mac” or FileVault in OS X 10.7 or later, then you can’t enable the Guest account. The "Guest User" login created by "Find My Mac" is not the same. Create a new account in which to test, and delete it, including its home folder, after testing.

  • Camera Drives (CompactFlash) no longer mount with Aperture 2.0

    Has anyone noticed that camera drives no longer mount in the finder. This means that we no longer have access to these drives in the Finder. I believe this started with the release of Aperture 2.0.
    Stellarphotorecovery no longer sees these drives.
    In addition, files saved to the flash cards (scanned images) are no longer seen by Aperture, iPhoto or Image Capture.
    Anyone have any idea on how we can mount these devices?

    I have been running the Aperture 2.0.1 upgrade for some time now and still can't import Aperture albums. It's all or nothing.
    Does anyone else continue to have the problem after upgrading to 2.0.1?
    Thanks

  • Manually mount volume with xattr option

    I need to mount a vxfs4.1 volume with the xattr option, but I get an illegal suboption error when I try. Is there a specific mount binary required for this to work? I am running Sol 10 kernel 142909-17:
    # mount -F vxfs -o xattr /dev/vx/dsk/ERMBE2B77E5wprdshared_dg/oravol /mnt
    UX:vxfs mount: ERROR: V-3-21298: illegal -o suboption -- xattr
    UX:vxfs mount: INFO: V-3-20147: Usage:

    That is actually the output from mount. The volume is mounted by solaris cluster 3.2, and it is a global mount, here is the vfstab entry:
    # grep applmgr /etc/vfstab
    /dev/vx/dsk/wprdshared_dg/oravol /dev/vx/rdsk/wprdshared_dg/oravol /wprd/ora/applmgr vxfs - no global,suid

  • Mount volume with alternative name?

    I did this before by accident,
    Currently on boot I run a simple applescript exactly like this
    mount volume "smb://uranus/GEN/"
    This mounts the volume as Gen
    The keychain holds the passwords so I have no need to write username and psw into the applescript
    I did it by accident before but I managed to give the drive a different name to GEN something like
    mount volume "smb://uranus/GEN/" with label "WINDOWS VOLUME G"
    Any suggestions how I might be able to do this?
    Many Thanks
    Matt

    Still struggling,
    found this using the Terminal
    mkdir /Volumes/G
    mount -t  smbfs //username:password@uranus/GEN /Volumes/G
    This does some of it. At top level under my imac it appears as GEN but go into macintosh HD volumes it appears as G. but drag it to the side bar and it becomes GEN again.???

  • Mounting nfs shares takes much longer since updating to 10.3.9

    Hi, first post here. The titles of the forums are vague and I hope "getting online" really is the "networking forum"; apologies if not.
    I have two linux machines which I regularly mount nfs shares from onto my powerbook. These machines are on the LAN and have known IP's for netinfod so I don't think the following problem is DNS related.
    Since the last 10.3.9 update, mounting these shares (via finder or command line mount_nfs) has become very unreliable. Sometimes they never seem to mount, sometimes almost immediately, and other times they mount eventually even though I might of canceled the dialog box waiting for the mount. The logs show:
    mount_nfs: bad MNT RPC: RPC: Timed out
    The server side logs show only repeated authentication approvals. The servers have not changed software -- only OSX has been updated.
    Independent if I use WiFi or a landline.
    Once the shares are mounted, there is no detectable connection problems at all. Was any part of the NFS client updated in 10.3.9? Any ideas what might be wrong. TIA.
    12" PowerBook G4   Mac OS X (10.3.9)  

    Just to bump this, as no one has chimed in, I found the problem and I will post the fix only if someone asks. It's not stupid, and it might help you. I am surprised that no one cares.
    I'd still like to know why you can't launch PS from a bootable backup.

  • Mount volume with windows server password (not remembering the password)

    Hello,
    I have a setup through "System Preferences" "Users & Groups" "Login Items", wherein there is a volume which is mounted upon login. Set volume is within a Windows Server domain, for which I have credentials to login.
    My question is related, to the fact that OSX (under Snow Leopard nor Lion), seems to remeber the password for said login, even though the checkbox for "remeber this password, etc." is set. So everyday I need to type in my password for it to mount the volume.

    Satellite C875-S7303
    If you have a Microsoft account, you can reset the Windows password easily. So do you have that or a local account?
    -Jerry

  • Mount network volume: different users same credentials, see different shares

    A set of network volumes on a NAS need to periodically be backed up to a local USB disk. Manually, I can mount most shares (from a Finder window). In a shell script I can list all files due (find) and use that list for backing up to a local USB volume (cpio). So far so good. However, I need to mount these network volumes first. The mount command doesn't seem to work for me.
    How do I mount a network volume in a shell script?
    Also I noticed that if under fast user switching user A logs in with credentials uName and uPassword, the NAS shows 6 shares to choose from. When user B on the same machine logs in with the same credentials uName and uPassword, only 5 shares are visible and one is not shown. It looks as if the credentials do not uniquely determine the volumes offered for mounting. Also, when user B mounts a share, it appears to be owned by user A (who is logged in but has not mounted any share on the NAS) rather than owned by B or by uName...
    How do I mount this volume as user uName rather than A or B?
    How can one uniquely determine the identity of the volume? Network volumes don't show UUIDs and the name given in the /Volume/ folder can change, as is discussed in message 11871367.

    eljonco wrote:
    I just checked: after a reboot, user A logs in (automatic login enabled), user A logs out, user B logs in, ls -a /Volumes only shows local HD and a USB HD. No network mounts there.
    In the finder window, the NAS shows up on the left. Clicking it and entering credentials uName, uPassword, a list of five, not 6, items is offered for mounting. So your options 1 and 4 are then ruled out, unless an alias made by user A and copied to user B's home folder would still link to user A's mounting options.
    Actually, only option 1 is ruled out. That Finder list is simply not reliable. It is likely cached somewhere and could be restored by deleting some hidden preference file. It regularly causes people to freak out when they see some sharepoint listed on a network that they have long since left.
    If you did Go > Connect to Server in the Finder and typed in the location, you could still create an alias.
    Once mounted one of 5 shares as uName with uPassword, an ls -al /Volumes shows the local drives and
    drwx------@ 11 B staff <date> sharename
    and all folders in sharename also show B:staff as user:group. I find that strange, as I did not log in to the share with credentials B, but with credentials uName. Anyhow.
    The uName user is for the network share. When MacOS X mounts that, it gives it permissions appropriate for the user who did the mounting. If you did an NFS mount as root, the server would handle permissions via UNIX uid and gid. I'm really not familiar with the details of AFP.
    As I read in a post about autoFS that 'cd /Volume/theHiddenShare' should magically mount that share, I gave it a shot. Alas, '/Volumes/theHiddenShare: No such file or directory'. Same long shot in the dark in the 'Go/Connect to' dialog gave 'The folder cannot be found'. Not surprisingly, I suppose.
    Yes. That has to be setup
    Here is what I've done to my /etc/auto_home:
    # Automounter map for /home
    #+auto_home     # Use directory service
    # Get /home records synthesized from user records
    #+/usr/libexec/od_user_homes
    myserver.org -allow_other,reconnect,fstype=sshfs [email protected]:/home/me_remote
    I'm not on a big network, so I've disabled the system functionality by commenting out "+auto_home" and "+/usr/libexec/od_user_homes". Now, the system doesn't manage /home and I am free to do with it what I want. This will mount the path "/home/myserver.org" connected to the "me_remote" user on "myserver.org". I'm using the funky MacFUSE sshfs filesystem. Your AFP file system should work much better. Your line would look something like this:
    drive5 -fstype=afp uUser@MyLocalServer:/theHiddenShare
    Run "automount -vc" to reset your automount system.
    Next use Finder Go > Connect to Server and type in "afp://uUser@MyLocalServer:/theHiddenShare".
    You want to mount the drive once so that you can store uPassword in your keychain.
    Now unmount the drive.
    The Finder mounts all go into /Volumes and, as you have discovered, can get themselves confused. This automount will be at "/home/drive5". All you have to do is enter that folder in the Finder and it will be automatically mounted. If you haven't used it for a while, it will be unmounted automatically.
    You may have to play around with this a little. I don't have any network AFP share that I need to mount on a regular basis, so those parameters may need to be adjusted somewhat.

  • Striped + Mirrored software RAID no longer mounting

    I have a MacPro 4,1 using the 4 internal bays each with a 1.5GB drive. Drives 1&2 are mirrored, drives 3&4 are mirrored. Those 2 mirrored drives are then striped together for a volume called 'Titanic.' Been working great for years, but just recently Titanic will no longer mount. My mirrors don't show any errors, but it seems I lost the stripe configuration. I updated to Yosemite last week. When running verify and repair I get:
    Invalid number of allocation blocks. The volume could not be verified completely. File system check exit code is 8.
    Running Terminal's checkRaid I get this:
    AppleRAID sets (3 found)
    ===============================================================================
    Name:                 Mirror2
    Unique ID:            43EF978D-B5CF-4410-82A9-CB0E880B8759
    Type:                 Mirror
    Status:               Online
    Size:                 1.5 TB (1499957919744 Bytes)
    Rebuild:              manual
    Device Node:          -
    #  DevNode   UUID                                  Status     Size
    0  disk2s2   29788AC9-0B7A-4E7E-94BF-E9FD8F697421  Online     1499957919744
    1  disk3s2   6DDF597F-B4A3-4AEB-AB8F-77BD4360A791  Online     1499957919744
    ===============================================================================
    ===============================================================================
    Name:                 Titanic
    Unique ID:            140B7C4C-9A76-4B5B-BFBF-FFE7968A99AB
    Type:                 Stripe
    Status:               Offline
    Size:                 3.0 TB (2999915773952 Bytes)
    Rebuild:              manual
    Device Node:          -
    #  DevNode   UUID                                  Status     Size
    -  -none-    0B55A0E0-CFB1-4B38-84CF-794F5F2AD1D6  Missing/Damaged
    1  -none-    43EF978D-B5CF-4410-82A9-CB0E880B8759  Online     1499957886976
    ===============================================================================
    ===============================================================================
    Name:                 Mirror1
    Unique ID:            0B55A0E0-CFB1-4B38-84CF-794F5F2AD1D6
    Type:                 Mirror
    Status:               Online
    Size:                 1.5 TB (1499957919744 Bytes)
    Rebuild:              manual
    Device Node:          disk5
    #  DevNode   UUID                                  Status     Size
    0  disk4s2   A2103B4C-FF2C-4126-8D5C-DCBF68890AC2  Online     1499957919744
    1  disk1s2   B549FC0E-D281-487F-9017-61F077D0E3A4  Online     1499957919744
    ===============================================================================
    Essentially if my mirrors are fine can I repair the striping? I have everything backed up offsite, but before I put my resources in that direction is there anything I can do to repair the problem?

    My jab at it: Apple vs SoftRAID, for RAID 0+1?
    Began under Mountain Lion or earlier without a rebuild?
    The drives are enterprise type 7.2k 1.5TB (typo) and verified with checksum during vs lips and a tanning for weak sectors...?
    SoftRAID today checks in background for media and I/O errors as well as stepped-read mirrors (3 should be minimum)
    I don't see any reason not to erase and restore, probably to a new set of 3-4 2TB drives with current OS.

Maybe you are looking for