Not searching mounted volume?

Recently got a new mac with the OS X 10.7 and the finder search doesn't work on mounted volumes.
It searches the mac HD fine.
Any ideas?

Did you follow my earlier suggestion:
You can also use Spotlight, but check in Spotlight prefs to make sure none of your disks are excluded (beware that not excluding your disks could take Spotlight a while to index after a reboot...)
System Prefs > Spotlight > Privacy
If the list is empty, then all your drives are included.
That dialogue should look like this (i.e., there should be nothing in the blue/white listing pane):
BTW, if you are new to Mac, be sure to read this:
http://support.apple.com/kb/HT3737

Similar Messages

Searches within InDesign Have Stopped Working on AFP Mounted Volumes On OS X 10.9

I have run into a new problem since using InDesign CC on a Mac running Mavericks, the search function has ceased working on AFP mounted volumes. For example, when placing an image, if I navigate to a pot of images on my server and then tap in part of the file name within the search field there is nothing found, even though the file name I am searching for is there.
I have spoken to Adobe technical support who said "well I do apologize for your inconvenience however adobe does not support if the file is on the network. We would be happy to help you if there is any issue with Search if the files are located locally". Slightly frustrating answer!
This issue looks to be related to the Mavericks operating system as I have Macs running OS X 10.8 which are fine, it is only the OS X 10.9 Macs that have this problem. Is anyone else having these issues?

I have no problem on two Macs running Mac OS X 10.9.2 with InDesign CC 9.2.
Have you started by restoring your preferences. Here's how:
Trash, Replace, Reset, or Restore the application Preferences
If you use the delete folder method, remember that in OS X 10.9, the <Home> library his hidden. In the Finder, hold down the Option key, and choose Go > Library to make it visible.

My time machine back up failed because it says the backup volume could not be mounted

My time machine back up failed because it says the backup volume could not be mounted. What does that mean and how do I fix it so that it backs up?

A whole lot about Time Machine for help with TM problems. Also you can select Mac Help from the Finder's Help menu and search for "time machine" to locate articles on how to use TM. See also Mac 101- Time Machine.
Use Disk Utility to repair the TM drive. If that doesn't help, and you don't find help from the above, then erase the drive and start a new TM backup.

Mounted Volume not shwoing up with Windows 2012 R2 failover cluster

Hi
We configured some drives as mounted volumes and configured it with Failover cluster. But it's not showing up the mounted volume details with Cluster Manager, it's showing the details as seen below
Expect support from someone to correct this issue
Thanks in advance
LMS

Hi LMS,
Are you doubt about the disk shown as GUID? Cluster Mount point Disk is showing as a Volume GUID in server 2012 R2 Failover Cluster I creating a mountpoint inside the cluster
and had the same behavior, instead of mount point name we had the volume GUI after volume label, that must by design.
How to configure volume mount points on a Microsoft Cluster Server
http://support.microsoft.com/kb/280297
I’m glad to be of help to you!
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Time Machine Contradiction: "The backup volume could not be mounted"

(This is only one wireless issue I've had this year, but I'm trying to keep this brief -- hoping clarity will instigate some help.)
Recently I bought a Western Digital 500GB drive to go with my AEBS. I was intent upon using the drive as an Airdisk for Time Machine backups, but it isn't working. (I also have the WD drive partitioned in halves, but there is no reason to believe that is an issue.) When wired, the disk backs-up quickly and easily. After the initial backup, and attempting to do so wirelessly, however, it doesn't work. I get the message: "The backup volume could not be mounted."
And there's the contradiction: the disk is mounted, I'm looking at the mounted disk as I type -- I even have no problems reading and writing from the Airdisks independent of Time Machine. I have all the latest software updates and am running Leopard. I've been going at this for hours, but I would really appreciate some help.
Here are some of the things I've tried:
-checking all connections
-erasing the Airdisk and starting from scratch
-repairing disk permissions(on my internal harddrive, the one I boot on, not the WD)
-attempting to "Connect to Server" in the Finder, only to get this:
And if you look, you can see that while the Airdisks are there, they are grey and can't be selected. It
never becomes possible to select them, and "Connecting to Server" never connects.
-I've toggled every Airport Utility setting to no avail(I will admit I might have missed something though).
-I've done everything I can think of
-banged my head into walls...
-and pulled my hair out, but nothing.
I really would like to get this working. This is my worst Apple experience yet, and it is literally making me sick. You will be my God if you can help me with this. Let me know if you need anymore information. Thanks in advance.
<Edited by Moderator>

Okay, so it seems you need to do initial Time-Machine-ing over WiFi if you intend to use it that way. Why nobody at Apple mentioned this baffles me; why this is even a problem, makes me wonder if Time Machine went through adequate testing.
So my problem is solved! I am my own God!
<Edited by Moderator>

Time Machine - "The backup volume could not be mounted" alert

This is a heads-up for anybody suffering from this error when performing Time Machine backups:
"The backup volume could not be mounted"
I had been using this facility fine for months until a few days ago when backing up mysteriously failed. The Apple support KB articles didn't help (eg, reset time machine drive setup, etc).
Apple Support didn't want to help me because they don't "support backups over networks" - sheesh! What happened to "Think Different!"??
Drag and drop your SPARSEBUNDLE file from your backup drive to the Disk Utility.
Perform a Verify Disk operation by clicking on the button.
A normal backup should be able to perform this procedure, but a corrupted one won't.
When trying to perform this on my backup, the Disk Utility would simply return to the original screen without performing anything a second after pressing the button.
In this case, I found deleting the old backup file and starting from scratch restored my computers ability to perform automated Time Machine backups.
I have concluded that the backup file became corrupted in some way - several previous posts have pointed to systems going into standby while backing up files as the cause of this.
Hopefully someone finds this useful one day.

There is a Time Machine preferences file at
<your startup drive root>/Library/Preferences/com.apple.TimeMachine.plist
Note: This is be main Library folder, not the one in your user folder.
You might try moving that to the Desktop so that the system creates a new one.

HT201372 I am trying to create a bootable USB drive for Yosemite and the terminal is telling me /Volumes/Untitled is not a valid volume mount point. HELP!!!

I erased the USB drive and partitioned it as directed in order to create a bootable drive. When I type in the sudo command in the terminal, it is telling me that /Volumes/Untitled is not a valid volume mount point. HELP!!!

FYI
my process just completed: here is what I see when it is done... (the first you saw in my earlier post. It took about 15-20 minutes.
To continue we need to erase the disk at /Volumes/Recovery.
If you wish to continue type (Y) then press return: y
Erasing Disk: 0%... 10%... 20%... 30%...100%...
Copying installer files to disk...
Copy complete.
Making disk bootable...
Copying boot files...
Copy complete.
Done.

Show mounted volumes in the Sidebar (not servers)?

Anyone have a Leopard tweak or hack to get the side bar to show mounted volumes (i.e.; share points), rather than servers? I need to see the share points, not the server itself (especially when Kerberos is enabled - its just plain goofy)
I like Leopard's Finder improvements for the most part, but need my sidebar to show discreet mounts like 10.4 (Tiger) did. Idont want to see the entire server thats hosting the mounted volume - thats just plain silly. I can use the "Connect to Server" app for that ( or browse the LAN)
Dragging mounts to the sidebar will work (they show up as "devices"), but they are forgotten after a reboot. Its a temporary solution at best.
Is this a bug? A limitation? A disaster? A feature?

I'm not quite sure what your complaint is. You still have the same option to manually connect via the "Go" menu as with Tiger, do you not? Does this not still result in mounted volumes appearing in the devices list? (BTW, "devices" is the appropriate generic name for them in a UNIX environment -- don't blame Apple for that, it is just following a naming convention older & more established than those of either the Mac or Windows OS's.)
If people are confused by the "Shared" section of the sidebar, which is a convenience item not essential to creating sharing connections, why not just suggest they remove it? A set of Finder preferences exists for this purpose. Deselect all three & no "Sharing" sidebar section will appear. Apple is not forcing anyone to use or see it unless they want to.
Moreover, Apple is not the originator of SMB, which has its origins in DOS, was modified by Microsoft in ways to this day not completely documented in any open standards, & must be reverse engineered for interoperability with other OS implementations. Not surprisingly, it must be configured carefully on the server side with this in mind for it to work reliably, which is no easy task since (among other things) its performance, ease-of-use, & security can't all be maximized at the same time. This is hard enough in a pure Windows Server domain environment, much more difficult in a mixed platform one.
Because of this, it may be premature to blame all the connection anomalies on Leopard and/or Finder's sidebar. A review of the protocols & settings used in your shop's SMB servers' implementation may turn up something helpful here, but that is probably best done by a network specialist familiar with the issues involved.
As a side note (& by way of an example), SMB incorporates "auto-discovery" too, just in a more limited way compared to Bonjour. Typically, to maintain network security, it is configured to auto-discover only on a client's initial contact with the server, & there are sometimes reliability issues with this mechanism on large networks due to latency, which may explain some of the problems your users are having.
So, don't be too quick to blame all this on Leopard alone -- as with all network issues, one must look at the entire network to identify causes & their remedies.

Have Mac OS 10.7.4 installed on an iMac-3.1 GHz Intel Core i5...the Finder will not find file on Windows mounted volumes...what setting should we be using...tried the same settings as our iMac 10.6.8-did not work!

Have Mac OS 10.7.4 installed on an iMac-3.1 GHz Intel Core i5...the Finder will not find files on Windows mounted volumes...what setting should we be using...tried the same/working settings as our iMac 10.6.8...did not work for 10.7.4!

Added note: We are tring to find files on Windows 2008 Server Standard...

I get /Volumes/Untitled is not a valid volume mount point when I try to use teminal to make bootable usb stick

I get /Volumes/Untitled is not a valid volume mount point when I try to use teminal to make bootable usb stick. Why and what do I do to fix this. Very frustrating. Thanks for any help. Btw, I went through all the steps properly more than once to fomat and partition etc.
John

FYI
my process just completed: here is what I see when it is done... (the first you saw in my earlier post. It took about 15-20 minutes.
To continue we need to erase the disk at /Volumes/Recovery.
If you wish to continue type (Y) then press return: y
Erasing Disk: 0%... 10%... 20%... 30%...100%...
Copying installer files to disk...
Copy complete.
Making disk bootable...
Copying boot files...
Copy complete.
Done.

Im getting an error message "the backup volume could not be mounted"

I'm getting an error message "the backup volume could not be mounted"

Is this a new message to a drive that has been ok?
Or are you trying to connect a new disk? If so it is wrongly formatted.
Or is this a TC.. have you tried rebooting or resetting it?

Time Machine and update to 10.5.3: The backup volume could not be mounted

I have the same problem reported by many others. Read all the posts, tried all the suggestions and nothing is working.
Western Digital 1Tb MyBook connected to an Airport Extreme. I can see the sparsebundle file created previously, open it and see the previous backups, and even Time Machine can see them. It just won't back up to the drive after the update from 10.5.2 to 10.53. No problem, however, having Time Machine backup to a FireWire WD MyBook connected to the iMac after updating to 10.5.3.
I hope Apple is keeping track of this issue. It was working really nice and I was impressed how easy it was to set up.

Having same problem here, 17" 1.67Ghz Powerbook G4, after update to 10.5.3 I get "Backup could not be mounted" with Time Capsule(w/ user accounts).
Attempted, to no avail:
  Deselecting Drive.  Would not let me reselect. Able to after deleting keychain items.
  Restarting with no drive selected, then reselecting.
  Repaired system permissions.
  Mounted Sparse image, and repaired image.
  Choosing backup now
When the sparse image is mounted, i am able to enter it through time machine's view other backup disks, so i think the image is fine.
the console lists the following entries:
5/29/08 5/29 | 11:32:10 PM /System/Library/CoreServices/backupd[148] Backup requested by user
5/29/08 5/29 | 11:32:10 PM /System/Library/CoreServices/backupd[148] Starting standard backup
5/29/08 5/29 | 11:32:10 PM /System/Library/CoreServices/backupd[148] Network mountpoint /Volumes/sean not owned by backupd... remounting
5/29/08 5/29 | 11:32:12 PM /System/Library/CoreServices/backupd[148] Failed to remount network volume.
5/29/08 5/29 | 11:32:17 PM /System/Library/CoreServices/backupd[148] Backup failed with error: 19
Iv'e tried everything ive seen recommended, does anyone have any ideas?
Thanks, Sean

Mount volume not working in 10.4.6

Could someone please explain why this script does not work in 10.4.6?
tell application "Finder"
activate
mount volume "afp://192.168.1.100/thesharetomount"
end tell
Works fine in 10.3.9 but 10.4.6 gives error "some object was not found"
Thanks for any info

Managed to figure out a trick to get around this problem.
I added user name to the mount command
tell application "System Events"
set myuser to get full name of current user
end tell
tell application "Finder"
activate
mount volume "afp://" & myuser & ":@192.168.1.100/sharetomount"
end tell
Now it works but can't figure out why it does not without giving a user name?

Yosemite run "mount volumes" is not same as Mountain Lion

I have a script to mount the shared folder from Windows server (named: servicedesk) as a volume in Yosemite iMac.
-- -------begin script-----
set loggedInUser to do shell script "whoami"
tell application "Finder"
try
mount volume "smb://servicedesk/M"
do shell script "ln -sf /Volumes/M/ ~/Desktop/M"
end try
end tell
----------End script--------
When run the script on Mountain Lion 10.8.5 iMac, I can list the "M" when run the command in terminal: ls /Volumes/
But when run the script on Yosemite iMac, It's show "servicedesk" instead "M" when run the command in terminal: ls /Volumes/
I don't know why it is difference and can't do anything to create symlink to the Desktop now. Please help????
Thank you,

Thanks for your reply @Camelot
Your reply is solved my question.
But I'm still wondering why it is same the way of script done (in OS 10.10.1) with 2 targets: shared folder on iMac and shared folder on Windows. The script which "mount volume" on MAC is have expected result, Windows is not. Please see the picture to easier understand
1/ "Idrive", is mapped from iMAC, "M" is mapped from WIndows
2/ But when show the result in Terminal, "Idrive" can list, "M" doesn't but it's shown "servicedesk". The icon is also difference on the Desktop!!!
much appreciate your comments

Xsan 4 will not mount volume on client

I recently upgraded my MDC and my client computer to Yosemite. I went through the migration process the best I could and created a Configuration Profile on my MDC for my client computer. I installed the profile successfully but the volume will not mount on the client computer. On the client computer within Profiles, the Xsan Configuration Profile has in red "Unsigned" underneath it, is that what is causing the problem?
Also a few notes: there are two other client computers that haven't been upgraded and are running Maverick and the volume does mount to those computers. The volume is also mounted on the MDC and if I go to Disk Utilities on the client computer I do see the volume, just not mounted.
Any help would be great! Thank you.

Thank you Claudio,
After doing much research and testing I believe you are onto something with my fsmpm or my .auth_secret file not being created. After using Server.app on the MDC I used the configure profile within Server.app. After installing the profile on my client computer it didn't mount and when looking within the Library/Preferences/Xsan folder there was no files (including the hidden .auth_secret file). So I then I used the web profile interface to create the configuration profile and this time it installed the fsnameservers and config.plist files but not the hidden auth_secret file and still no mount.
To answer some of you questions, I did try several times the "sudo xsanctl mount Volume Name" but had no success. I was previously running 10.9 on the MDC and my client computer. I am not sure if the MDC already had an Open Directory Master before upgrading and I did have a little bit of problems activating Xsan, because some of my DNS settings had changed. I got that all squared away and Xsan started working.
The reason I believe it is a fsmpm issue is because when I executed the command "sudo xsanctl i" (views the volumes connected to Xsan) I go a message reading "fsmpm not running error3". So after reading this forum Xsan: "fsmpm not running" message in Xsan Admin - Apple Support I copied the .auth_secret from the MDC to my client and still no mount. I tried again with all the files within Library/Preferences/Xsan folder and nothing. I then got the .auth_secret file from another client computer running 10.9 and still no mount, BUT when I copied all the files within the 10.9 client's Library/Preferences/Xsan the volume appeared! YEAH! But I'm not sure if this is a fix I should be happy with or continue to figure out why its not working the proper way? That way in the future I'm not running into this issue over and over again.
So I need to figure out either how to get my fsmpn running in 10.10 or figure out why my my Server.app on the MDC won't create the auth_sect file. I read somewhere that within the Xsan screen in the Sever app it should show the Authentication Secret, but I do not see this on my Xsan screen. Should it be there and if so is this where my problem steams from? Any thoughts? Thank you so much!

Not searching mounted volume?

Similar Messages

Maybe you are looking for